Gearbox

This would be solved tomorrow if they could implement GPU-per-eye rendering with dual GPUs.

From what I've read the Xtal is actually very efficient with the way it renders and warps the image, and the display has a really high fill factor, so it ends up not needing more GPU than other headsets.

Whoa look at moneybags here. Or are they releasing a consumer version?

Heh, we used to do this in a certain other sim to use the HTS pod to line up Maverick shots on things that didn't justify using a HARM.

Using the camera mounted on the motion platform with Rift doesn't work right. This software seems to work pretty well with iRacing. I haven't actually set up my motion platform to work with DCS yet, I haven't got enough free time. https://github.com/matzman666/OpenVR-InputEmulator/ You fix one of your hand controllers on your chair near your head and the software subtracts the motion. Your virtual head still moves away from where it should be a bit, but way less than it would do without it. The other option is to use no sensors at all. Doing this will fix your head in 3d space and you can only pitch, roll, and yaw it. Drift in the inertial sensor readings will also mean you need fairly frequent presses of the HMD center button.

It's not the answer you're looking for, but get a TrackIR. It will elevate the entire experience. If money is an issue give facetracknoir or opentrack a shot if you have or can get a cheap webcam. https://forums.eagle.ru/showthread.php?t=186375

Those are all small SHORAD systems where the radar is built into transport and launch chassis. If it gets a 146lb HARM warhead to the face I don't think the optical tracker will still be operable.

I wonder what would happen if you ran it in a VM and saved a snapshot.

Ah, I didn't understand that this was only a TIR issue I thought you had it in VR also.

It's a tradeoff... if you constrain the view and a VR user hits the constraint their view becomes uncoupled from what their inner ear is doing and it's really jarring.

Something like this will work great, the computer just recognizes it as a joystick. http://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=205

When I would run Wild Weasel missions in Falcon it was useful because you could use the HTS to get their location to easily set up a maverick or a bomb to take them out. Just had to get closer of course.

It should be since the pimax has so many more pixels to deal with. The very wide FOV means that a good portion of them are outside of the cone that you can actually slew your eyeballs to, so cutting down the quality on that part of the display should be a no-brainer.

When you fly a mission on a server, are all the AI behavior calculations being done server side or client side? If it's server side, would it be possible to run a dedicated server locally on your machine so that all that stuff is happening on its own CPU core instead of the one that's running your DCS 3D rendering?

Hmm, is it worth disabling hyperthreading on my 8700k when running DCS?

That's partly what this mod does: https://forums.eagle.ru/showthread.php?t=215373 Remember we are still in the infancy of VR tech and it takes time for things to be implemented. I don't know how old you are but I remember the infancy of 3D, and before that the infancy of home computers at all. It's a shame that the golden age of flight sims happened back when computers still sucked. Here's a screenshot of the first flight sim I ever played, on the Timex Sinclair 2068 boasting a 3.5MHz processor and 48 KB of RAM.

Are these through the lens photos of the HMD?

I have a pair that I bought back when they came out, are they worth using with VR? Can you use them by feel well enough to be worth it?

Maybe now you can? When I built my new machine a year ago you couldn't. They update Windows constantly and are slowly changing all the control panels over to the new style.

Thanks for this detailed review. Any more updates now that you've had it for a couple of weeks? How's the readability of things like the gauges, radar, and MFDs?

Even in Pro you have to do registry hacks to make it think you set a domain policy or it will just update in the middle of the day while you're trying to use it.

Rendering the scene twice is a killer yes, so we need to claw back whatever performance we can. Your eye is really only capable of high resolution in a small cone in the middle of the retina (the fovea) so as you get further from there you can render the scene with less and less detail. You can knock down or even eliminate the anti aliasing, and probably get away with running half resolution or worse at the periphery. This frees up render power. Even if the double-rendering gets handled better or they finally give us dual GPU with single GPU per eye there are always gains to be had, especially for the crazy high resolutions of future headsets.

I had this, ended up in the ocean a couple of times until I realized what was happening.

Nah, the main difference is that Pro has features for corporate environments like the ability to join a domain.

Here's the benchmarking I was thinking of, scroll down a bit and there are charts for DRAM frequency and impact on FPS: https://forums.eagle.ru/showpost.php?p=2624490&postcount=2 All other things equal he found a 10% increase in average FPS and a 15% increase in minimum FPS going from DDR4-2133 to DDR4-3200.