Lange_666

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.

I normally don't do an upgrade but a new full install. Ain't got the time in the next few weeks to spend much "continuous" time behind the screen (once i start i want to finish it until i'm satisfied) so went for an upgrade but just like previous attempts on previous Windows versions, upgrades had have some minor issues compared to fresh installs. Should have known better from my past experience.

No track yet since it doesn't happen anymore (for now). The only difference is that i reverted back to Win 10 Pro after upgrading to Win 11 Pro a few days before. The mission was made just before the upgrade still under Win 10 Pro. Since i reverted back to Win 10 Pro the AI SU-27 didn't crash once one multiple tries...

I do the same as Fisherman82. I center while in the hangar, then re-center once I'm in the aircraft (most of the time the view then shifts a bit compared to the hangar viewpoint) and depending on the aircraft, i move the camera a bit.

Right after the Rift-S was released the Oculus forum was flooded with connection problems. Main solution: pull the USB and re-connect. Other solutions where using a PCI USB card etc... My first Rift-S (on my old computer, i7 4770K and Asrock MB) had the same problem, it would only be recognized after a boot for only 20% of the time. Putting in a USB 3.0 PCI express card solved that for 90%. For the remaining 10%, pulling the USB connection wasn't really needed, just stopping and re-starting the Oculus service would always reconnect the headset. New computer (5800X3D on a Gigabyte MB) solved all of these Rift-S connection problems. Headset was recognized directly "each time" and no extra USB PCI card was used. Then my 1st Rift-S died and i got another one (a used one). However, this one never connects after boot and also the stop/re-start of the Oculus service doesn't make the headset connect. The only way to make it connect is disconnecting the USB and reconnect it. Then the Rift-S is connected and stays connected until the next reboot except if i close Oculus software (Oculus service keeps running). If re-open the Oculus software, it still shows the Rift-S as connected but it doesn't in reality (in Device Manager one of Rift-S USB entry's changed from R-ft-S to Unknown). Tried to use a powered hub on which i can switch on/off the USB's but that doesn't work either. It needs to be a USB port directly connected to the MB. So why the difference between both headsets?

Decided to upgrade to Win 11 Pro (coming from Win 10 Pro). There's quite some stuff i like in 11 compared to 10 and some i don't but overall it ran pretty good except for 4 things: Rift-S: - Often a little bit of lag in my Rift-S when turning my head. Didn't need to turn my head quickly for that. Happened in every VR environment, also in the Oculus world. Sometimes there was no lag at all. In Windows: - Sometimes input lag from Mouse/Keyboard in Windows and therefore also in DCS when using my HOTAS when pressing a button and then sends out keyboard strokes. In general it was fine but had it happen 3 times without finding out why. - Stopping a Target script took always some time, starting was fine, stopping a script required +/- 10 seconds In Win 10 stopping a script was just an eye blink.. Re-install of Target software didn't solve it. - ExplorerPatcher to give more control over the taskbar messed some stuff up in the Taskbar, like not being able to use the Start button or the search function. Searched quite a bit for the culprit of this but didn't find anything to solve it. Removed ExplorerPatcher, after that all fine again. Made me think of either installing Win 11 Pro from scratch (which i normally do) but i don't have the time right now to re-install and setting up everything (there's a lot more then just Windows and DCS) or revert back to Win 10 Pro. Ended up reverting back to Win 10 Pro. All 4 mentioned problems gone, no more input lag, no more lag in the Rift-S, stopping a Target script is done in an eye blink again. Staying on Windows 10 Pro for now. Q: Are there Rift-S users who run Windows 11 without any display lag and is it a fresh install or an upgrade?

I'll post one as soon as i remember to save one because i always forget to do so since tracks before 2.9 were... well... broken.

2.9 Open Beta: When i fly offline i do this either as a weapons training to get familiar with the aircraft's weapon systems but mostly i fly online. The last few days i wanted to dig a bit deeper in Air to Air BVR combat with the F-18, because honestly, i just suck at this. Made a simple 1 vs 1 against a SU-27 on the Nevada map. The AI SU-27 is set to "ACE" (tried other settings with the same result). Both aircraft start opposite one another out at +/- 20.000 feet and 80nm distance which gives me the time to set the weapons and radar up. The SU-27 mostly goes up to 36.000 feet after a while but once its starts maneuvering after i fire some missiles, it will often (1/2) make a dive turn and then fly's straight into the ground well before any missile has reached the target. There's plenty of room to make a decent dive tough This just destroys gameplay...

A complete changelog of all versions and there versionnumbers can be found here (OpenBeta first in the list, Stable more down). https://www.digitalcombatsimulator.com/en/news/changelog/ PS: SkateZilla's app is a must imo, makes DCS life very easy, even so if the new version still contains quite a few bugs.

^^^^^ this. It gives you a headset with a display port so you don't have to "fight" the setup over airlink (wifi) or cable (USB).

If i'm correct, running DCS from the DCS shortcut launches DCS_Updater.exe (to be found in your install directory in de bin folder) which will offer to update your current DCS version to the latest. If you have Open Beta installed, you can already enjoy 2.9, you can have both Open Beta and Stable installed if you want. Personally, i use SkateZilla's updater/launcher utility which besides launching and updating offers a lot more options to launch DCS. Can be used with both Open Beta and Stable.

@Rayzer TrackIR: Will give you the option to look around more quickly but depending on the profile used (an aggressive one) you could ending up chasing the mouse if you need to click on something. Can be annoying but a headtracker is a must. Reversing an axis is done in "Axis Tune" on the bottom of the DCS controls for that particular aircraft (check that you are editing the correct aircraft). Docs: you could use Chuck's Guides to start, it will come with a lot of pictures showing where to find those controls/switches/buttons in the cockpits.

Updated from Win 10 Pro to Win 11 Pro. Normally i install such an "upgrade" clean from scratch but i don't have the time right now so i just followed the upgrade path for the time being. Works fine in general just getting used to the differences... But one thing that i noticed bugs me a bit and that is the stopping time when stopping a script running in Target Script. In Win 10 it stopped instantaneous when hitting the stop button, in Win 11 it takes up 5 to 10 seconds before the "Script stopped!" message appears and the script stops running. While this is happening, Target software freezes until the "Script stopped!" appears. Anybody any clue's?

Yeah but then you are using "new" technologies like G-Sync "and" fast V-Sync to "solve the problem which initiates in TrackIR in the first place. Those who don't have a G-Sync are still left with the problem so it still exist as to today. And it IS the root cause and i'm 200% sure if i come and watch your setup in a non G-Sync environment i still would see the problem. BTW: i still prefer a fixed FPS V-Synced FPS over any fluctuating FPS anytime. It's just A LOT SMOOTHER then fluctuating FPS all over the place.

Because it never did, not in 2.7 nor in any other version. Same goes for MSFS and IL-2, they suffer from the same problem. The issue has been around since TrackIR exist, the only solution is to sync your frames with the TrackIR pull rate (or a division of it).

Also, it might be easier to search for that lost FPS window in 2D rather then in VR.

Using the search option (on top of the page) for this topic reduces those 110 pages to 3. Still to much?