davidp57

→ this

Hi guys ! Thanks OP for this excellent thread, good idea to have it pinned. I've got a question : while experimenting with Oculus and DCS (vanilla version, not Steam) I noticed that the LeftCTL+KP7 and LeftCTL+KP8 did something : the oculus image froze, there was a sound like a device was disconnected, and the image moved again as if nothing happened (also the FPS changed). Are these new shortcuts added to Oculus to complement the CTL+KP1/2/3/4 ? What did it do ?

+1

Sorry Wags but I don't understand your answer (in context). Other than that, we also have this problem (sometimes, not always) in our MP missions.

Speed is probably not the same, too ; I don't know if this has an effect on radar...

I'd suggest to bind it to a keyboard shortcut (in the Control Options) ; it's very frustrating to start up a Harrier, line up the navigation system, then try and click on the "parking brake" but only succeed on hitting the fuel cutoff (which is right beside it) and shutting everything off :P

This works for me : I'm on a Acer Predator 34", 100hz GSync monitor, with an additional 12" 1080p 60hz for MFDs. If I turn GSync off, my Predator runs at 100hz and the MFDs at 60hz, with no visible stutter (to which I'm quite sensible, so I'd have noticed). If I turn it on, of course the Predator refresh rate adapts itself to the game fps, and the MFDs stay at 60hz ; still no stutter. I'm on Windows 10 with all the latest updates, Geforce 1080Ti (11GB) with the latest Nvidia driver, the Predator plugged on DisplayPort and the 12" on a DVI-HDMI adapter.

You need to trim when your speed changes, or your weight (e.g. when refueling, or dropping ordnance). Other than that it should not be necessary. You can also use autopilot ON, then OFF for a quick auto-trim

Great, thanks !

Harlikwin, could you elaborate about the ASW off and ASW on keyboard shortcuts please ? Are these in DCS ? I can't find them in the controls setup screen...

In my humble opinion, it's all a matter of layers : in any case, your Rift will use Oculus service to render data. If you use SteamVR another layer is added which uses Steam, then Oculus service. Not sure it's useful...

Happy to help ! I discovered this by accident when looking through header files.

Well done ! I admire your courage and fortitude !

You can also put this in your script : //Turn off automatic Joystick and Throttle disabling Configure(&Throttle, MODE_KEEPENABLED); Configure(&Joystick, MODE_KEEPENABLED);

Ejected pilot at angels 600 ;)

Tu seras le bienvenu à la VEAF ; les copains sont moqueurs et la bière est fraiche : une vraie bande de pilotes ;)

There is a left and right trim ; in fact for most planes it's a good idea to map a hat button on the stick (the Warthog has a grey one dedicated to trim on the A10) for the 4 trim directions. I do not constantly trim, except : - when droping ordnance - when changing pitch / roll while under autopilot (trim will make the autopilot climb/descend or go left/right without turning it off) - on VSTOL with cross wind

Hi, thanks for the suggestion. Since fpsVR is sold on the steam store, does this mean that it does not work out of SteamVR ? My DCS is standalone and uses the Oculus Rift without SteamVR ever launching...

Trim, trim, trim ; and then trim again. :D More seriously, when anticipating an asymetrical loadout on the harrier (which does not like it at all), trim first, drop your weapon, then trim more. Here's what I do, considering I'll drop a heavy bomb from the left side : - start level and on autopilot (ensures a perfect trim) - trim a bit to the left, up to the point I need stick input to the right to maintain level flight - drop my bomb - immediately trim more to the left, up to the point I'm more or less trimmed - turn autopilot on again

You can also drop the Liveries\AV8BNA folder straight into your Saved Games\DCS folder !

This relates to the way the Sensors Point of Interest is tracked : - IRMV → the Maverick IR camera is slewed by the TDC and the Maverick computer tries to keep the image fixed by tracking the contrast differences in the picture - TV → the DMT camera is slewed by the TDC and the plane computer tries to keep the image fixed optically - INS → the DMT camera is slewed by the TDC and the plane computer tries to keep the image fixed by pointing the camera at coordinates using the inertial navigation system (INS) When the DMT cannot see the target (e.g. it goes out of its gimbal limits) the system switches to INS automatically so it can remember where the target was. As soon as the remembered target comes back in a position visible by the DMT camera, it switche back to TV automatically. Hope this helps.

It's the conjunction of low screen resolution (objectively big pixels) and short screen-eye distance (subjectively very big pixels) which makes the small gaps between pixels almost visible, giving the idea of looking through a fly net

isn't it possible to completely disable the 2d mirror ?

Thanks n26 for this excellent tool !

This is what you want : http://www.2112design.com/blog/multi-keyboard-remapper/ I used it myself to make a poor man's UFC out of a spare gaming keyboard. Tell me if you need help programming it.