3Dmigoto VR mod for DCS : Label masking, color enhancement, sharpen, FXAA, copy/paste of radio MSG,....

[lefuneste01]

2023/01/28 for stable 2.8.1.34667.2 and OB 2.8.2.35759 => version 20.0 available in first post :

• compatibility with 2.8.2.35759, fix bug in sharpen.

As usual, I did not test it too much !

Edited January 28, 2023 by lefuneste01

[kyodjiin]

Thanks a lot ! So far so good.
Performance seems yet slightly lower than before but haze feature is back.

[Pande4360]

Hi any idea how this interacts with VirtualDesktop? The OpenXR version seems to be recognizing the game with VD, the ingame menu seems to work, however the effects are inconsistent. E.g. the color corrections seems to sometimes work and sometimes it doesnt, it switches on and off midflight depending on parameters i havent quite figured out yet. Anyway this shows me the app is generally working but seems to be buggy.

[lefuneste01]

8 hours ago, Pande4360 said:

Hi any idea how this interacts with VirtualDesktop? The OpenXR version seems to be recognizing the game with VD, the ingame menu seems to work, however the effects are inconsistent. E.g. the color corrections seems to sometimes work and sometimes it doesnt, it switches on and off midflight depending on parameters i havent quite figured out yet. Anyway this shows me the app is generally working but seems to be buggy.

Did you do the troubleshooting guide at the first post to ensure you have a compliant configuration with the mod ? Can you post a track showing the issue ?

The global problem is I can only modify low level shaders without having the full view of the game, and it's specificities. For example, AV8 cockpit glass shader was not the same in 2 different mission in the past, but this is no more existing yet. Or the shader I use for color change is not the same regarding G factor. The only way to cope with this is to have feedback and include new specific cases reported.

[lefuneste01]

22 hours ago, kyodjiin said:

Thanks a lot ! So far so good.
Performance seems yet slightly lower than before but haze feature is back.

I did some measurement and did not notice a big change.

You can anyway try to comment  (put a ";" at the beginning of the line) these two "include" lines in d3dx.ini :

;------------------------------------------------------------------------
; flat shadow, to comment if needed
;------------------------------------------------------------------------
include = ShaderFixes\shadows.ini

;------------------------------------------------------------------------
; Mi24 cockpit, to comment if needed
;------------------------------------------------------------------------
include = ShaderFixes\Mi24cockpit.ini

first one is linked to shadow desabling (I did not notice any fps change when disabling shadow) and second one is linked to mi24 map enlightening.

It reduce the number of shaders call "monitored" by the mod.

I did not advertise them but if you can give some feedback.

 

[kyodjiin]

I had some tests and I didn't notice big change either. At least, I have the same performance than DCS without 3dmigoto.

Anyway, I saw several warnings in the d3d11_log.txt you might want to look at :
warning X4121: gradient-based operations must be moved out of flow control to prevent divergence. Performance may improve by using a non-gradient operation

And still getting some errors too :
bin\3dmigoto\ShaderFixes\000000005b2834a5.hlsl(169,20-161): error X3013: 'FXAA': no matching 8 parameter function

d3d11_log.txt

Edited January 29, 2023 by kyodjiin

[lefuneste01]

34 minutes ago, kyodjiin said:

I had some tests and I didn't notice big change either. At least, I have the same performance than DCS without 3dmigoto.

Anyway, I saw several warnings in the d3d11_log.txt you might want to look at :
warning X4121: gradient-based operations must be moved out of flow control to prevent divergence. Performance may improve by using a non-gradient operation

And still getting some errors too :
bin\3dmigoto\ShaderFixes\000000005b2834a5.hlsl(169,20-161): error X3013: 'FXAA': no matching 8 parameter function

d3d11_log.txt 1.72 MB · 0 downloads

 

Warning are linked to menu, there are specific shaders triggered when menu is selected, and they are occuring from the beginning of the mod. They should not have impact on fps. Regarding FXAA, error, are you in 2D or with the stable ?

[kyodjiin]

Sorry, I don't get it. What is 2D and/or stable ? 
I'm running DCS Openbeta

[lefuneste01]

New version 20.0.1 available in first post. This time the error with FXAA should be gone !

1 hour ago, kyodjiin said:

Sorry, I don't get it. What is 2D and/or stable ? 
I'm running DCS Openbeta

Stable is the standard version of DCS

2D is the opposite of VR.

But the issue was occuring for 2D and VR in stable and OB...

[Alex_buka]

Hi! Still have an error with FXAA shader. VR, OpenXR, openbeta. 

d3d11_log.txt

[kyodjiin]

Okay. I'm running DCS OpenBeta in VR mode. I didn't even know 3dmigoto is compatible with DCS 2d.

Edited January 29, 2023 by kyodjiin

[spikenet]

This might have been addressed, is there any issues with running this (openxr version) with the new version of open beta and changes to openxr using a rift?

Edited January 30, 2023 by spikenet

[Eldur]

