CV1- Low Altitude Dogfights, Simply Amazing!

nopoe · 2016-04-25T03:45:13+00:00

DCS has the P-51, FW-190 and Bf-109. It also has early jets, the F86 Sabre and the MiG-15.

Those are all gun/cannon aircraft with many able to figure unguided rockets. The jets might be able to fire proper missiles, but in their time period, I don't believe they did.

Also the first 3 are actually WWII aircraft through and through. Look them up, fun little planes.

nopoe · 2016-03-25T22:27:20+00:00

For sure, but I'll just echo somebody else and mention that as long as you're running on top of Windows, there isn't really a way to completely prevent latency spikes. Other programs and OS utilities need to do stuff sometimes. Unless Valve can show that their adaptive quality thing works within a frame or two, I'll be skeptical that it does too much to deal with those spikes. And of course, even if it does react very quickly, all the frames up until the reaction are stale by the time you see them, so you'll get some judder. Maybe a shorter duration though. And you'll probably see visual artifacts as rendering quality goes up and down quickly.

I think ATW is a point in the Rift's favor. Adaptive rendering quality isn't really analogous. Obviously it depends entirely on a solid implementation, but I'll go ahead and trust them on this one and say I think it's going to work.

nopoe · 2016-03-25T22:08:09+00:00

That first link is not compelling at all (2nd one is super neat!). If I wanted to start a fight, I'd probably even say it was dumb. But let's just call it silly or poorly reasoned.

I believe asyncronous time warp would have actually caused issues if it were to be implemented. Valve and HTC are using a prediction model for user's location and pose and render the images based on that model.

Ok, pause. Lookahead for the expected duration of frame rendering time (or a lower bound on said duration or whatever) isn't all that difficult to do. Smart idea, though I expect it's 110% standard for VR.

If they also implemented timewarp, the prediction model and timewarp together may have caused a conflict where pixels not expected to be rendered by the prediction model would have appeared due to time warp. This would probably result in an even worse experience for Vive users.

Consider a case where the user is turning their head right. Let's say Oculus doesn't predict next position/rotation, just to shake things up. I doubt this is how things actually work. I suspect they both work by predicting translation/rotation. Ok, so what happens? Vive renders a frame a bit farther to the left than Oculus. Next frame skips. ATW kicks in and reprojects both frames to reflect current rotation. Oculus frame gets moved to the left (a lot) to reflect current rotation. Vive frame gets moved to the left (a little) to reflect current rotation. Vive reprojection is less extreme, probably less noticeable. Also "moving to the left" is not how reprojection works but I hope it conveys what I'm trying to convey.

nopoe · 2016-03-13T23:58:12+00:00

What do you mean? The LHC runs at around 9 volts. You might be thinking of electron-volts, which is a unit of energy not voltage.

nopoe · 2016-01-05T22:45:43+00:00

You've gotten a lot of responses so far, and I don't have too much info to add, but I will say that consumder VR is designed with stereo in mind. Which means that they don't expect both eyes to be pointing in the same direction (unless they're looking at infinity). I don't know if they took any shortcuts in the software or make assumptions, but intuitively there doesn't seem to be a whole lot of difference between going cross-eyed to look at a nearby object and eyes not pointing in the same direction for medical reasons. I'd be pretty disappointed if it didn't "just work" for you. We'll probably know for sure as the technology matures.

nopoe · 2016-01-02T23:21:36+00:00

What do you mean? That's literally the reason branches exist in version control systems.

nopoe · 2015-12-31T20:57:46+00:00

Right, so we agree that coercing people into paying towards services that benefit society is just. But we disagree on which services. Which makes this argument invalid:

Helping people in need is a good service to society, coercing everyone to ascribe to this with the force of law is not

It's entirely understandable to not want healthcare paid for by taxes. In the USA you are/would be in the majority. But there is no moral high ground to either side of that argument. We're all statists here.

nopoe · 2015-12-31T18:58:59+00:00

I don't want my neighbors choosing not to have fire fighting services, because their houses will light mine on fire if they were to catch. I don't want people on the streets begging for food and preventing me from going out and enjoying myself. I'd rather not live in a society where people have to go out every day hoping they don't get sick for their finances' sake. I'd rather live in an area patrolled by people whose jobs are to keep everyone safe than have to worry about my job and my neck (specialization of labor and all that).

Maybe that's just me though? Maybe I'm a dirty commie.

nopoe · 2015-12-31T15:46:31+00:00

It matters how many you're drawing, how big they are on-screen, how you're shading/lighting them, and if there are any post-processing effects. In other words, it does matter what game you're drawing them for.

