Lange_666

Top... Can't find where I need to do that (Google doesn't play along this time). Does it refer to the C-State in the BIOS? If yes, I have it on AUTO. BTW, I didn't change any such setting in between the updates and when reverting back to 2.9.15. all is normal again so it must be something within DCS latest update. Also, FZG_Immel has an Intel CPU...

Logs attached: Updating to 2.9.16 adds +20°C to the CPU temp, in idle in the menu and in game during a mission. Reverting back to 2.9.15 reverts everything back to the temps I had before the update. Re-updating again to 2.9.16 adds the +20°C in back so there is clearly a problem somewhere. I'm going to stay at 2.9.15.9599.1 for the time being so reverted back again and the temps went down with 20°C. 2.9.15.dcs.log 2.9.16.dcs.log DxDiag.txt

Updated to 2.9.16.10523 yesterday and ran the game after the update. Directly noticed that my PC made quite a bit more noise than before the update when sitting in the main menu. Wasn't 100 % sure about the previous CPU temps and load but i guessed it was a lot lower. With the update to 2.9.16.10523, CPU temp was 77° and 44° CPU load. To be 100% sure i reverted back to 2.9.15.9599.1 and took some snapshots of the Afterburner values in the main menu. 2.9.15.9599.1: CPU temp: 52°C, CPU load 24% 2.9.16.10523: CPU temp: 74°C, CPU load 45% The same behaviour is also noticable in game where in 2.9.16.10523 things run a lot hotter. After reverted back to 2.9.15.9599.1 the lower temps and load were back to normal, after updating again to 2.9.16.10523 it was back to the hotter temps and higher loads.

This is an option: Pressing the S1 key (or whatever you want) will go through a sequence of 3 steps which each press moving on the next sequence. Step one will reduce the sensitivity of both X and Y axis and put LED 2 on as reminder in which sensitivity you're in. Next press of S1 will reduce sensitivity even more and will turn off LED 2 and turn on LED 4 to set a visual reminder of this sensitivity. Next press of S1 will return sensitivity back to normal and also will turn off LED 4. With no LED's turned on, it indicates that sensitivity is back into it's original state. MapKey(&Joystick, S1, SEQ( // (Change Stick Axis behaviour - open the sequence CHAIN( EXEC( // curve 1 reduced input "SetSCurve(&Joystick, JOYX, 0, 0, 0, 2, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 2, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) ), CHAIN( EXEC( // curve 2 even more reduced input "SetSCurve(&Joystick, JOYX, 0, 0, 0, 4, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 4, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2) ), CHAIN( EXEC( // reset to normal stick input "SetSCurve(&Joystick, JOYX, 0, 0, 0, 0, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 0, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) )), //close the Sequence

Yes there is: https://forum.dcs.world/forum/1315-dcs-cold-war-germany/

It's NOT normal. If it does there certainly is an issue while booting the first time.

I had set them both directly after the latest full PC install, according to a little list I made what should be excluded. I added TacView to that list because I did read that "it could" cause stuttering while recording/saving. I removed it again from the exclusions after posting my comment above just for testing purposes. I don't have stuttering with TacView when it's not excluded.

This has been a "possible" solution for stuttering issues since TacView came into play. However, I have it enabled and never had micro stuttering with it. Question then still remains: why some have micro stuttering with it enabled and why some have no micro stuttering at all with TacView enabled? Maybe because I have set TacView as exclusion in the Anti-Virus?

Haven't checked the mobo specs myself but does it have a diagnostic display (mostly 2x8-digit) where you can follow the boot process. If yes, you can follow the boot process and see what code is generated the moment the PC turns off again. With that code you can then (mostly) determine what's the cause?

