Lange_666

For those who use/need WMR: https://www.ghacks.net/2023/12/21/windows-mixed-reality-is-history/

Home tab, select a build sim slot, right click on it.

BTW, the topic title talks about the Rift (S) in DCS. For Quest headsets there are other topics.

Don't use the preset editor for setting presets. Use the presets on the main Home tab. Select a preset, start DCS, set it the way you want for triple monitors, close DCS, your setup is now saved to that preset which you can now also give a name you want. Select another one, start DCS again, set it the way you want again for VR, close DCS, your setup is now saved to that preset, rename. Etc...

I didn't want to troll and i also did read that AMD CPU's are more prone to problems after the 2.9 release but i guess if someone post a message that there are problems and then point out that it's an AMD CPU problem, certainly if it's in the topic title, only AMD users will jump into that topic making it look like AMD CPU's are the real problem. But if you start searching a bit into the 2.9 problems and then look at people's specs you'll find that there are also a lot of Intel users with the same problems. So...? If its really really an AMD CPU problem, what does it cause for you that it doesn't cause for me? Clearly something else must be the problem since i don't have the same issues. And i really have a smooth ride (and smooth for me means smoooooth). I've also seen the Task Manager screen shots where people CPU's one or more cores go to 100% utilisation and then say, hey that's my problem. Well, I have that to but it isn't causing any trouble here so is it really an AMD CPU problem (i doubt it)? The below screenshot is DCS in MT with high to very high settings but CPU hyperthreading OFF (with it ON i don't see different performance wise in DCS but MSFS runs better imho with it turned off so i leave it off).

Running a 5800X3D and i have a smooth experience under 2.9, both MT and ST.

Cinebench perhaps? https://www.maxon.net/en/cinebench

For me when the new version came out, i used the preset editor to make my presets but somehow i never got it to work and always had issues with it. Up until today i don't know what the meaning of the preset editor really is. Even if i select the preset editor tab and don't change anything in there, upon selecting another tab i get a pop-up telling that i have to save the changed settings....? So to get my presets working on the main tab, i did +/- what MAXsenna did (except copying the options.lua each time), select a preset, start DCS, make the changes, close DCS and then rename that preset and then on to the next. Works just fine and i didn't touched the preset editor since.

I know about the icon but i never thought about the "somebody reacted to" as it being a like or thanks. If it's a written post then it's always with a name of the poster. Not that i care about likes and thanks anyway.

It's set like i want already long time ago. Didn't think about likes and thanks as being a notification

I have the "push notifications" set to OFF (i don't need to notified with every post made and certainly not on "other devices"). Q: Isn't it enough to just say NO to the question to not be annoyed anymore later on. Why does that question needs to be repeated after an x number of days? No is NO and OFF is OFF.

When i get "somebody reacted to post" notification there is never a new post (or i must have been inactive for a long time). This sort of notification can also show up on posts that are more then a few days old. Real notifications always show the name of the poster or when there are more posters in a fast sequence, i get posted by X, Y , Z and a few others. The "somebody reacted to a post" for me is a bug in the forum.

It's version 2 currently which is still under development and still contains a few bugs mostly for the extra options you can use but the main part of the utility is working just fine.

FC F-15C: TDC Slew Horizontal and TDC Slew Vertical.

Yes, most modules also have an axis control for the radar cursor. Examples: F-18C: Throttle Designator Controller - Horizontal Axis Throttle Designator Controller - Vertical Axis F-16: RDR Cursor Switch - Y-Axis RDR Cursor Switch - X-Axis You can assign one of the XBox analog sticks to these controls.

But that shouldn't keep @JT Animal from using it for the throttle in F-18.

If using Target Script you can adjust the Throttle response by the press of a button through SetSCurve, SetJCurve or SetCustomCurve commands. (btw, that's how, for example, the F-16 works, the moment you open the refuel door, the HOTAS inputs differ from when the refuel door is closed)

That's the way i launch DCS every time. I never use the big Launch button.

I reverted back to Win10 Pro already because i also had a few other anomalies, sometimes input lag (mouse/keyboard/HOTAS buttons), a little 1 vs 1 BVR mission that i created to train some BVR resulted often in a crash of the AI SU-27 by diving into the ground, the Target problem etc... Since i reverted back to Win 10, stopping a Target script has no delay anymore, the AI SU-27 doesn't dive into the ground (not once), no more input lag. Next i'll do is a clean install instead of an upgrade. Must say that in the past each time i "upgraded" Windows to another version it made me clean install it later because it never felt really smooth. Same with this one.

Here the only thing that gets unchecked after closing the Updater is Launch External Apps with Sim, all the rest that i have checked stays checked. But... when i check Launch External Apps with Sim and launch the sim, none of my checked app launch together or before the sim.

Since the latest 2.9 DCS version (2.9.1.48111) i don't have stutter anymore in MT VR so i don't need Turbo mode anymore.

Yep, did that back then without success.

After installing the latest version 3.0.23.608 (which includes F-16 Throttle) none of my scripts would compile and would always come with an error: Compile Error: Identifier name expected in targetdx128.tmh at line 883 It's the first line where the extra DX buttons (above 32) are defined. I just replaced the defines.tmh, sys.tmh and hid.tmh files with those from a previous version 3.0.20.826 and then it worked again. Actually, both sys.tmh and hid.tmh don't need to be replaced because they are the same as the previous version but defines.tmh differs (i guess because the F-16 Throttle also goes beyond the standard 32 DX buttons per device). Solution: just replace the new defines.tmh with the the old one. I'll drop that old one here: defines.tmh

But i guess that setting it from axis to slider will not cure the problem because i never have set any axis to a slider, let it be throttle, rudder or zoom and i never seen that effect. And they work just fine set as axis. I think more of a pinched wire inside the throttle, it would not be the first one.

I wonder if the same effect (odd shimmering/ghosting when rolling the plane on distant objects) is also there on Q2/Q3/Q-Pro headsets (it's not there on a Rift-S but that has a Display Port) because it's the main reason why i returned the Pico 4.