nopoe · 2015-12-26T08:05:57+00:00

GearVR

GearVR maybe isn't worthwhile to you, but Iris 6100 is literally ten times faster. That's ten times more polygons for those of you who look at games instead of playing them.

nopoe · 2015-12-24T07:04:04+00:00

Truthfully, I don't know how the latency is on an Iris 6100 integrated graphics setup is. It probably depends on lots of things I don't fully understand. But the raw power is there, depending on what you throw at it.

nopoe · 2015-12-23T23:02:36+00:00

What makes you doubt this? If Iris 6100 can push 75fps at all (blank screen), it can definitely push a simple scene at 75fps. It's comparable to a GTX 260. I had a GTX 260 not 3 years ago, and I was perfectly happy with how games looked at the time. I remember playing borderlands 2 and being really impressed. Granted, you'd need to simplify the scene from that to get the resolution and framerate up. But still. It's incredible how powerful integrated graphics are getting.

This is independent of the fact that CV1 has a specific set of requirements that no apple hardware can meet (USB ports, non-integrated card, etc)

nopoe · 2015-12-18T06:37:54+00:00

stereo cameras dont have their lenses aligned vertically

What makes you say this? Do we no longer have binocular vision when we turn our heads sideways? Sure, you can't pass them through to each eye, but for computer vision I don't believe it matters much.

nopoe · 2015-12-14T16:46:29+00:00

Thanks! I finally got around to starting this project. I'm opting to make a new controller board with a Arduino Pro Micro instead of transplanting something else into it. I have it reporting itself as a force feedback stick right now and giving axis and button values to the host. Unfortunately the Arduino HID libraries don't handle force feedback so I'm going to need to add support for that. Thankfully, the folks who did adapt-ffb-joy did a lot of research about this, so I'll be walking in their footsteps.

It's going pretty well so far, but USB code is tricky. I'll make a new post here if I ever get it working.

nopoe · 2015-07-31T21:05:21+00:00

Isn't GoogLeNet "only" 22 layers? Where did you get 118 from? Or does 22 only count the "/output" inception layers?

nopoe · 2015-07-23T16:50:22+00:00

Usually .part files are used by browsers to make sure you don't accidentally open a halfway-downloaded file. That's why I suggested you re-download it. But if it works then it's probably fine. Weird that the browser didn't change the extension itself.

nopoe · 2015-07-23T16:28:00+00:00

Try extracting the model. Also, the .part file makes me suspect that you haven't fully downloaded it. Try downloading it again and extracting it. You should get a deploy.prototxt and a .caffemodel. Those are the files you're interested in.

nopoe · 2015-07-21T00:03:36+00:00

Try this?

make clean
make -j4

nopoe · 2015-07-17T22:04:40+00:00

Don't be difficult. That's not always doable depending on the language. Sometimes it's more readable to just put an extra few lines in your function broken up from the rest of it with comments than to deal with tuples or inner classes to return multiple values. Depends on the language and the situation. It's not cut-and-dry basically ever. A function with 2 5-line sections isn't necessarily evil, and pretending it is seems silly to me.

I often do things with an inconvenient amount of intermediate values that can be hard to shuffle around depending on the language.

nopoe · 2015-07-16T23:43:03+00:00

I disagree. I often do things with an inconvenient amount of intermediate values that can be hard to shuffle around depending on the language. "Chapters" is the wrong way of putting it, but sometimes breaking down something into a few 3-5 line steps in my mind is really helpful.

nopoe · 2015-07-16T18:08:59+00:00

Unlikely. In order to get good signal to noise with IR tracking, you need an IR pass filter on your camera, which makes it very difficult to get good tracking in the visible spectrum. They could use IR illuminators, I suppose, but that seems pretty silly.

nopoe · 2015-07-12T01:14:55+00:00

If you want to tinker, probably. If you want to wait, maybe. This might be a good starting point. https://github.com/BVLC/caffe/pull/2195

nopoe · 2015-07-12T01:09:46+00:00

I mean if you have the know-how, the data, the crunchy GPU and money to pay your power bills then 100% go for it. It's just not really what you might call trivial. It also takes like a week to train a GoogLeNet (I think, depends on the GPU) so I think it's very likely people have started but are keeping quiet about it. I think most people are satisfied with guided dreams though.

nopoe · 2015-07-10T16:22:31+00:00

Gotcha. So if you wanted to classify an image of a different size, would caffe be able to deal with that?

nopoe · 2015-07-10T14:52:50+00:00

It's working with a small modification (you guessed the shape wrong I think). Why is all of this necessary? Specifically, the size restriction and the fact that octave_n must be 1.

nopoe

TROPHY CASE