datman34

OK so complete reinstall following instructions. Note that Open Composite was set to steam vr. Steam vr did not have the app running, that I could see. I think the issue was related to steam somehow taking control and I think there were conflicts. After I got it running. In the mirror I could see movement if I moved the headset. But the headset only displayed black. I read on the forums about a file called D3DCompilier_47.dll. Yup it was there. Deleted it and BAM worked like a dream. Thanks for the help. Now excuse me I gotta go learn how not to die when taking off in a P-51.

Hello. I am looking for some assistance. I have been searching for a few days now. I have found nothing. Some background: I use a reverb G2. I updated all software a week or so ago. I am not running the beta. OpenXR works great for MSFS 2020. DCS work with steam vr. The issue: I start up with headset plugged in. I launch WMR and check to see if open xr is working. I start up DCS. WMR recognizes that I am launching a VR app as I have the 4 little balls moving around. I can hear DCS once it starts. Nothing but the 4 balls in the headset. On my monitor I can see DCS has loaded in VR. I can move headset around and nothing moves in DCS but does move in WMR. Note that last week DCS worked fine. Also nothing new has been installed since last working. I have tried uninstalling and re-installing. I have tried to repair DCS. I shut down most apps not needed. Nothing works. Any assistance would be awesome. Of course, worse comes to worse I can just use steam VR. UGGGGGGHHHHHH!

An update. OMG what a difference. So happy now.

I am super looking forward to next level simulation.

Well, that might explain some weird behavior I have had with throttle controls in the past. And Thanks

I did not use windows to set up my TPR. Learned that years ago. I play in simulator only and thus setup the non-game mode. A question about sliders for the TPR, do I need to do that in other modules? How about the throttle?

I never messed axis tuning. My controls work wonderfully in IL-2 and MSFS2020, And thus, no need to tune. Well it goes to show that what works in one place may not work in another. Of course I cannot test it out until after work. Man this day is gonna drag.

I will change the toe nreaks and throttle to sliders. And thank you so much for helping. I should prob make friends with a knowledgeable pilot and get tutored the right way instead of banging my head. LOL

Sliders? I do not use any software to set up the controls. I go into the settings and select the F-16 sim and set them there. I select the action (such as left toe break) and then push the button or axis that I want (such as the left toe break on the TPR). I will have to check that out, As far as load out, I have exactly what is loaded when I do cold start. Are you saying go clean? I guess I just have to learn rudder and break controls better. Oh and I turn off parking breaks before moving. Still the issue of having to push throttle way up to get the aircraft moving. I am sure I am just missing something.

Sorry if this is in the wrong forum. Background first. I have DCS World through steam. I have a HP Reverb G2. I have a Thrustmaster Warthog and TPR mounted on a MonsterTech flight stand. I fly in VR and not Steam VR. All 3 controls are calibrated. All 3 appear fine inside DCS when in the control setup, Issues When flying the F-16 and taxing, I have issues with the following. The aircraft won't move unless I throttle very high (over 90%) Engaging the toe breaks does not stop the aircraft fully Reducing throttle to idle with toe break does not stop the aircraft When flying, the aircraft tends to roll with and without trim I checked the axis and see no fluctuations and thus do not set dead zones. The issue does not appear while in my A-10C II or my P-51. Also after I set the controls, the settings will switch to either different key binds or be removed. This happens in all modules. Some more than others. Example: P-51 I bind my rudder trim to the China hat. Come back and it is set to another binding or is gone. I am at my wits end. I have tried so many things and am at a loss. Please help.

An update: So I have the throttles mapped correctly all along. I do not know if the left engine for the A10 must be done first or not. I do left first now. The F16 I lock the 2 throttles together. I have learned to set the throttles out of idle cutoff before launching the mission. Before I click start mission , I move them into idle cutoff. Then everything is good from that point. Only thing I can think of is possibly one of the following. Hardware going bad? Computer going bad. USB hub going bad bad USB cable? software glitch I was doing it wrong I've had the warthog for 2.5 years. My TPR for about a year. My computer for 2. So could be anything. Oh well.

Thanks. I will try that out. It does appear that all my previous mappings have changed. Was it a recent update maybe? Been a little while since I have played.

So I have a ThrustMaster Warthog stick and throttle. I play in VR. When starting from cold dark I have to hit right shift and home to move it out of idle cutoff. I use to be able to just use the throttle. This is also true with A10. All my WWII aircraft do not require this. Am I missing something? Do I need to add some type of mapping? Please help. I cannot see my keyboard in VR. I do have a mouse.