scommander2

Hi @MAXsenna, any suggestion for using the TM USB TPR Calibration Tool? Thanks.

Yup, AIM-9X has the two-axis thrust-vectoring control which is not in other AIM-9 versions, and few planes can carry AIM-9x or similar missiles.

cool... good to know any major fix after .15. Thanks... PS: NV is still trying to fix crash and blank screen in the past patches... Hope this patch stops the bleeding...

Cool, thanks!!

Hi @Qcumber, sorry off the topic a bit. Has any chance tried the new driver 576.15 yet? Any impact to DCS, better or worse? Thanks.

Yes, I heard tones of issues were caused by the previous versions of NV drivers. NV has released the recent driver to fix the blank screen, unable to read GPU temp... stuffs. It should be a major fix. I saw that few users post their DCS test with 5080 with their test metrics (thanks for their information). I think that the previous drivers may not affect to these users. There is one of threads:

End year?

I guess CASE II may work for the night with the clear weather.

We have few already have had some performance issue with the latest DCS patch. DCS uses E-cores for IO cores.

It's Link4A and not encrypted data. Link16 is a data encrypted.

I was kind of okay prior to 2.9.15.9509, and 2.9.15.9599 is dead in the water now. Has anyone sounded the alarm to the ED tech support yet? Should I do so?

Sorry, it is out of my knowledge to help here anymore. However, I would like to learn if it has something to do with the 576.15 driver for Nvidia 50xx if I get one in the future.

Agree, it is not hardware issue beside the hardware should be able to perform very good result. At this point, we have done what we can try.... Want to try ED tech support?

What were the CPU/GPU utilization then? I have tested with affinity with P-Cores only v.s. affinity with P/E-cores (default by DCS), they were not too much different on my 12 P-Cores and 8 E-cores. Beside, ME runs with the CPU bound in the most of time (my CPU was about 28%, GPU was around 20% for 4080). While played around NV driver, and I got my display refresh rate become 30 MHz (not sure) so my FPS was low around 30 (hope it is not a case).

I had dropped my dcs.log into the discord dcs-log-analyzer and the app-bot got me back with the following message: Is it okay? Thanks.

FYI: one user also complained the related issue (may not be same). He ran the GPU stress test, and he got very low FPS from GPU.

This entry and related log have been removed from discord completed.

Okay, it explains why dcs.log said: system affinity mask: 11111111111111111111111111111111 process affinity mask: 1111111111111111 all cores are available for dcs.exe but dcs can use P-cores only. In my opinion, if we can disable PL for once to try out.

I think PL does something more than just applied the CPU affinity. According to the attached dcs.log: 2025-04-22 22:45:39.244 WARNING APP (Main): ProcessLasso is running Sorry, I missed this one However, I am still interested that DCS simply ignores all E-cores for its IO core usage... Is it caused by PL?

They are same. Process Lasso is not required anymore for the most recent DCS version, instead it causes some issues according to some users.

I found out that my HDR was enabled for some reasons, it was much better after I disabled it.

I am wondering that not few E-Cores were used by IO Cores, intertesting.

Off topic a bit, ED may be a good candidate for F-15E since ED is making F-15 C/D with full-fidelity.

I saw a YouTube video that a user replaced his Thrustmaster with Moza with the existing Thrustmaster mounting. He was able to mount Moza on it in the most of holes not all and he realized the base was moved during playing. Ended up, he still got the Moza plate.

I guess that the patch has no impact for users who have the topnotch hardware.