davidp57

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.

Good news ! Thanks Zeus !

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 !

I was going to say that ; in the EHSD page, one of the bottom buttons will be labelled MK1 ; press it to create a markpoint and therefore a flight plan.

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.

Thanks but does it work without these files ?

With the crash of the cryptocurrencies during the end of 2018, we'll (I hope) see video card prices drastically reduce in 2019. That's my (hope and) prevision ;) Until then, I'll stick with my 1080ti which is quite good already.

I can't help much, I just bought an Oculus 5 days ago ;) But about setting reprojection in SteamVR, you could use Advanced Settings VR : https://github.com/matzman666/OpenVR-AdvancedSettings

Eureka ! @Chic : I had already tried this modification, as I thought I remembered. But now I've been a bit more thorough and I noticed that it only changed the joystick.lua file, whereas I had problems with keys. I therefore decided to modify the keyboard.lua in the same way and voilà : it works perfectly, the keys stopped repeating and are now perfectly usable to map. Attached : my modified modification ;) Config - Keys - NS430.zip

CTLD should do this.

@BadCRC : Thanksm but as I said, I'm using keys to send commands to the simulated encoders of the NS430... I haven't yet found a cheap enough buttons board with built-in encoders - and yes I saw your post about this, it's awesome and it's awefully expensive ;) @Chic : I'll try this although I seem to remember having already tried. Nevermind, I'll try again. Thanks !