Nikolai V. Chr.

I am not sure if this is still an issue in 2024.2 or next. It only happened for some users. On Fri, Oct 25, 2024 at 5:35 PM Gijs gijsrooy@users.sourceforge.net wrote: status: Accepted --> NeedInfo Comment: @forgolai https://sourceforge.net/u/forgolai/profile/, is this still an issue or can we close it? [codetickets:#2257] https://sourceforge.net/p/flightgear/codetickets/2257/ Maketimer is unreliable especially when using restart(delay) on it frequently Status: NeedInfo Milestone: 2020.1 Labels: nasal...

HDR: Use hdr specific property to drive blackout that is independent of ALS filter. And blackout now has a tunnel desaturation.

Sorry, its too long ago, I don't remember.

2020.3.19

=none They both run one same core (the 2nd). The second client hangs until the popup appears during loading and is clicked away. unset They both run on the same core (the 1st). The second client popup comes when starting the app, and it hangs during loading and continues to hang.

I was running with --prop:/sim/thread-cpu-affinity=none And yes, its very much reproduceable as in 100% of the time. Both the hang, and the flocking to same core.

And yes, there is also an issue with the read-only popup. It seems delayed, I wrote all the above while 2nd FG client was starting up and when I returned to look at it the popup was only just coming up. FG 2020.4 nightly win 10, from today, precompiled binary.

The issue is still there. We talked about this on the mailing list last year. The issue is that the first client chooses its core to run on. The second and third client then chooses the same core to run on. Easy to see in task manager. For 2020.3 its the 1st core, for 2020.4 its seems random core, but its the same they choose. The fix is: let windows decide which core to run on for main thread and all other threads too. There is really no reason to mess with affinity in 2024.