Due to the LM stuttering bug that they are still trying to track down and fix, I know I and many others (FSL Dev's as well) have reverted to the 5.2 client. I have the 5.2 client and the 5.3HF1 scenery and content installed. My question, reading the change log for 8040, will those running 5.3 client not see any of these fixes then as they say 5.3HF1 only?
8040 Release Question
- Thread starter B777ER
- Start date
deansalman
Member
8040 just came out so I think they must have fixed something with P3D HF 1 update which I am running. Everything seems to be running ok
So those on 5.2 will still see the visibility going to unlimited on approach using 5.2 client? I don't want to be on the 5.2 client but the stuttering issue is currently a showstopper with 5.3.
Yes, that is an issue with our development logistics and need to focus on the new version with a unique interface vs. pushing this to older versions each with their own considerations. In this case, 5.2 can't be fixed the same way we did for 5.3 in this regard. In short time I'm sure we'll be on to a new version with this resolved and newer issues to consider.
The 5.3HF1 stuttering issue, based on all the info I see, is related to either an incomplete/invalid update/installation of P3D, scenery add-ons, AI traffic/environment/road traffic overload, or general overload influenced by options (such as Autogen Draw Distance), or specific .cfg adjustments which are problematic. I'm sure it will be sorted soon for those that are still experiencing it. In the mean time I highly recommend isolation testing ASP3D 8042 just posted, and vanilla P3D 5.3HF1+ full re-install with options low, then move things up/add things slowly until you identify what is causing the issue on your side, then you can avoid that option/item with everything else running appropriately.
The 5.3HF1 stuttering issue, based on all the info I see, is related to either an incomplete/invalid update/installation of P3D, scenery add-ons, AI traffic/environment/road traffic overload, or general overload influenced by options (such as Autogen Draw Distance), or specific .cfg adjustments which are problematic. I'm sure it will be sorted soon for those that are still experiencing it. In the mean time I highly recommend isolation testing ASP3D 8042 just posted, and vanilla P3D 5.3HF1+ full re-install with options low, then move things up/add things slowly until you identify what is causing the issue on your side, then you can avoid that option/item with everything else running appropriately.
Last edited:
– [01/04/22] Fixed issue where very long smoothing transition times might occur with P3D 5.3+, causing very high visibility when low visibility is expected, especially on approach/landing at destination in IMC where clearer visibility exists on the approach path and descent into surface altitudes (below approximately 7,000ft) occurs at those initially-higher visibilities
Will this be implemented for 5.2 HF1 too in the future?
Will this be implemented for 5.2 HF1 too in the future?
I tested 8042 with v5.3 hotfixed HF1 on the route from TBPB to TNCM, I did not observed any troubles.
Again without any stutters or lags.
My config :
AMD R7 3700X at 4.2 GHz all 8 cores, HT OFF
GTX 1060 6 GB stock clocking with driver 466.27
32 GB 3200 MHz RAM, stock clocking too
Again without any stutters or lags.
My config :
AMD R7 3700X at 4.2 GHz all 8 cores, HT OFF
GTX 1060 6 GB stock clocking with driver 466.27
32 GB 3200 MHz RAM, stock clocking too
The fixes/changes are specific to 5.3. We are not planning additional changes to the older interfaces. 5.2 has its own set of issues that prevent us improving things the way we did with 5.3.