This is what I use: I also use 2 of the 5 leds on the throttle base to visualize in which state the curves are. SEQ( // (OU) Change Stick Axis behaviour - open the sequence CHAIN( EXEC( // curve 1 reduced input "SetSCurve(&Joystick, JOYX, 0, 0, 0, 2, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 2, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) ), CHAIN( EXEC( // curve 2 even more reduced input "SetSCurve(&Joystick, JOYX, 0, 0, 0, 4, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0, 4, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2) ), CHAIN( EXEC( // reset to normal stick input "SetSCurve(&Joystick, JOYX, 0, 0, 0 ,0, 0); SetSCurve(&Joystick, JOYY, 0, 0, 0 ,0, 0);" ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4) )), //close the Sequence

If you want normal curves for regular flying and additional curves for refueling you can use Target and set additional curves with the press of a button, another press will then revert back to your original curves.

10GB at mission start (Free Flight), taking a dip 5-10 secs into the mission to 6.9 GB, then fluctuates between 6.9 and 7.4 GB. Reserved VRAM 11.3 GB out of 12 GB.

Mmm, F-16 Free Flight Afghanistan (2D). Res: 2560x1440, overall high to medium settings, FPS capped at 60. 30 seconds into the free flight mission I get this: VRAM: 10+GB, 2 minutes into the flight and it maxes out at just under 12GB, my VRAM is all used up by then. RAM: 36GB

If you can't find it in any shop (you need a part number first) then contacting Thrustmaster would be the next step. In general they respond quickly and probably will offer a spare replacement (at some cost off course). The contact form will do the job. https://support.thrustmaster.com/en/contact-en/

@SOLIDKREATE: I see in your screenshots that your AV still has a problem listed. If done everything right this shouldn't be. It should be green (same for your Firewall). You have to add the Eagle Dynamics folder (and your Saved Games folder while you're at it) exception to the AV "before" you run a repair.

There's a difference in VRAM usage between in game measurement and measured with MSI Afterburner. The MSI one shows a much higher VRAM usage, sometimes more than 50%.

Recently bought a Logitec Pro X2 LightSpeed Wireless. I like it very much, a LOT better than the Corsair HS70 Wireless I used before. Fits nicely (everybody's head is different), not to tight, not to lose, lightweight, very good build quality (couldn't say that from the Corsair), direct connection when turned on (couldn't say that from the Corsair, very good battery life (couldn't say that from the Corsair either) so it's been a win, win, win move. https://www.soundguys.com/logitech-g-pro-x-2-lightspeed-review-92068/

Yup it did. However, FS2020 and FS2024 are, although released 14 and 18 years later, not on par with what FSX had in terms of ATC (or AI traffic which is even worse in 20/24).

+1 Switched to 566.xx series after using 516.94 and 537.58 because I wanted to play around a bit with a hacked frame generation tweak and DLSS settings in MSFS 2024 because MSFS2024 didn't show up in the profile setting in the NCP of the older drivers. Updated to 570.xx since, no black screens here. Maybe card dependent (using a 3080Ti with 2 monitors, one connected through DP, the other through HDMI)?

Jeez dudes, get a life and fight it out in a PM chat. Nobody, but really NOBODY is interested in this. Moderators, isn't it time to put a lid on this topic?

Prices at my local PC shop: cards that are in stock RX 9070: 799 € - 849 € RX 9070 XT: 899 € - 999 € RX 7900 XTX: 1049 € - 1149 € NVidia: 5090: 4999 € (however, another store has them listed from 2609 € to 3199 € but nothing in stock) 5080: 1899 € - 2499 € (however, another store has them listed from 1239 € to 1889 € but nothing in stock) 5070Ti: 1499 € 5070: 999 €

I have no clue if the symbolic links I posted are soft or hard (been reading a bit about the difference between them but after a few lines I lose it) but they do work. That is all that matters.

For those with a bit of money in their pocket: null

MSI Center comes with the Mobo I guess. In general that's just lots of bloatware. Andrenalin is for AMD Graphics cards, since you have an nVidia 3090Ti, no need for this.

Depends a bit. I had no problem with 32GB of RAM with my previous system is but decided to go for 64GB for the one I have now (2 years old now). With the Irak map I noticed it would use up to +40GB of RAM so if I only had 32 it would need to swap things around at some point which might cause a bit of stuttering while doing so, who knows. With 64GB that problem doesn't exist.... yet.