koen330

The launcher has the option to easily enable/disable modules. What is actually the benefit of disabling modules/terrains? When disabled, are they removed from disk? Are the control binds-lost after disabling a module?

As title says: I will disable the launcher. It delays the startup of the game, does not really add new functionality and uses some cpu (even when game is running) I will disable it....

I also have the impression ED has limited testers with VR capability. Or VR is low on the priority list...

Discord is exploding with VR issues after the latest release.... I wonder if the controller issue is a Quest problem or if other brands are affected too?

I had a lot of respect for ED to postpone the update due to a lot of stoppers preventing the release at the laste moment. They knew they would have a lot of criticism when they did it, but they did. I really don't understand why they released it a couple of days later in this state. Discord is exploding with all the problems created with this release. Seems their extensive testing was not enough. I really don't get it, and fully agree this release is unacceptable if you want to provide a quality product.

After new update, when you launch DCS you are actually launching the launcher...:)

I just upgraded, and my handcontrollers are not working anymore in VR. The handcontrollers work in the new Launcher window, but then you are still in the "PC interface". As soon as DCS starts up, no more handcontrollers. They are still enabled in the DCS settings as before. I use Quest 3. Can somebody confirm similar behaviour, or am I missing something? edit: on discord more users are having same issue....

I just updated to 2.9.6 In VR, the hand controllers work in the new launcher, but when the game starts, and I actually enter DCS, they are not working anymore. They are enabled in the settings, just as before. What am I missing?

I figured it out. When ammo is set to unlimited, there is no haptic feedback for canons/machine guns

Hello, I just installed my ButKicker Pro with Hapticonnect today. (via USB) It seems to be working fine, and I still have to tune the settings. I mainly fly Warbirds, and on these the Canons or weapons don't give any feedback to the ButKicker. I would imagine the Canon in B109 should give a definite punch to the kicker. I also regret there is no feedback from buffeting at slow speed, close to stall. All instruments start shaking when stalling, but no feedback in the kicker. This is a shame and missed opportunity for more immersion. Pulling G's the kicker starts shaking. All in all mixed feelings with the product. Not yet sure what I have to think about it....

OpenXR 1.1 is out. Is this something we can update ourself, or has this to be implemented by DCS or VR headset manufacturers?

+1 We all want DCS to be a simulator as realistic as possible. All modules study level, etc. Flight characteristics as close as possible to the real aircraft, etc. The long grass kills this completely, especially on grass strips for warbirds. If the grass would be this tall in reality, not a single plane would be able to operate on this field, certainly not with heavy payload. Please make the grass shorter on landing strips. It can be nice and long for off-field helicopter operations.

I fully agree. The statement is long overdue. I can't judge what the best approach is for ED to solve the issue, (hotfix or not). I have no IT background. But, I lost hours and hours of troubleshooting before I found this tread. I didn't realise it was the VR part that was causing the crashes. I reinstalled everything from scratch. This was absolutely not necessary if there would have been a short message from ED in their news section. Especially given the fact they are already aware of the issue for such a long time. Luckily we have some smart people here who could help us out with a "hot-fix" so we can sim again. And yes, I joined the forum, so I could take part in this conversation...

Same problem here (on Quest 3). I played DCS, stopped for half an hour. I wanted to continue and BAM, crashing on startup. Probably the Oculus update was pushed at that time. I started investigating, running the cleanup, etc...Looking on internet didn't bring me to this page, as I was looking for DCS crash on start-up, not realising it was the VR part. After a couple of hours I decided to reinstall everything. Jippie, everything worked again (I thought) as the first times I started DCS after the re-Install it was stil in 2D. Me happy again, until I tried VR again, and crashing...:( Realising it was the VR part, I ended up finding this tread. Unfortunately I lost a couple of hours.... Some communication about this problem would have been nice. The above mentioned fix did it for me. I can play again in VR. Still I hope an official fix will come soon.