Lange_666

Target Device Analyzer: When no script is running i have bot the stick and the throttle as separate devices in the Target Device Analyzer. However, seeing some pictures where the Thrustmaster combined shows in the (when a script is running) Target Device Analyzer, i wonder what setting needs to be set to get that combined device in the Target Device Analyzer, i don't have that (i do have other devices in there like the MFG rudders)?

In general no. Sometimes stable is updated to the latest beta and then for a short period they share the same version number which then allows you to connect to players on both versions but in general, open beta only connects to open beta and stable only to stable.

Does DCS run in 2D?

I would try with a complete empty script (all buttons and switches commented out "//") and just both TG1 and 2 programmed to be sure nothing make things go belly up further down the road in the script.

Did you set the correct path to your DCS installation on the App Settings tab? On the same tab: what are your VR Interface Settings? Looking at your log DCS started in VR and it detects your Oculus Rift S so it should work: Can it be that you have set up Guardian on another spot/place then the one you sit in when you run DCS? Because if i do that, your headset will show DCS within the Guardian boundary you have set up and you might not see it when you sit behind your desk. If this is not the case, what do you see if you just run the Oculus software (don't run DCS) and put on the headset?

No. Oculus software must be running and set up. Unknown sources in the Oculus software must be set to on. In DCS settings under the VR tab, "Enable Virtual Reality Headset" must be ticked After you have done that, you need to restart DCS to make the switch to VR mode. That's all. Tip: Use Skatezilla's updater utility to make an easy switch between 2D and VR (and vice versa).

Works fine on mine: TG2 Out returns Space TG1 Out returns nothing (0) TG1 In returns R_SHIFT P just fine.

Taking it apart is not difficult, lot's of tube video's on the subject. Could be that the Y-hall sensor has become a bit loose, just a guess.

Ehm? My OpenBeta exe is called DCS.exe and not openbeta.exe. Looking at your responses, i guess you don't seem to get the idea behind ED's Open Beta and Stable versions.

But since yesterday afternoon not anymore. Open Beta progressed to the next level, it has been updated to 2.7.6.12852.

Deleting (make a backup first) the Input folder in the Saved Games folder ( C:\Users\Your Name\Saved Games\DCS\Config\Input) and let DCS create a new one?

Once this is done, no need for the Virpil software again.

BTW: Stable and Open Beta are on the same version right now (2.7.5.10896).

When it comes down to the gimbals (the part that makes the joystick move), VKB/Virpil are lightyears (!!!) ahead of Thrustmaster.

What if you leave Rendering Type and Rendering Size empty?

I guess with a PULSE to generate one action to uncage and one to cage. If you don't pulse it will generate pulses as long as it's pressed at the in the script defined rates (standard SetKBRate(25, 35); ). You can either push the China Hat forward to uncage and backwards to cage or combine both on one button. First time you press it it will uncage, second time it will cage. Would be something like this: //MapKey( &Throttle, CHF, SEQ(PULSE+UnCage, PULSE+Cage)); or use the shift statement to combine both action on the same button. press China Hat Forward to UnCage and press S4 (or whatever is defined as the shift button)+China Hat Forward to Cage. //MapKeyIO( &Throttle, CHF, PULSE+Cage, PULSE+UnCage); There are other options to if needed. Edit: I just saw that Cage/UnCage is just one button all together. In that case: //MapKey( &Throttle, CHF, PULSE+Cage-UnCage); // Replace Cage-UnCage with whatever DX button you have there.

Post a screenshot of your ingame audio settings if you which, it's easier for us.

So the 3080ti should have gotten 16GB instead of 12?

Change the standard springs with the provided heavier ones, it's a lot better.

Mapkey( &Throttle, IDLERON, PULSE+DX87); PULSE in capital letters

Honestly, just to get some VR going, needing to run WMR for Windows, WMR for Steam, SteamVR and the bulk of Steam settings and upscaling and downscaling and what not other crap is not the road to go if you ask me. No G2 or one of those WMR/Steam headsets for me, just way too much hassle. I'll stick with my Rift S.

For me it doesn't work either, when i enter a cockpit, first thing i do is reset the camera view and then adjust the cockpit camera view according to my liking. It changes for each aircraft. Saving these views never worked.

I use the INCR / DECR axis on my Warthog throttle for that. It works as a full zoom Axis in 2D and as a range "button" axis in VR. This way i can use the same function for both. In VR when the axis has a value below 50 , there is no zoom, when it reaches 50% it activates VR Zoom and it stays there until it reaches between 90% and 100% axis range, then it goes Spyglass Zoom (and back offcourse), works nice.

This one was one of the most disappointing flightsims i ever bought.

NP, just have fun...