Lange_666

For what I read, it seems that when starting DCS from the regular DCS desktop icon it now starts the MT version versus starting ST like it did before. (I use SkateZilla's updater/launcher where I have the option to launch either in ST or MT). To be sure you launch ST, just go to your DCS install location, in there you have a directory called bin and another bin-mt. The bin is ST, the bin-mt the MT version. Both contain a DCS.exe. Just go into each and create a shortcut from DCS.exe and put these on your desktop. Rename one DCS-ST and the other DCS-MT. This way you can launch either ST or MT and see the difference between the two. As Silverdevil says, the best thing to do if you want to use your old RAM, is to get exact the same specs (brand + RAM timings) as you have installed already. If you mix brands or use add a set with different timings you can easily run into problems. If you can't get them anymore, replace your old rams with new ones. Also, be sure how many RAM slots you have. RAM always comes in 2 pieces. If you only have a motherboard with 2 slots, you can only replace with new RAM. 16GB is on the edge these days for DCS. With settings too high I go over 16GB Ram on a simple mission, in VR multiplayer it uses even over 32GB.

Might be an option if my current Rift-S dies but I'm preferring one with a DP connection instead of wifi/USB-link.

RGB noise: Could be the cable Pico: Overall clarity is better but there are so many ghosting artifacts when the image moves quickly while using ASW. Without ASW at native refresh freq it was very good but it was difficult to keep the FPS above the native refresh freq on my setup (5800x3d+3080Ti). Once it dropped below that it started to stutter. And since ASW was so bad i did send it back. ASW also only worked with Virtual Desktop, with their own Streaming Assistant it even didn't. So i preferred a headset with less resolution but with a lot better overall performance.

Thats what i ment. Was more in an answer to YoYo because he's impatient...

Subject to change...

Rift-S (since that was what the topic was created for): I still use it (although on half the refresh rate through ASW). Think it's a good headset but i only have (had) a Pico 4 to compare it to and i prefer the Rift-S over the Pico simply because it has a display port. The Pico has too many artifacts when using ASW (or it's implementation of it) compared to the Rift-S. Biggest drawback for me of the Rift-S is the disconnection (not being recognized) each time the PC has been shutdown. So i need to un-plug / re-plug the USB each time after a PC restart. I had that also with my previous headset on my previous PC but there it would only disconnect 20% of the reboots and even then simply stopping and starting the Oculus service would make it re-connect. On this PC my first Rift-S never disconnected but my second one does disconnect each time and cycling the Oculus service doesn't do the trick with this one. So it's a bit headset depended.

They should also look into their device analyzer. In the previous version i still had the combined Warthog showing when a script was running. With this version nothing anymore, no single unit, no combined one but... it still picks up my MFG rudders...

Thanks for the info. Cool that I don't have to use the target128dx hack but it doesn't solve the above problem. This is how the latest Target version looks after it's started so that's not solved: I can drag the status window down and the script window to the left but after closing and restarting they are back in the same place as the screenshot below shows. Also, stopping a script still isn't instantly like in Windows 7, 8 and 10 but still varies up to 15 secs (in recent days i saw it stop once directly). According to Thrustmaster this is some sort of incompatibility of Windows 11. This update didn't solve that. I had the same behaviour as below after an update from Win 10 to 11 and also after a complete fresh install of Win 11 Pro.

OpenXR Toolkit: https://mbucchia.github.io/OpenXR-Toolkit/

Time to block the update of the non PTC version because when this bug enters the release version, we're screwed.

Yes but then you would see the shadows created by the cloud move rapidly as the cloud passes in front of the sun. Here it's like an extra cloud layer is added or shifted at once. This is visible to the left of the HUD when it happens.

A thing that annoys me quite a while now is cloud shifting and the effect it has on overall lighting. The effect is not always the same. The result of the cloud shift might be brighter (even a lot brighter than in the video) or a lot less bright or darker or sometimes in stages when more than one cloud shift happens. The next video says it all: the cloud shift happens at 0:19 in the video (just after the nose wheel lifts) when all of a sudden the entire area is a lot brighter lit by the sun.

No doc but here's a starter: 1: Right click in one of the Sim Build Slots and set the paths to your DCS installation (possible that the app does this automatic, can't remember). 2: Select a Preset which you want to launch (you can change these preset settings by selecting a preset, launch the game, set what you want and quit. Next time you select that preset, it will launch with your chosen settings). 3: Choose either Multi-Threading ON or OFF. 4: Hit either the top LAUNCH button to launch with your selected preset or hit either LAUNCH VR ON or LAUNCH VR OFF to launch DCS with your selected preset but with VR on or off. Tip: Don't touch Option Preset Editor for your presets. It will mess things up.

If you ever called the stuff that comes out of your water tap "water" (and i guess you do) then your point in this discussion is just silly. Drop it.

You can set (or could be already mandatory) Oculus to use OpenXR as runtime in the Oculus software under the General settings tab.

How does putting a Virpil stick on a Warthog base make it less stiff? It's the Warthog gimbal design that makes the setup stiff. Best way is to do it the other way around, Virpil base with the Warthog stick on it and you get a super smooth experience.

Because everybody will be reporting about the same version instead of possible multiple other older versions hanging around which could cause questions about things that are already solved. The "other sims" don't have the option to skip a version, multiplayer or not, so either you are at the latest version or you don't play. It keeps things tidy. The only drawback is that if there is a major bug introduced, there is no way to revert.

@4romeodelta: do you run DCS in MT in VR with OpenXR and with Turbo Mode turned on? Could cause a crash in DCS MT when the headset is taken off/or inside out tracking is lost. When it happens then the only way out is through Task Manager

Just wondering if the single DCS releases (future OB and stable unified versions) will be mandatory updates. Other sims are all mandatory these days.

Yes it does. Also, modern glasses can have all sorts of filters these days (at a cost off course).

If you can't get it working, you can contact TM support. In general they respond quite quickly.

To be found under: Virus & threat protection --> Virus & threat protection settings --> Manage settings --> Exclusions Just set the entire ED folder as exclusion.

You need to copy that input folder "from" the DCS.openbeta.BAK folder into the newly created DCS.openbeta folder (created by DCS when you ran DCS after renaming it to DCS.openbeta.BAK). The reason for copying only the Input folder is to have all your controllers back on how they were set up in your original DCS.openbeta. That way, you can test with your old inputs already configured. Now that this is done, run DCS again. It will run with a new, fresh default configuration besides the Inputs. This will rule out or point out if your problem sits inside the old SavedGames\DCS.openbeta folder.

I don't use Grmelin so i don't know. Didn't you try the 120DX hack for Target Script i sended over via PM?