Lange_666

I just checked your (latest) DCS log file again. I see FPS is set to 300 and VSync is OFF. You can leave the FPS at 300 in game (but since your monitor has a max refresh of 180, i would set that to 180) and set VSync to ON and set an "FPS cap" in the nVidia Control Panel (NCC) to 120 if you are sure you can maintain that all the way through or 60 if not. Also, did you set up G-Sync in the NCC? If yes, turn that off. Next, you can play around with the monitors refresh rate if you want, i have a 144Hz capable monitor but i set it to 120Hz to be at the same poll rate as TrackIR. I also set an FPS cap of 60 so that's exactly half the refresh rate of my monitor which gives 120-60-40-30 if divided by 2-3-4, otherwise it would be 144-72-36-18 which doesn't match the poll rate of the TrackIR. In your case with a monitor at 180 this would be 180-90-45. Worth a shot. And please record a video while panning so we can see what you see. Options: Do you have a webcam lying around? You can try that with Opentrack instead of TrackIR. There are also options to use a cell phone for tracking, just roam the internet for info.

Depending on what those "jobs" are, but in general you won't notice if your browser opens 0.01 second slower. I would keep that 250€ in my pocket and use it for something else.

Just ran a little test, no problem here (2.3.2.2). Radio's are populated in the overlays just fine and they work.

Personally (<--) i would not go 4K on a less than 32" monitor. Single pixels are way too small on a 27" and when visually searching for the enemy when no labels are used...

That's always a point of discussion. For some games they recommend it to be turned on, for some to be turned off. That you have to go into the BIOS makes it even more problematic.

The tech tubers just copy one another to get their own views up.

https://forum.dcs.world/topic/381300-dcs-shutdown-time/#comment-5714666

Tacview is certainly the culprit for the difference between smooth panning while playing in game and some stuttery panning while playing a recording. I just commented out the Tacview entry in the export.lua and the induced stutter while panning in a recording is gone. Re-enabling Tacview and it's there again. Also, as escaner points out, when FPS is not stable (on the monitors refresh rate (or a division of it)), TrackIR can induce some extra stutter.

I don't think a replay is fully representative compared to what you get in game. I recorded a few tracks to post here but i didn't because during gameplay it was all fine but when viewing my own recordings i saw a lot of stutter when panning during replay that wasn't there while recording. Also, slow panning is fine, fast panning shows a bit of stutter when playing your tracks and if i compare that to mine with a very aggressive curve setting, the more it becomes visible. The moment i took control while playing the track, the stutter vanished. Why that is i don't know (yet). Same happens with other peoples tracks. So i see no real difference when i compare your track with mine. Also, tracks are not representative since they are recorded on one system and then played on another with completely different specs. The best way to compare is not a track but a video made while playing.

I did a short search on audio (cards) and FPS stuttering but the results i looked at all talk about audio stuttering which is not what you are after. Even AI generated results are beside the point and are close to complete bull regarding this issue. If i have some spare time later on i will dive a bit deeper and see if i can find anything.

I would focus on this.

Still on version Meta 66.0.0.308.370 (on Win 11 Pro 25H2) here but since that latest DCS updates I notice also more irregular hick-ups using my Rift-S while playing, especially more in multiplayer. 3080Ti with driver 576.28. No DLSS or DLAA here, I prefer the shimmering over the ghosting.

1,207 TB. Since I have DCS on a 1TB drive, and when updating it needs installation space, I moved around 600GB (less used stuff) to 2 other drives using symbolic links. Works fine.

The black screen only appears in 2D, in VR it's not there. Also, if you bring up the ingame FPS counter (and game data) and leave it active while exiting, it's still displayed as long as the black screen is visible.

^^^^ Only possible within the European Union if i'm correctly informed and only with an active MS account. Outside the EU you can extend it too for 30$ (yeah right).

Good idea although i don't know how it is in real life. But in the sim, with max trim input at the moment on the reset, it can be very brutal, resulting in a very brutal pull-up or dive. Can't imagine it's like that in reality.

SkateZilla's one, just one icon for everything.

