diamond26

Just two posts above yours, you have the author explaining (supporting) a user of the software and also mentioning his effort towards a rewrite of it. I use Skatezilla's software everytime I use DCS and it's working fine even if it's more than 400 days without update

I agree, but your step 5 reads like you are launching DCS from within Quest. The reason I suggested to not use Quest desktop option to launch, was because there were issues in the past. Haven't used it for ages so I don't know if now it works flawlessly

My suggestion is to launch DCS from PC and not from within Quest2. So after the very detailed steps provided by Nealius you can also just launch DCS from PC (after step 4) Note: The key steps in the process above are 1 and 4 to make sure you have VR through Link

Same problem with F1. Resolved quickly with above. Thanks

Similar observation for mirrors. FPS is lower compared to other modules but not by much.

I have no mods installed (except if VRperfkit is considered a mod in this regard). I see this behavior sporadically especailly when flying in VR. So sometimes everything is fine some others I see these camouflage wings

+1

I can confirm that they work but no move in VR

It would be nice if it can be fixed by changing the projection distance

Same here, the altitude is almost unrecognizable and headings barely visible (Quest2 user without issues in other modules)

Looks like the mission editor doesn't have correct skins or any of the advertised ones

yes as always after updates - fxo and metashaders are taking long to rebuild for each map/scenario

Good you found a solution but obviously this is a specific case cause I also have South Atlantic map and i had no issues after the latest update. But it's a good find for the future. I have seen others mentioned terrains shadercache.

You obviously missed my point whcih was if you tried to isolate the problem by taking out of the equation one of the two mods FHolger OpenVR FSR and VR Shaders and see if you have any impact. I asked about SteamVR because I didn't know if FHolger OpenVR FSR required it. OpenXR is not benefiting all Quest2 users but for sure it's not causing any issue and can do a lot more than ODT/OTT options.

have you checked without FHolger OpenVR FSR (doesn't this one need SteamVR in order to run) ? I'm using Kegetys (TAZ) shaders as I mentioned earlier with Quest2 without issues. When I want to use FSR I use VRperfkit. OpenXR via OpenComposite (+OpenXR toolkit) also works fine with Q2 But if I'm not mistaken Rift S is different to Quest2, so maybe our Quest2 based suggestions are not valid for you.

This version is still working as expected with latest DCS 2.7.15.26783

my understanding is you just switch back to default runtime which is steamvr. So actually as long as you don't run SteamVR and you are not using the option Force Steamvr when you launch DCS, then you are using Oculus default runtime.

There is absolutely no need to use SteamVR with Oculus (link cable or airlink). Oculus has its own runtime and works fine

Mostly 60-100 ft AGL with a pop-up to 3000 ft to see how it behaves looking from high to low while decenting On the topic of perfromance of maps, if SA is at this level now (at least for my system) and they keep improving as everybody else did on maps, I expect similar perfromance as Syria map today, when is out of EA. For comparison this is M2000 over Aleppo at SP settings

I guess you are not familiar with CapframeX legend. Red is just a color for GPU as blue is for CPU max thread, it doesn't mean stuttering. I understand your comments about FPS jumping are against my high settings which makes sense. Lowest FPS figure as you can see for the diagram is P0.1 at 23 fps. The same for lower settings(MP graph) is 40.1 FPS. The difference between the two setups (SP vs MP) is the high ghosting on 3-9 lin eon SP which I can understand at this point of the map development and the busy scenery in Ushuaia. Similar behavior you can find over Aleppo in Syria

I'm so far happy with the early access level performance of SA map. Below an example of what I get flying a M2000 over Ushuaia low level with two different settings and ASW enabled on Quest2 @90hz max resolution. Obviously Multiplayer settings (MP) which are lower offer stable 45 fps with minimum ghosting at 3-9 line.

My experience shows that profiles (with VR enabled in DCS settings) launch with Simple LAunch button always launch with Oculus api. In addition the VR ON is always using on profile regardless of the option selected. I may use something wrong but that's what I have experienced. NOTE: In order to use OpenXR with Oculus you need SteamVR api enabled and Opencomposite

@SkateZillaBut that variable only works for Launch VR ON not for plain Launch (regardless if in the DCS settings VR is enable), correct?

You are welcome

If you follow my instructions you will see that in order for Oculus to work through OpenXR you need Opencomposite. Then you install OpenXR toolkit and start DCS with VR On button in DCS update utility with SteamVR api enabled.