Lange_666

The dreadful time bug... (which isn't really a bug). Mentioned x-times all through the forum... first thing to look at when authorization fails.

If you want to do more then just assigning a button to a function then you need more then just the ingame configuration option (hence you used Foxy before to do that). Several option if you don't want to use T.A.R.G.E.T like Joystick Gremlin https://whitemagic.github.io/JoystickGremlin/ T.A.R.G.E.T looks difficult but really isn't, if you could do Foxy, you can do T.A.R.G.E.T also (you don't really need to know how to program even if at first it looks like you need to). You could go the simple road and use the T.A.R.G.E.T GUI option to program your HOTAS needs. Or you could use T.A.R.G.E.T Script, looks difficult but if you follow the manual, you'll see it's not, just go step by step, take your time to read through the manual and try the examples (both GUI and script version don't work side by side). + one big advantage is that there is a mod to use 120DX buttons instead the regular 32. Could come in handy. Lots of stuff to be found here: https://forum.dcs.world/forum/336-thrustmaster/

Lots of info can be found in de VR section of this forum. https://forum.dcs.world/forum/302-virtual-reality/

I only have one build (OB) so the preset behavior between builds should not be a problem in my case. But it still loads the default preset on each first start of the app, whatever preset is selected, previously or new. On the second run, the correct preset is used.

This is the behavior i'm talking about, never seen that before 2.8.x Just try to select it like that yourself, impossible.

Off topic: that last one doesn't count for everybody.

I never had a problem with the previously selected build or preset until DCS 2.8.x came out. Since then, whenever the app is launched, in case of the presets, there are always 2 presets selected (which you can't do yourself), the default one and the previous used one. Even if you de-select and re-select your wanted preset, the app always launches with the default settings when used the first time after launch. Either you sit through the DCS launch, quit DCS and re-launch or use the task manager to kill the DCS process, re-select the preset in the app and then it's OK. But i guess the initial problem lays in DCS 2.7.x --> 2.8.x and not in the app because the app wasn't updated anymore since 2.7.x and it used to work just fine with that version.

Time to put a lid on this topic. It would be nice if the topic starter (me) could lock it so you children could go fight somewhere else.

You'll be able to piss a bit further... If this will be far enough will depend on your expectations.

This means that each mission created before the update, even those delivered standard with DCS over the years, is having this problem. Isn't it up to ED to correct that in one single go instead of us opening each mission, select a new preset and save again? Or is that part of the "fun"?

So if i understand this correctly, SteamVR is mandatory?

Just drill 4 new holes for the Virpil base in the Warthog plate, the Virpil base will cover the old holes so you don't see them.

It's BIG indeed, new pilot body for the F-18C.

20 days to 1st march, just sit it out and go flying...

The first one is a work around which loads default settings (at my end). If i then select my VR settings (preset 3) then the game needs to reload. If one switches a lot between 2D and VR the settings that are loaded are always depending on the previous run. It should be selectable in game without a restart. We have a tickbox but here the same problem as above exists. SkateZilla's app does wonders to overcome the problem but since 2.8.x (2.7.x was fine) there's a little quirk that makes it load default settings at first startup (after a reboot) even when another preset is selected. Sometimes even 2 presets in the app are selected which is not possible to do yourself.

Mmm, there is an option in the System tab where you can set the scale of the GUI. But the default setting is 1 and you can set it only higher then that (up to 2 in steps of 0.25). Mayby by accident changed that to a lower value directly in the options.lua (or in one of your presets?) Options.lua to be found in C:\Users\YourName\Saved Games\DCS.openbeta\Config Look for: ["scaleGui"] = 1,

Easy-peasy, just make a copy of the beta, put it somewhere and update/revert that copy back to the stable version. Create a shortcut to the DCS.exe in the bin folder and you have 2 versions side by side. Nothing more to it.

With this utility, you make (and launch) every version you want.

Here it didn't, that was the first thing i tried and it didn't work. + restart of the game (from desktop) or full PC reboot should act a rescan of TrackIR which it didn't.

The gimbals of WW, Virpil and VKB are in a league of there own compared to what TM has to offer. Their Cougar gimbals where just nothing but crap (i replaced mine with an Ubermod as soon as got the possibility), the overall idea for the Warthog is better but there is just way to much friction on the plastic parts compared to the latest designs the competition uses. And those that say they have no friction or that it doesn't bother them have never laid their hands on a stick with one of those gimbals.

I see that they have an extension set including different springs: https://wwsimstore.com/view/goods-details.html?id=370 It also includes a dampening device. Or find a spring supplier which has something similar (same size, but heavier) on offer.

Found a bit more. I have 4 selfmade profiles, FPS-Test, Offline, Online and VR. Even when one of these profiles is set (from the previous session) in the select profile option, DCS still loaded default settings. Then i found that it happens when 2 profiles are selected at the same time. This is something you can't do yourself but when the app is started, the Default profile is sometimes added. Even if you see your preset selected, if the Default preset is also active at the same time, it will load the Default one. Happens only since one of the latest DCS updates.

This is my command line in the DCS icon: "E:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR

Unless you win...

Yes, stuttering (can be, depending on the export script, some of these are rather long and take up time, causing stutter). I have only profiles on which DCS only receives input from the Streamdeck, not the other way around (like for flap positions, rpm read-out etc...). With one direction StreamDeck ---> DCS, no problems or FPS drops. UFC use is a good example of this, works just fine, no hick-ups.