It's a lot closer to reality now in VR instead of the 2D version where it's more on/off. A lot of people want their sim to be as close to reality as it can get until they are annoyed by something and then all of a sudden it's not so needed any more. This ^^^^

You can't turn it off, not for the F-16 either. You can only move it up down. In 2D you get a clear view with either the visor up or down, makes it look like you can turn it on/off. In VR it's different. Topic poster is talking about the VR implementation where, unlike in 2D, you can see the edges of the visor, the nose gap and the fixation on top of the helmet. Depending on how the different headsets visualize this, it can be distracting.

Rift-S user here. For me it's just fine, it's a small gap (unlike the screenshot in the first post). The only thing that's distracting a little bit for now is the fact when moving my head from left to right (or vice versa) the small gap becomes a bit more noticeable, but not bigger, only more pronounced, in the direction i look and less noticeable in the direction i don't look which makes it "switch" a bit.

Did you try each RAM module one by one? Still error 55?

Did it boot properly after the BIOS update? If no, did the BIOS update went OK? If not, look no further than that because upgrading to Win11 before let you boot and play (although with performance issues). If you can't get into the BIOS clear the CMOS either through a jumper or by pulling out the battery. Still error 55 after that, as provided above, check RAM seatings and or faulty modules.

Kinda drastic solution if you ask me. You will probably end up with the same problem as you have now, spend quite a bit of money for no solution. I to have quite some stutters lately when in MP, mostly in VR where before it was as good as stutter free.

In the comments on the DCS User files of Thrustmaster Combined Full DX Mapping there is a post with the same error but with no solution. Digging a bit deeper into the internet cave i came across what you already tried (in white). But there's a bit more below where I found that "solution": ----------------------------------------------------- You should explain people what it does. It prevent the pc to turn on/off the device for power saving. It can be a reason for this error message. But most of the time it's because we install driver and Target in the incorrect order. Driver must be installed first, then we MUST disconnect all Target compatible peripheral before installing Target. Should be ok now. (It can also be due to the Teamspeak 3 joystick plugin. I had to delete it). If you read the ThrustMaster TARGET release note, it is said it is a must. Warning Unplug all T.A.R.G.E.T-compatible controllers before proceeding with installation. When prompted to reboot after installation, plug each controller again. If we install TARGET with controller plugged in, it will take a long time to install filter, and controller will not hide when we run a script. Must reinstall properly after having made this error. Many people do it. As we have to plug our controller to install the driver.. And.. We rarely read release note. ----------------------------------------------------- Another one: What I did to remedy this. 1. Unplug joystick and uninstall Drivers, then TARGET 2 Deleted all Thrustmaster folders in >Program Files, Program files x86, and Users\UserName\AppData\Roaming 3 Went to Device Manager>View> show hidden devices 4 (make sure at this point al your regular USB devices such as phones, printers and headphones are connected to USB) DO NOT CONNECT your Thrustmaster device 5 Right clicked and uninstalled all greyed out Universal Serial Bus controllers, Human Interface Devices. ( for a good measure look through other categories to make sure there isn't a greyed out Thrustmaster device somewhere there) 6 Restarted the PC 7 Plugged in my joystick and let Windows install drivers. I did not install drivers from thrustmeter support downloads. What that changed is that now my joystick is displayed as a Thrustmaster Virtual Game Controller (root) : Status OK. Instead of T.16000m FCS : Status OK. 8 Installed TARGET --------------------------------------------------------- This one above is different because in step 7 and 8 he's plugging in his joystick before installing Target which should not be done according to the release note. --------------------------------------------------------- Also,my own encounter with this problem (at that time with the Target Gui which returns the same error): PS: The solved not 100% points to the device analyzer problem where devices don't show up, nothing to do the internal error. To remove the "USB HID device with hardware ID cannot be found" message when compiled I edited target.tmh and commented out the Thrustmaster devices i don't have (this was not needed on older target.tmh versions). If you can't solve it, you can contact TM support through their website. It can take a few days before they respond but I always got an answer and they go through until you have a solution.

Onboard graphics card on the motherboard? If yes, disable it in the BIOS and be sure to plug the monitor cable in the correct port (that of the RX 9070 XT)