Since DCS is now running via OpenXR anyways, is the non-OpenXR version obsolete or do we just need the OpenXR version of this mod when using OpenXR Toolkit?

[lefuneste01]

7 hours ago, Eldur said:

Since DCS is now running via OpenXR anyways, is the non-OpenXR version obsolete or do we just need the OpenXR version of this mod when using OpenXR Toolkit?

The mod is working with all kind of rendering, as soon it is direcXt11 and the dll can be injected. I used the OpenXR version of the mod to test OpenXR, I'm not sure the normal version will work with OpenXR. But you can try.

Edited January 30, 2023 by lefuneste01

[lefuneste01]

I uploaded the 20.0.2, the last error should be fixed. It was an issue only when setting menu during high G.

[kyodjiin]

FXAA error fixed. Many thanks !

[Anakin1977]

Don't know if the problem that surfaced after I installed the newest version is because of this mod but I have not changed anything and it started appearing:

 

Whenever I pull more than 6G instead of the standar gradual blackness which if i stop  pulling goes away immediately, I get a balck screen with some whitish cockpit outlines. It is not gradual but immediate and even if I stop pulling, it takes way more to go return to normal.

 

EDIT:I confirm It is the mod. I started DCS without it (i use stable version and OPEN XR through Open Composite) and no problem whatsoever.

Edited February 5, 2023 by Anakin1977

[lefuneste01]

4 hours ago, Anakin1977 said:

Don't know if the problem that surfaced after I installed the newest version is because of this mod but I have not changed anything and it started appearing:

 

Whenever I pull more than 6G instead of the standar gradual blackness which if i stop  pulling goes away immediately, I get a balck screen with some whitish cockpit outlines. It is not gradual but immediate and even if I stop pulling, it takes way more to go return to normal.

 

EDIT:I confirm It is the mod. I started DCS without it (i use stable version and OPEN XR through Open Composite) and no problem whatsoever.

 

As usual, send a track showing the issue (with F18 or AV8 or ant FC3 plane). I used the one given previously to fix G effect: do you have the same issue with it ? https://forum.dcs.world/topic/207154-3dmigoto-vr-mod-for-dcs-label-masking-color-enhancement-sharpen-fxaa-copypaste-of-radio-msg/?do=findComment&comment=5118971

 

Edited February 5, 2023 by lefuneste01

[spikenet]

18 hours ago, Anakin1977 said:

Whenever I pull more than 6G instead of the standar gradual blackness which if i stop  pulling goes away immediately, I get a balck screen with some whitish cockpit outlines. It is not gradual but immediate and even if I stop pulling, it takes way more to go return to normal.

I experienced the same with my rift in the tomcat. Eventually, the occulus software crashed and had to reboot computer to get the headset working again. Works fine without the mod.

Edited February 6, 2023 by spikenet

[Anakin1977]

19 hours ago, lefuneste01 said:

As usual, send a track showing the issue (with F18 or AV8 or ant FC3 plane). I used the one given previously to fix G effect: do you have the same issue with it ? https://forum.dcs.world/topic/207154-3dmigoto-vr-mod-for-dcs-label-masking-color-enhancement-sharpen-fxaa-copypaste-of-radio-msg/?do=findComment&comment=5118971

 

 

Not an experienced user here. Happy to do the job if you guide me on how to put together the track...

[lefuneste01]

25 minutes ago, Anakin1977 said:

Not an experienced user here. Happy to do the job if you guide me on how to put together the track...

At first, can you reproduce the issue with an instant action mission on a plane I own (FC3, F18, AV8, A10CII) ?

[Anakin1977]

On 2/6/2023 at 5:43 PM, lefuneste01 said:

At first, can you reproduce the issue with an instant action mission on a plane I own (FC3, F18, AV8, A10CII) ?

Sorry no. Only Viper avialble here. But i am able to reporduce it every time I pull >6G no matter the environment...

[lefuneste01]

11 hours ago, Anakin1977 said:

Sorry no. Only Viper avialble here. But i am able to reporduce it every time I pull >6G no matter the environment...

could you try to reproduce with the Su25T ?

[kyodjiin]

Hello lefuneste01,

    I just realized that last version turned F18C night colors from green to white for consoles labels and instruments gauges. 

    Is there a setting to revert to green ?

[lefuneste01]

13 hours ago, kyodjiin said:

Hello lefuneste01,

    I just realized that last version turned F18C night colors from green to white for consoles labels and instruments gauges. 

    Is there a setting to revert to green ?

Hello, this is a bug linked to a test I did to see if Kegetys texture supersampling was worth to be used. finally I did not see any changes, but I left the shader with modification commented 'in case of'.
The issue is dumping the shader even without any changes will put this "green to white" effect. I had this kind of issue for other shaders, the only way is to go to assembly language instead of HLSL. But as there is no change done here, just suppress in "shaderfixes" all files named "00000000cc428b13-ps*", it should fix the problem.

I'll update the mod to remove these files. Thanks for reporting, it was not easy to detect it.

Edited February 12, 2023 by lefuneste01