VR Shaders mod for better VR experience

[JSpidey]

Correct

Okay thank you

[TomcatFly]

Hi

3 questions for you experts: I use JSGME for enabling these shaders and it's fine, but I still have few doubts:

1) Every time I decide to edit _HMD.hlsl I cannot save the file directly over itself and only way I find is saving it on desktop and then copying and paste into original position, then overwriting and having the updated version. Is this normal?

2) I've noticed that - even emptying "fxo" and "metashaders" folders, at DCS restart it seems DCS takes little bit more time to load than normal, but I'm not usre it is really compiling everything. For sure fxo and metashaders2 folders will be again filled with necessary file. Instead, if with JSGME I deactivate and activate again the shaders, on DCS restart I have to wait a very much longer time and the same also entering some mission for 1st time again, until all is compiled of course. So, my question is : why longer time in one case and very much much longer time on 2nd case? What's the difference between 2 procedures?

3) Considering point 2, what should I do after I modifiy the _HMD.hlsl file (for example removing the bloom or enabling simple glass canopy etc.) to be sure these modification will be effective? Any need to empty fxo and metashadres2 folders in this case, or just enough to modify and restart DCS?

 

Thank you very much!

[mtd2811]

Shaders mod for better VR performance (experimental)

 

Anyone esle getting “shader cant compile” or something like that, error at startup with yesterdays patch?

 

Edit: it says grass2.fx failed to compile and crashes dcs

 

 

Sent from my iPhone using Tapatalk

Edited June 4, 2020 by mtd2811

[Voodooflies]

Hopefully a fix will come up soon. :)

[speed-of-heat]

Hi

3 questions for you experts: I use JSGME for enabling these shaders and it's fine, but I still have few doubts:

1) Every time I decide to edit _HMD.hlsl I cannot save the file directly over itself and only way I find is saving it on desktop and then copying and paste into original position, then overwriting and having the updated version. Is this normal?

2) I've noticed that - even emptying "fxo" and "metashaders" folders, at DCS restart it seems DCS takes little bit more time to load than normal, but I'm not usre it is really compiling everything. For sure fxo and metashaders2 folders will be again filled with necessary file. Instead, if with JSGME I deactivate and activate again the shaders, on DCS restart I have to wait a very much longer time and the same also entering some mission for 1st time again, until all is compiled of course. So, my question is : why longer time in one case and very much much longer time on 2nd case? What's the difference between 2 procedures?

3) Considering point 2, what should I do after I modifiy the _HMD.hlsl file (for example removing the bloom or enabling simple glass canopy etc.) to be sure these modification will be effective? Any need to empty fxo and metashadres2 folders in this case, or just enough to modify and restart DCS?

 

Thank you very much!

 

1) No its not normal

2) it should be a one time thing, nb 2.5.6 takes longer to load anyway, btw i dont think you need to do it anymore

3) normally you shoul d just restart

[TomcatFly]

1) No its not normal

2) it should be a one time thing, nb 2.5.6 takes longer to load anyway, btw i dont think you need to do it anymore

3) normally you shoul d just restart

 

Thank you for the reply.

 

So, about point 2:

 

I've Open Beta 2.5.6.

 

So you mean I should only delete fxo and matashaders and it should be enough for recompiling, right?

 

In any case, as told, if I deactivate and activate the shaders again through JSGME, to load DCS and - even more - when loading a new mission 1st time it can take even 4-5 long mins. While removing fxo e metashaders2 only, it just takes 30 to 40 sec more the 1st time. For this my doubt....

 

Of course, after one or the other thing, all comes back to normality that is very quick DCS and missions loading with my pc and hw.

 

Thank you!

[speed-of-heat]

Thank you for the reply.

 

So, about point 2:

 

I've Open Beta 2.5.6.

 

So you mean I should only delete fxo and matashaders and it should be enough for recompiling, right?

 

In any case, as told, if I deactivate and activate the shaders again through JSGME, to load DCS and - even more - when loading a new mission 1st time it can take even 4-5 long mins. While removing fxo e metashaders2 only, it just takes 30 to 40 sec more the 1st time. For this my doubt....

 

Of course, after one or the other thing, all comes back to normality that is very quick DCS and missions loading with my pc and hw.

 

Thank you!

 

it can do, my point is i don't think you really need to delet fxo and metashaders anymore either... if you get a glitch it might be worthwhile .

 

and yes changing the parameters will cause a shader recompile...

[hannibal]

so is the word to wait for a proper vr shaders mod update?

[Kril]

it can do, my point is i don't think you really need to delet fxo and metashaders anymore either... if you get a glitch it might be worthwhile .

 

and yes changing the parameters will cause a shader recompile...

 

