RedHot

I looked up the Vive controller bindings in the DCS controls tab. It did not have any axis bindings. Tested again, but no joy. However, I found out that it is only the left hand controller which is the problem. When the right hand controller is on, and the left is off, everything works just fine. When the left hand controller is on, the stick starts flickering again. After checking that all Vive bindings in DCS were deleted, I starter testing bindings set up in steam vr. I stripped out everything from the DCS app spesific binding configuration (only left grip laser pointer and trigger click). This did also not fix the problem. Then I did the same stripping of bindings for the Steam VR app and Steam Home and VR Dashboard apps. Same result. No joy. So far, it is clear that the problem is the left hand vive VR controller. Something with its configuration is messing with DCS, and makes the stick flicker and the game unplayable in VR. please help.......... PS. Flying the Hornet using a Thrustmaster Warthog Throttle and F-18 stick

Done some testing on this problem and found that the left VR hand controller is causing the problem. If I turn of the left controller and keep the right one on, there is no flickering when moving the hotas stick. I created a custom binding for the VR hand controllers using the steamVR settings, with a bear minimum of bindings -just the trigger and the grip. However, it still seme to be the left controller causing the problem. I see some of u are talking about axis bindings. Is there anywhere in DCS you can set bindings for pointing devices ?

thks guys. Good advice. A little surprising that ED have formal support in DCS for VRfree when it semes like the product is not mature enough for the market, and basically no where to be found. I´ve looked at some YT videos about Leap Motion and it looks like it has some limitations. Spesifically when u grab the hotas with your hands….. Since 2.8 my Vive VR hand controllers cause my hotas stick to act kinda crazy -flickering back and forth. So, I need to turn them off to be able to fly the jet, leaving me with the mouse to interact with the cockpit. This is a step backwards in realism and also very annoying. So, I have to find an alternative solution to the VR hand controllers to interact with the cockpit

Xmast is comming up and I wanted to treat myself with a pair of the Sensoryx VRfree consumer golvesystem for my F18 setup. However, I cant seme to find a shop which sells them. Can anyone help here ?

I have exactly the same issue with the Hornet. Makes VR unplayable. Using the mouse is just not the same as using hand controllers to interact with the cockpit. This happened after upgrading to 2.8. Any tips for resolution comes highly appreciated

This happened just after the upgrade to 2.8. When hand controllers are enabled in VR, the stick is flickering, and takes very intermediate and staggered input from my HOTAS stick. It is not possible to fly the plane using the HOTAS. When I disable hand controllers, the flickering stops and I can use my HOTAS stick just fine. This means that I have to change the way I am operating the cockpit from using the hand controllers, to using the mouse. This is a less realistic way of flying in VR, and also really annoying. My HOTAS is Thrustmaster Warthog stick base with a F18C Thrustmaster Stick. My VR is the VIVE PRO set

I have the exact same issue. It occured right after the upgrade to 2.8. When VR hand controllers are enabled, the stick is flickering and the input from my HOTAS stick is staggerd to an extent where it is not possible to manouver the plane. I have been using hand controllers in VR for a long time to operate buttons and switches. Now I have to start using the mouse, which is not realistic. So, If anyone have a fix for this, it would be much appreciated I use a Thurstmaster Warthog stick base, with a Thrustmaster F18C Hornet stick. My VR headset and controllers are the VIVE Pro set.

Thks for responding. After posting the problem, I re-installed the Steam open-beta-public version (I opted for the open beta, which did not let me start DCS, and then opted back to the open bete-public). This resolved the problem. Now the moduels are rendering properly. The vaicompro add-on also picks up the module radios, which it did not do before I re-installed the open-beta-public. So, my conclusion is that something must have been reset, when I did the re-install. Hopefully, this problem does not come back, as it prevents me from flying.

Hi I am running DCS Steam open beta / public version. DCS starts just fine, but my F-16C module does not render fully. Only parts of the plane is visual. The entire cockpit and front of the plan is just not there. I have tried to adjust the graphics parmeters, but nothing seemes to help. I run a i5-6400 2,7Ghz CPU, 32 MB RAM and a GTX 1070 Graphics card PS. I tried to put this post in the bugs and problems topic, but the cloud and weather topic was the only one available