diamond26

After an extensive trial and error activity, I ended up finding that the problem was a binding for the Bombing Table Toggle to my throttle. Why this one caused all this issue with VR and not in 2D, I can only guess because the Bombing Table appears in different position in VR

the problem solved the hard way. Renamed (so I can have important files available) DCS saved game folder and let DCS rebuild a new one. After that F-4E worked again. Now i have to bring back bindings and missions

errors remains with ST - non OpenXR

dcs.log-20240605-172620.zip

The question is why only F-4E has the problem. I played numerous missions, after I discovered the F-4E issue, with other planes even heavy multiplayer and everything run as before. @Cobra847 if you need more details please let me know. I really want to fly F-4E again!

Yes impossible to fly in VR anymore with F-4E

Same problem here. F-4E suddenly stopped working in VR. DCS crashes every time I try to launch F-4E, either instant action or mission based. VR headset is Quest Pro. Can't recall any recent change between Sunday and Monday when it stopped working. In 2D it launches as before. I have perfomed full repair and no mods are running. any plane_VR_dcs_working.log F4E_2D_working_dcs.log F4E_VR_broken_dcs.log

what sounds exactly are you reffering to?

V65 works as expected on a Quest Pro

Generally speaking the map is behaving really well for its size and nature. Better than South Atlantic. I had to reduce Forest Detail factor to 0.5 to keep 72 FPS at low levels.

it seems it's the new price for maps these days (latest flyable modules are priced at 80$). Both Afghanistan and South Atlantic are at the same price. Sinai and Syria are at 60$

This looks like a good idea. Can you provide the 3D file ? I have also researched the Globular Cluster headphones and the reviews I read were not in favor, so I'm still using the QPro ones. I tried a set of Bluetooth earbuds I have but I was getting a lot of background noise while in game.

here are two test on my system with Qpro (using Quad Views) and process lasso to distribute better the cores' workload null nullnull

Yes I witnessed the same. It's a bit lower with 2.9.4. Nothing else though (stutters or bad artifacts)

@baltic_dragonI flew the mission last night and this behavior is still there. Obviously I went directly to the carrier but it will be nice to have it resolved next time you revisit this one.

Thanks for the update. The Tanker topic is a matter of reality vs game play. If people want an easier play then I understand the slight disortion of reality. At least we managed to get refuelled without being shot down!

@Jenson last night we flew the remastered M10 (thanks again for keeping this campaign updated). We noticed an issue with AI DCA. They followed us in our return till the carrier and actually we had to enable one of them as he got too close. Carrier group then took care of them while we were performing our CASE III recovery. Note: Texaco 1-1 seems to be too close to enemy forces ( there was a point that the tanker was 45 nm from the enemy)

The guidance was only to block Oculus PC app to go to V63. For the headset, apart from what you suggest (which I haven't tried) the only option is to keep wifi off In addition the headest updates if you have SW updates off are enforced after some time. For example v62 in my case has a mandatory enforcement by 28/3. So I guess you are safe in headset with SW updates set to OFF even with wifi on for some period of time which will be mentioned by META.

I only created a bak.staging (actually renamed an existing folder) and a bak.tmp folders and it worked as suggested by @Lange_666

what about this suggestion :

I have also mentioned the issue to META in their support page (not that it matters too much as they use AI for response! )

I'm coming back on this topic of low VR performance. F1 on a low spec machine (like my laptop with an RTX2060 6GB) is definetely not playable in VR compared to other models. Using Link (Quest Pro) and the same settings the difference between F-15E (heavy also in VR) and F1 is 15-20 fps which brings the F1 down to 9-10 FPS Using Virtual Desktop F1 is a bit better with 20-30 FPS. This means that F1 is making more aggressive use of VRAM. And to give you a more startling comparison, F-18 free flight in the same map is averaging 50-60FPS!

Fixed!

Same problem as OP witnessed today. Map is functional but getting the message to install it.

Me too, Oculus Link provides better quality and stability and ASW is miles better that SSW from VD. VD seems to help when I use my laptop as the VRAM is limited and the VD's VRAM use is better compared to Link. That's a requirement for eye tracking to work for VD and Qpro. I imagine won't do anything for Q3