Is mod work with latest patch?

[speed-of-heat]

so is the word to wait for a proper vr shaders mod update?

 

yes

[speed-of-heat]

Is mod work with latest patch?

 

no...

[Hammer1-1]

after this patch, it makes me thankful this mod exists...now I wait for the update.

[Jafergon]

Same feelings here. I really appreciate the work involved in this mod. Supercarrier is no longer playable for me without it :(

[speed-of-heat]

i dropped my in game PD to 0.9 as a short term thing .. works quite well, its not as clear as i would like but it it functions well enough in the short term

[Eldur]

I run at 1.0 PD normally and just for the LOLs and some retro flashbacking, I dropped it to 0.5, just to see its effect on performance. Literally One White Duck / 0^10 = Nothing At All. Looked like back in the 90s though

[m005106]

Yep, unplayable for me since the update. I really need the 45 fps+ASW since I'm pretty susceptible to motion sickness.

I'm thinking of getting a TrackIR since I get decent frames playing through the monitor. I was wondering how hard it would be to check your six with trackIR.

[speed-of-heat]

it's very doable ...

[stormrider]

Yep, unplayable for me since the update. I really need the 45 fps+ASW since I'm pretty susceptible to motion sickness.

I'm thinking of getting a TrackIR since I get decent frames playing through the monitor. I was wondering how hard it would be to check your six with trackIR.

 

 

That thing is expensive. I'd say save your money for a GPU upgrade.

[m005106]

That thing is expensive. I'd say save your money for a GPU upgrade.

 

Quite true, mate. I am at 1080p and the 3600+5700xt just chews through the frame rate at max(excluding MSAA, SSAA, ray tracing) settings.

However, in VR, the only playable(non-nauseating) setting was with the default 'VR' settings, 1.0 PD, 150% super sampling in steam VR(looks like my old EGA monitor from the 90s).

 

My reference line for 'playable' is looking sideways at low altitudes and no tree ghosting. It kinda has to be super smooth. I was getting this smoothness with the shader mod, but no joy since the latest update.

 

So, I was wondering if I should get a TrackIR, or upgrade to a 2080S:D

[Taz1004]

I can live with the frame rate loss. But I loved this mod for getting rid of the fake cockpit canopy reflections. Is there another way to get rid of them?

 

By the way, you get best performance to quality if you're supersampling by factor of two. Or halves. When the HMD compositor down samples 2.35 pixels down to 1, it's not as efficient as downsampling 2 pixels to 1. SteamVR SS 100% is not actually your HMD's native resolution. It already super samples at 100%. So find out your HMD's actual native resolution, then in SteamVR, find the % that best matches 2x your native resolution.

[imacken]

I can live with the frame rate loss. But I loved this mod for getting rid of the fake cockpit canopy reflections. Is there another way to get rid of them?

 

By the way, you get best performance to quality if you're supersampling by factor of two. Or halves. When the HMD compositor down samples 2.35 pixels down to 1, it's not as efficient as downsampling 2 pixels to 1. SteamVR SS 100% is not actually your HMD's native resolution. It already super samples at 100%. So find out your HMD's actual native resolution, then in SteamVR, find the % that best matches 2x your native resolution.

 

Not sure I understand your point. SteamVR SS at 100% is the closest to native res. Certainly on the Reverb.

[Taz1004]

Not sure I understand your point. SteamVR SS at 100% is the closest to native res. Certainly on the Reverb.

 

Not for everyone.

 

https://forums.eagle.ru/showpost.php?p=4345153&postcount=106

 

Just saying to make sure. You can ignore if it doesn't apply to you.

[imacken]

Not for everyone.

 

https://forums.eagle.ru/showpost.php?p=4345153&postcount=106

 

Just saying to make sure. You can ignore if it doesn't apply to you.

 

That must either be a VERY old version, or there is a general SS rate setting as well that works on top of the game specific one. Been 100% for a long time now.

 

EDIT: In fact, if you look at the thread you linked to, you'll see I followed that up with the same questions, and he agreed that there was another setting set and that 100% was, in fact, native.

Edited June 5, 2020 by imacken

[Taz1004]

 

https://steamcommunity.com/app/250820/discussions/3/2666627242542040761/

 

Regardless of the reason, many people with many different HMD's had issues with SteamVR's percentage indication. I simply said to go by the resolution number and don't depend on the percentage. That such a bad advice that warranted all these proof?

[speed-of-heat]

I can live with the frame rate loss. But I loved this mod for getting rid of the fake cockpit canopy reflections. Is there another way to get rid of them?

 

 

you just turn them off ... there is an option under the options -> special menu for the F-18 ... canopy reelections