Lange_666

Bit off-topic but on Rift-S: guess my Rift-S went to heaven, 2 days ago it came with a detection problem, since then the blue led on the front doesn't come on and i can't get past the sensor check. Tried about everthing i could find...

In the current one: This is what i do and what works, maybe there are other possibiliy's: Open updater / start DCS / set desired settings / close DCS / select App Settings tab in updater / under Custom Preset Names enter your preset name / press apply / repeat for next preset. Warning: Since 2.8 (i guess) there is a little problem when running the updater for the first time after the program has been closed, it will load default values for DCS (viewable in the last line of the log). On the second start of DCS when u select a preset it will load the correct one. To shortcut this behavior i open Task Manager, run updater, start DCS, it will load default values, the moment DCS shows up in Task Manager i kill the process, then restart again through the updater with the correct preset.

null

In DCS you have 3 different presets you can set and select with each his own settings. Drawback is that the latest used preset is loaded again next time whhen you run DCS. When you change to a new preset where one of the settings requires a restart, DCS will restart first to load that setting (like certain texture settings, VSync etc...). I will default to the latest used preset when you load DCS the next time. With the updater you can select a different preset before DCS runs. It will load that one instead of the previous used setup without the need to go through a restart (if needed). I use a high to ultra preset setting for single play, a medium one for online play and another one for VR.

It's normal that it shows up under Multi Media. Not normal you can't right click. But i never touched anything regarding my Warthog in here.

On my previous Intel motherboard I had problems with my VR headset being recognized when plugged into USB. With my current AMD X570 motherboard i still have to see the first disconnect of VR headset but i had the same problem with the Warthog when running a script. It would sometimes trow back the same error as you get: One of the selected USB devices has been unplugged. When it happened it always happened when running MSFS and always at the same point in the loading process. Looked at various solutions, none of which worked until i plugged both stick and throttle USB's to a USB-C splitter cable and then into my only USB-C port. Since then i didn't had any unplug message. What bugs me a little is that load of USB HID Device with hardware id xxxxxxx cannot be found messages. These are all each different devices. I don't have that, i only see devices that are recognized by Target.

Maybe of any help: https://www.reddit.com/r/hotas/comments/7lybgv/a_solution_to_thrustmaster_target_software_on_the/ https://www.reddit.com/r/hotas/comments/bf62bp/target_software_help_t1600m_hotas/

That's the solution to remove the stutter but don't you have little vertical black borders (left and right at the edge of your view) that flicker when you move your head rapidly?

If i remember correctly, Foxy is limited to 32 DX buttons, with Target and the 120 DX button script you can assign 120 DX buttons in total. Target isn't that complex, it just look like it if you're not familiar with code but in the end it does the same as Foxy, just differently written. I start off with a basic script which already has every button in it + a group of actions/buttons/axis controls that i use the same for each module. The other are empty, nothing assigned so i just have to add the macro's (for more readability) for each button or layer. There's a little proggy that converts your entire control setup for a particular aircraft from HTML (a save option in DCS) to an entire macro list. Everything goes fairly quick once you get your initial setup done (but it's a bit of work yes).

This. If you un-tick Foldable View, the Load Profile and Save Profile As option become available.

Yup, it ain't IL-2 where you set everything for all the aircraft in one go. As Rudel said, each aircraft has it's own specific controls, however, a lot of them are equal like gear up/down/toggle and in general have the same bindings... You'll also find that modern aircraft use a slightly different name for certain controls then WW2 aircraft. But you don't need to set up everything in one go, just pause the sim if something is missing, get into controls, set up what you need and fly on.

Real cool stuff. One first question: After looking at the screenshots i see that in the presets "VR Headset" is present. Does that mean that the preset switches to this profile when VR has been used like in the old app? I found that always a bit confusing because i use 2 VR presets and after using one of then it defaulted always back to VR Headset.

It's not the first time that a new DCS beta release get flagged by your anti-virus. After encountering it for the first time, i've set Windows Defender not to scan DCS (+ every other installed sim) and saved/games folders. Been running like this ever since.

That is also there in 2D, i had mine reading 900 !!! constantly in 2D so i let go of my cap and set the maxFPS in the config file to 1000 just to see how far it would go. It jumped around the 200 mark. So that theoretic value is to be taken with a big grain of salt.

I went this road also, replacing my old trusty U2 modded Cougar 3 years ago. I bought a refurbished one directly from the TM webshop (they are sometimes available) at 60% of a new one. Coming from a U2 modded Cougar, the THWH stickbase was just a horrible experience (but better then original Cougar one). Tried a Sajah green spring + sanding and regreasing which helped a lot but still. Then went for the Virpil WarBRD base but used the Warthog base plate because it's a lot heavier and more stable then the Virpil starform base that comes with the WarBRD. Sold off my Warthog base without base plate (you need to drill new holes for the WarBRD base but the old ones are covered by the new base. And then the TARGET DX120 (not 128) mod makes it complete. The WarBRD gimbals are 100 times better then the TM ones!!!

Make your TrackIR profile a lot more aggressive, takes a while to get used to. DCS_Fast.xml

Under the BUY button on the P-51 page there is also a TRIAL button. This will give you a 14 day try-out option without buying. After that 14 days are gone, it will tell you to either to remove or buy the module when you load up DCS.

I just wonder how the theoretically FPS value is calculated or why that's even there in the first place. On my system i saw values going up to over 600. But when changing the MaxFPS value in the DCS config file to 900 instead of the limited 180, i only reached about 200.

Something else you might check: - In the controls section on the bottom right: Disable Hot Plug (so Enable should be visible !!!) - In the MISC. tab, be sure to deselect "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" This one can lead to some weird HOTAS inputs if ticked. If stuff doesn't work, backup your DCS Saved Games folder (under C:Users\Your Name\...), then delete it and let the game create a new one. Then check for double entry's and remove those that you don't need, some HOTAS axis will be double with your rudder, pick only airplane and start with that, set the axis you need, pick flight where the aircraft is already started and on the runway and check axis response. Should work, if not, you have an interference somewhere else.

They do.

I would def get a card with over 12GB of VRAM, my 3080Ti is always maxed out in VR (low res Rift-S), even in 2D on the more demanding maps like Syria or Marianas it reached 12GB easely even with almost no units moving around. Also, i have never been able to run DCS in VR stutter free when it's not on it's native display frequency or halved (by ASW). The slightest fluctuation in FPS always result in stuttering or rowing boat effect. So if mine would run at 32 FPS, i would switch back to 2D (my Rift-S runs 80Hz or 40 in ASW, but i always run DCS at 40 to keep the overhead to prevent stuttering).

It would be a lot easier if the OpenXR Toolkit should recognize the headset (Rift-S in this case) and set the start resolution values for that particular headset. Now it's just a set of numbers (or percentages) which makes no sense. + i guess OpenXR toolkit is not exactly written with Oculus in mind.

Thanks, running the update now...

Rift-S user here: Played around with the toolkit a bit on previous DCS versions and now in latest ST and MT versions. Honestly, i don't see any benefit of using it over OTT.

Q: Anybody using a Rift S updated to v50 of the software already? If so... any problems lurking around?