August 28, 20241 yr Moderator The SDK for v5 is here. I have reassigned the MainThreadScheduler to core6 from 0 to keep the latter free for OS duties. The fix for aircraft wheels at FSDT airports is not one that bothers me. I couldn’t see any other benefits I lost as a result of reverting to 5.3HF2. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
August 28, 20241 yr 46 minutes ago, 787flyer said: If i am not mistaken, in v5.3 you could assign the P3D main thread to any core (whatever is your fastest core for your CPU) but in P3Dv5.4 I thought it was locked to core 0 (so I read), but I stand to be corrected as I never did install v5.4 If that's not the case, that would be one less obstacle in moving to v5.4. Yes indeed, I suspect you are mistaken @787flyer. The main thread can be assigned to whatever core you like in V5.4. Here is my AF for V5.4:- AffinityMask=4294967295 P3DCoreAffinityMask=4294967292 MainThreadScheduler=15 RenderThreadScheduler=11 FrameWorkerThreadScheduler=28
August 28, 20241 yr Commercial Member 1 hour ago, 787flyer said: No, I dont think so Luke. I have a Job Scheduler that can assign the P3D main thread, the terrain (Renderthreadscheduler) threads and Frameworkerthreadscheduler to different cores in P3Dv5.3 You're right - for some reason I thought that came out in 5.4. But Sparkrite is correct - the main thread can be on any core you want - in fact an application cannot force a thread to a specific core in Windows. It can always be overridden. Cheers Luke Kolin I make simFDR, the most advanced flight data recorder for FSX, Prepar3D and X-Plane.
August 29, 20241 yr Thanks Guys for the feedback on the Job Scheduler uncertainties. Looks promising. So, I did some more digging into the EHAM textures issue in v5.4 and this can be overcome by updating the LUA script. I think the only other thing that prevents me from moving to v5.4 is the issue Ray ran into with AI traffic causing some spurious issues, if I remember. @Ray Proudfoot- did you ever get to the bottom of this? SpoilerSystem specs: MFG Crosswind pedals| ACE B747 yoke |Honeycomb Bravo throttleNow built: P3Dv5.3HF2: Intel i5-12600K @4.8Ghz | MSI Z690-A PRO | Asus Dual RTX 4070 Super OC 12Gb| 32Gb Corsair Vengeance LPX DDR4 3200Mhz |Samsung 980Evo Pro PCIe 500Gb | WD Black SN850 PCIe 2Tb | WD SA510 4Tb |beQuiet 802 Tower Case|Corsair RM850 PSU | Acer Predator X34P 3440x1440pMark AldridgeMSFS2024 SU5 & P3D v5.3 HF2
August 29, 20241 yr Moderator 44 minutes ago, 787flyer said: @Ray Proudfoot- did you ever get to the bottom of this? Nope. Very difficult to determine the BGLs responsible. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
September 1, 20241 yr Can't imagine going back to 5.3. P3d 5.4 works flawlessly for me and extremely stutter-free. I still have my Jetline computer (4 years) with my Nvidia 1080Ti and my sliders are all full right or 1 setting below on some of them. Of course, I do not use AIG for traffic since I found it contrary to their advertising it to be "one click". I truly found it very cumbersome. I am very happy with my UT LIVE for traffic and although not as robust as AIG, it is robust enough for me with adequate traffic at all airports as well as aircraft in the sky. Edited September 1, 20241 yr by spilok
Create an account or sign in to comment