lefuneste01

Good !

Activate what ?

Version 19.0 available for testing here: https://www.mediafire.com/file/jjkl6kze5ny29q2/3DmigotoDCS_VR_19.0.zip/file New feature to lighten Mi24 moving map, new menu for NS430 position/scale, fix for high G, cleaning. An "helicopter" menu page is available to host rotor and Mi24 setting. You must setup NS430 mode to 1 (display GPS in GUI windows) to setup its position by the menu.

Hello, can you post a track using the F18 ? I was about to release the next version, so it should be better if it can fix your issue...

Issue reproduced. I found the shader to use, I need now to do hte fix. It will be in next release, as a new option to enlight the moving map of the Mi24, I found it too dark in VR.

Hello, can you post a track ? This is the version of 3dmigoto library used by the mod.

Could you share the list of these edm and an associated track ? It should help to have things fixed at mid term by devs and allows other to optimize fps at short term... I had another case with huge fps impact : It should not be related to hangar. It seems devs are not so often taking reports like this into account...It's too bad, because it may help to lower fps impact of things more complex to solve. My mod is still for example increasing fps by 300% with cluster CBU explosion, some optimization and option should be provided to allow people to choose eye candy explosion/smoke putting your PC on its knees or less rough graphics but more constant fps. It will become crucial as soon as better CPU parallelization will be provided, so issue will be mostly on GPU.

Could you post a track ? If it's GPU related maybe I can do the same than I did for CBU cluster in my mod.

Hello, this is a common NVS issue, by default they fill the whole FoV in VR for all modules. You need to use mode to reduce their size.

Hello, try my mod : https://forum.dcs.world/topic/207154-3dmigoto-vr-mod-for-dcs-label-masking-color-enhancement-sharpen-fxaa-copypaste-of-radio-msg Press CTRL+I in game to toggle on/off TADS overlay. It will also toggle PNVS...

But I think I'll need to modify it for the BS3. My SSD on which DCS is installed is out of service, I'm waiting a new one to re install DCS and work on it.

Or mine, which does a little more than NVG size and will allow you to set the size using a menu while in game :

It should, but there is also a setting in the DCS special option tab for the F18.

You can try my mod, it has an option to disable rotor (only from cockpit view) for AH64, Mi24, Gazelle, Ka50:

It should work except if you are using NS430 in 2D...As nobody reported the issue, I did not try to fix it. Post a track, I have the gazelle and can have a look.

You can try my mod, even if it do not remove sratch texture (they looks ok in VR, at the opposite of fake reflects that looks like stensil) :

For people using VR, you can use my mod to reduce size of NVG and si be able to look below them (as in real life, for what I understand) :

You can try my mod

Did you compare OpenXR fps with SteamVR fps ? I had lower fps with OpenXR...

Just do what is in troubleshooting guide of first post it should be enough. But anyway à as you re install all you should have a clean config. Check that all graphics settings are the same than in the pdf of first post. Then, to check things: Use one su25T standard mission, setup cockpit color change, set mul factor to zero, save by F12 => cockpit will be black. Otherwise you have an issue with settings, or other mods. Then launch your mission with the F16 and check if cockpit is still black. If not, there is an issue either with F16 (I do not have it so I can not check) or context of mission, that is another gobal shader than the one used for all other missions may be used. In this case, try to modify the mission to replace the F16 by a Su25T, check if the issue is still there. If yes, post the mission here, so I will be able to reproduce. If not, this is linked to F16, as I do not have it I will be able to fix by 15 days trial but not after...

Strange, as it is based on the shaders used for global illumination, which are also used to identify cockpit and "oustide" areas, needed for color, label masking and sharpen features. I tested it on the modules I have : AH64, AV8, Mi24, F18, Mig21, UH1, A10C, blackshark, Gazelle, lockon planes. I wonder which modules are so impacting they change global illumination...

Good find, I left a test in d3dx.ini. I'll fix it for next release, but in the meantime you can remove "+10000" in the line post x2 = $\users_settings\user_keymapping_setup.ini\labelMaskFlag+1000 in d3dx.ini.

Hello, I tested only in external view, because it's easier to check effect on horizon. So I'll have a look. But some other features may also not work for you, as for example color changes/sharpen only for cockpit, label masking,...Can you ensure you have the same graphic option than in troubleshooting guide attached in first post ? EDIT : I confirm it is working in cockpit, so please do trouble shooting guide.

All features are disabled by default. You'll have to go through menu to set them (or press some shortcut keys to toggle them on/off, like color change or sharpen mode).

Which options have impact on HUD or HMD ?