miguelaco

Hi, When launching AIM-7 from TWS or RWS it correctly goes to STT and albeit the TTG is displayed, the missile arrow/triangle does not progress to the target. When launching in STT mode, the arrow/triangle depicting the missile progress to the target according to displayed TTG. Find attached a short track depicting the issue. First launch is in RWS, second in STT, third in TWS and fourth in STT again. Cheers aim7_bug.trk

That fixed it for me too but I don't want to leave HT disabled just for DCS. Specially when once in the sim, I noticed a small hit on fps stability with HT off. Did you try downgrading the BIOS? I didn't do anything special with my ASUS board, just followed the usual procedure to bump up the version but applied a previous one instead. Cheers

I rolled back the BIOS to an August 2024 version, and DCS load times have improved a lot, pretty much on par with the benchmarks I got when disabling HT. I have an Asus ROG Strix Z790-F Gaming WiFi II. The BIOS version is 1503 dated 2024/08/08.

I'm aware of that change, but we're talking here (at least I am) of loading times from desktop to main menu. In my case, once in the menu the sim runs smooth with no excessive loading times, before and after the patch.

No improvement for me in load times after updating to latest DCS version 2.9.20.15010. Wonder if the fix made it to this patch as it doesn't seem mentioned in the changelog.

I think this is the same issue: I'm personally having the same behavior although mine is a 14900k. The linked comment sounds exactly as yours. I'm willing to downgrade my BIOS just to test this issue, but it seems a fix for long load times is scheduled for the next patch (hopefully releases today) so I'll wait for it.

Actually, depending on your configuration, there are now 3 places to setup sharpness: Pimax Play: it works only in VR and it's applied to the entire fov DCS: it works both in VR and 2D and also applied to the entire fov mbucchia's Quadviews Foveated: it works only in VR and it is only applied to the foveated region I would like to do some tests, but my feeling is that if you enable it in PP, it's not a good practice to enable it in DCS at the same time. I have my doubts with mbucchia's QV. Any thoughts or recommendations on where should we set sharpness to achieve better quality or performance?

That's interesting, I updated my BIOS to latest versions as soon as they were released to mitigate the degradation issues. I'll wait for the fix and if it doesn't solve it, then I'll revert to older BIOS versions. Thanks for sharing your observations.

I also have HAGS and Game Mode enabled, and I’m running the latest Nvidia drivers. The results I’m seeing are very similar to the ones I posted earlier, consistent across the last five driver versions. I normally fly in VR, but for these measurements I tested without VR enabled. My CPU cores are unparked as well, otherwise the usual warning would show up in the logs. From what I can tell, the issue is definitely CPU-related, I know there are a lot of factors, but it's clear that there are several users with the same behavior I described and I thought it could give some hints to what's going on here with this issue. If anyone else is seeing the same behavior, it would be helpful if you could share your load times with HT enabled vs. disabled.

I'd stick with mbucchia's quadviews for now until Pimax optimizes its own implementation. Didn't notice any hit in performance in my OG Crystal with latest PP + Pimax OpenXR + mbucchia's quadviews.

I'm happy a fix for loading times is in the works, but at the same time, I don't think HT On vs Off should be disregarded, if not as a direct cause to the issue, at least as something that might point to it. It's clear many users find that disabling HT helps with load times, both in these forums and the discord server. In my case, I made 12 runs, 6 with HT on and another 6 with HT off. The results are as follows: Desktop to launcher average of 37s with HT on vs. 13s with HT off. Launcher to menu average of 85s with HT on vs. 41s with HT off. I don't think it makes much sense to assume as normal behavior that disabling HT cuts loading times by more than half compared to HT enabled. I really think this should be looked at by the developers as it may point to a possible issue with Intel CPUs. I'm running DCS on a 14900k, btw. dcs-hton.log.zip dcs-htoff.log.zip

I have the same issue in the menu and I'm not disabling e-cores at all. I'm trying to pinpoint the cause and noticed that disabling Hyperthreading kind of fixes the issue in the main menu. Sadly, it seems that fps are less stable once in the cockpit, so it is a dead end for me. I keep reading that lowering the polling rate of the mouse seems to help, but I don't know how to do that in my Logitech MX Master 3. I have to say it is really annoying, even if it seems fine once in-sim.

I also noticed a huge improvement in load times by disabling Hyper-threading. I didn't get better performance once in the cockpit, a little improvement in stability if any.

I think the unlock & relock when releasing the uncage button is not right, aside the other inconsistencies noted above between non-acm L&S and STT.

This seems to be corrected in today's patch, MAN, S/A and AUTO modes in the Hornet are working as expected. Congrats to the team!!!