Gryzor

File is in steam folder (refer to my initial post please). DCS with WMR devices uses steam VR, however I use the DCS non steam version. I notice some performance hit, but no much (however I have a 2080ti)

DCS PD is not the same thing, it does not gives the same results like modding the file I was refering (of course that I tested DCS PD before modding files, along with steam supersampling). The file "\\STEAM\config\steam.vrsettings" and its parameter "renderTargetMultiplier", putting a value of 2, gives a extra detail in clarity (not reachable with default steam supersampling or DCS PD), its like steam software is cutting down the maximum resolution of Odyssey or others WMR devices.

Noticed in "renderTargetMultiplier", 2 or 2.5 number of WMR steam software (by defult, it is is 1.0). You can easily find the difference in A-10 or F18 map MFD. So I think that WMR cliffhouse is more sharper. Do you know other tips for improving clarity in steam with samsung odyssey?

I found a tweak that improves clarity and pixel density in steam VR a LOT in steamvr apps, specially in DCS world (at least, for my point of view): Modify the following files: A) \\STEAM\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings and edit the file, changing "renderTargetScale" : 3.0" (instead of 1.0) B) \\STEAM\config\steam.vrsettings and edit "compositor" : { "renderTargetMultiplier" : 2.5 }, instead of 1. With this file modifications, you will reach the same image quality in SteamVR apps as you have in WMR cliffhouse (or at least, some picture very close). Its incredible for me the difference of quality, now and before is like the night & day. I hope WMR DEVs could implement this in a easier way.

Those exampleas are great, how can I make? I noticed also that with dynamic weather the clouds does not disappears, and there is 0 stuttering opposite with clouds with normal weather Do you can post other weather presets please?

Persian gulf for me is stuttering since last 2 updates. Before it was smooth as silk

I edited this modified labels that works in 2.5.3. I attach the file. It substitutes the "dot" version, just for other version with a subtle dot in VR that fades in/out with the distance, also works with ground units - I edited the fade in/out distances just to have a compromise in VR and realistic view) You have only to put this file in DCS user folder @ \DCS\Config\View Please test it, for me its very useful specially with VR Labels.lua

I could see at 11 or 12 nm (barely, as a subtle dot), but now its impossible to spot anything in VR above 5-6. Any "impostor" option, like the one we had with 1.5 two years ago, will be more than convenient, specially to people with 4K monitors or VR HMD devices.

Not fixed the microstuttering in today´s update. Performance in PG was better in 2.5.2

I have to test it, however, many thanks to all devs for their quick reactivity and support.

what is the situation of the new lighting that will be implemented? starting in PG and extending to other maps? I´m refereing to Chizh post on DCSW News launched 05/05/2018: "Combined, we think you’ll be pretty impressed with the progress. Once this effort is complete, we will move these changes to our other maps." This progress is night lighting we have now? Is a bit different the lighting we have now, in comparison to these pictures: https://www.digitalcombatsimulator.com/upload/iblock/f33/DCS-PG-Night-Lighting-04.jpg https://www.digitalcombatsimulator.com/upload/iblock/ab3/DCS-PG-Night-Lighting-03.jpg https://www.digitalcombatsimulator.com/upload/iblock/1d0/DCS-PG-Night-Lighting-02.jpg https://www.digitalcombatsimulator.com/upload/iblock/1d0/DCS-PG-Night-Lighting-01.jpg

There are many servers online because its the release version

I have no OTT installed in my PC, so OTT is not the cause (i use Oculus debug tool instead). Trying with 1.00, 1.50 and 1.60 pixel density option, ASW does not working in any of them.

I tested with Oculus dash 2.0 disabled, enabling the old one, han have the ASW not working. ASW works perfectly in other software and applications, and in DCS 2.5.2, please fix 2.5.3 ASW not enabling, and of course do not give us the release version witout the fix, please.

I am comparing the microstuttering starting thorough STEAM VR plugin, with both version (2.5.2 and 2.5.3), not by oculus plugin. In 2.5.2 there is not microstuttering

I have the same "lag", like you were drunk in cockpit, appart of ASW not working. Reverting to 2.5.2 after that, ASW on without any lag

I hope that ASW not working will be fixed in next release version. Please devs take this into account as a high priority, Oculus users I believe that are a large % of DCS simmers (I heard in other posts that Wags has a Samsung Odyssey)

Just to report, I have a lot microstuttering in 2.5.3 beta (hotfix) in comparison with release version. Specially noticed when I fly above ground at low altitude. I reverted to 2.5.2 and that sort of "microstuttering" does not exists in PG (even in Dubai is smooth as silk), with my configuration (32GB ram, ssd 2TB samsung 840EVO, 7700K@5Ghz, 1080ti) I tested everything, no software in background, exactly the same configuration between the two testes.Maybe some coding of 2.5.3 related with different pre-loading could cause this new microstuttering? I hope PG map will be tweak regarding performance, or at least, not decreasing in performance from one version to another

what i noticed about the new thin-longer vortex ring: now only generates from players plane, not from AI.

Same. ASW not fixed. :-(

Anybody tried the new beta hotfix? it seems that when I click to update it, it´s not updating

Anybody tried to launch thorought steam VR plugin? because its seems looking forums that others with VIVE or samsung odyssey does not have this problem. Is there any way to force start thorought steam plugin? some command line to DCS.exe??

I noticed that contrais are larger that previous update.

Also crashing at exit directly from flight

I tried all those things, ASW is broken after the update