Nodak

It has 1440x1600 res, at 100% your running 1423 verticle, it takes min 108 to equal/ top native. Yeah, it's an oddball with res, 108% makes 1451x1813 on mine. 100% on mine is 1396x1745, and here I assumed they all had the same numbers. Even more important to check the actual res and not the percentage scale.

You set it for DCS while its running, the catch is it won't apply until you shut both off and restart them.

What he said, USAF pointy nose aggressor model for the "original" Nellis map, gladly pay for that.

StarVR is pretty much done, very tiny niche market that no longer needs them. https://greenlightinsights.com/starbreeze-closes-vr-ventures/ I'm hoping Acer grabs all the goodies like the lenses and runs with them in a consumer level set like this one. Why else would they make a detachable set?

Under the tab on the individual aircraft key bind page, at the very bottom is the UI keys. There's four dx bindable mouse keys you can set to a 4 way hat switch on a HOTAS, now leave your mouse where it belongs, on the desk. The game allows you to move the mouse courser in sync with your HMD, so you can simply look at the switch or control and click the hat to action it. Left and right click either rotates or switches, scroll in or out pushes or pulls a control, easy as that and its free. There are some pits where it's tough to see or get the mouse view on certain controls, if you use the switch often, put it on a controller. If you hard mount your controllers, muscle memory works, you don't need to see them. Yeah, what they said, voice attack is the mutts nuts for running all things comms in game.

${1} Bet you can't watch it just once.

Any chance of getting a reset button on the G meter?

Yeah, but if he needs to get out really fast...

Maybe it's a visibility issue instead of performance? For me its easier to fight on Nevada turf, simply because I can see further and judge angles better over the deserts. Very hard to do over the green. Being as your fighting another manned jet, he may be having an easier time judging angles and tracking your big mover.

What your not factoring in is steamVR as a universal app, so a setting of 100% in an Occulus giving a PD of 1 won't give a PD of 1 in a HMD with a different set of screens running a different native resolution at 100%. To get the native res ignore the slider and use the actual resolution read out below it. Such as 1440x1600. You can use steam for in game settings, but you need to know what your particular brand of HMD's actually doing in it. The scale is different depending on your make. A O+ is at base resolution at 108% and will only scale up to 213% maximum in steamVR, there is no beyond despite steamVR showing one. That is a true statement for an O+, but not necessarily true for other makes. Unless you know how your HMD's actually scaling in SteamVR, might be a better idea setting it at true base res and using the in game to scale up. Also something to consider, the relationship between video card settings and game apps. If your trying to up the res in steam, is steamVR actually taking advantage of the cards game setting abilities since it's not seen as the game itself.

Labeling isn't just for pilots, they aren't the only ones who's jobs involve flipping switches. All kinds of shops spend time performing their maintenance and procedures functions. They better be clearly and neatly organized, because many of the guys doing the checks aren't exactly regulars at it.

You can do it yourself, Eagle Dynamics\DCS World\Mods\aircraft\F14\Cockpit materials file, find this materials["HUD_GREEN"] = {36,221,36,255} first three values are the red green blue, last is intensity which is already max. Go here, https://www.w3schools.com/colors/colors_rgb.asp and play with the values to darken, or form a new VR friendly color.

Can't wait for the ships life support section that wipes down and cleans the lenses on my VR HMD between sorties.

Steam should never be set below 108%, anything lower is beneath your O+ headsets native resolution. Settings are card dependent, with an AMD Vega I suffer no penalty with in game 2.0 PD as far as spotting, going one above that and the spotting is gone. So experiment what shoe fits best for you. Also ignore the number of your built in mechanical IPD setting on the O+ HMD, it isn't accurate, go by what your eyes comfort tells you. Play around with your world scaling setting, in game called IPD for some reason, you'll get easier to read cockpits and MFD's if they're the correct size and not too small. Lots of O+ users report the scaling is off, bit on the small side. Smaller numbers = larger scale on the in game IPD, it has nothing to do with inter pupil distance.

Is something weird about them, as you move closer toward them the image of your pilot and pit gets smaller. It's opposite in the F-5.

INS needs to be aligned first.

You ran him out of fuel too, that white streak of smoke was his seat departing. Finish with pistols on the ground, two vs one.

Logical guess, there were more guys with B model experience involved with it's creation, and more deeper research is required for the A, it's been longer since it's been operational.

RCR 0, Alaska, nuff said.

Yes, there is a difference between the O+ and rift, instrument reading, not so much, it is slightly better. MFD's, HUD, absolutely superior. Outside the pit into the world, to die for compared to a rift. You can do a non icon guns fight in a jet very well, don't lose sight, but even if you do you can pick them back up. Was nearly impossible in a rift. The clear sky's and especially desert terrain in shadows is something else.

Just a hunch, but when you land is your left slat extended and right one retracted? Been seeing that bug quite a bit. As for G, its force isn't uniform throughout an airframe. It's a balanced system through force, some with the G, most against. Any surprise you can create shear forces well in excess of the limits. Keep it smooth.

Think it's the opposite, more movement at slow speeds, the C-141 had a rudder system that had two different ranges, higher movement range for slow speeds. It was dangerous to over rudder it at high speeds.

Ever driven up to an icy intersection sloped slightly down with anti skid, it don't work. There's no braking action at all, I'd rather have direct control, at least I have the ability to get the wheel stopped, ABS won't stop it with low traction. I'd imagine those carrier decks get awful slick with all the fluid leaks and petrol products about. That and some occasional sudden angle changes from wave action, not a good mix with taxi inertia. Don't see how you'd do it without direct control, someone would get their toes crushed.

Be great for taking the kids along.

In the key binding list with every aircraft type, upper left, the very last set of keys isn't for an aircraft, but listed as UI. User interface, in it there's bindings for VR zoom, and centering. Also has bindings for mouse actions which you'll find very handy, you won't have to reach for you mouse if you have the buttons ever again. These UI bindings work universally for every module, and will over ride their key bindings once set to a dx key.