No, the fix will be included with Sim Update 3 and tested with the rest of the aircraft updates. I think that’s what was meant by that
1 Like
Only if 3rd party devs update their aircraft via the marketplace. Carenado is updating every few months the PA44. I can confirm that because that’s the one I have, don’t know about the other ones.
In a weird way I am actually happy about this mess. Suddenly I can take up my other hobbies, such as playing the piano, instead of being stuck with MSFS every day after work.
4 Likes
Can you please explain what do they mean by divide the flaps lift by 2X?
For example: if the King Air has: lift_coef_flaps = 0.85970
what should I do?
Hi @Jummivana ,
Many thanks for the announcement on this. Good to know that the cause has been found and is being worked on. With respect to the workaround I have 28 instances of that file on my computer. Within the first such file I opened I have 1 instance of lift_coef and 2 instances of lift_scalar. The questions I have are:
- Do I need to change all instances of lift_coef and lift_scalar within each file?
- Do I need to change all 28 files?
- Will any future update reset these to the correct setting or will I need to change them back myself?
Note: I only have 1 “mod” installed which is the A320NX. All other planes are what came with the original installation.
If the team are suggestion workarounds then can I ask that they provide more detailed instructions?
Many thanks for all of the fun I have had with the product so far!
1 Like
but how do you want to automatically test flight models ?
My guess would be 0.85970 / 2 = 0.4something
the new coef would be 0.85970/2 I believe. which is 0.42985
I think Sim Updates always reset manual changes.
A32nx dev version has a fix btw.
2 Likes
So, are we updating both lift_coef_flaps and lift_scalar or do they mean we can update one or the other?
<tinfoilhat>
I am starting to suspect they accidentally pushed a debug build for release.
Someone reported getting a debug breakpoint dialog which is impossible to happen unless DEBUG is defined.
Looking at the filesize, the FlightSimulator.exe increased from 292MB to 327MB. That is more than 10% larger.
I cant see the reason for that increase given a ‘World Update’.
</tinfoilhat>
1 Like
I’m afraid that is indeed what they mean by it 
Not sure, hopefully they provide a tutorial or new files
We’ll see. I’m sure they’ll be extra careful with Sim Update 3 now that this has happened.
If the filesize decreases, this could be the reason
From what I saw in the FBW A320, they adjusted lift_coef_flaps and lift_coef_ground_effect_mach_table. I think I will start with those
I just edited some of the default aircraft and now I get the following message when starting the sim: ‘Some packages in your community folder may not have been updated and, as a result, may have an unexpected impact on the title’s performance and behavior. Please move your community packages …’ followed by what looks like the world 3 update notes. I downloaded 361MB, files for the edited planes. Now their .cfg file is reset to Asobo default, thus reverting my changes back.
I wouldn’t change that one.
1 Like
you shouldn’t change what’s in the onestore folder directly
just ask a mod dev to do it. Someone from fbw/salty/working title would surely be glad to do it
Weird, I have never seen that when editing official files. Maybe they have actually added proper checking now with the update. (I havent tried it)
Normally one would have to delete the entire package folder to get it to re-download again.
Much appreciated to hear from the team on the matter.
As a fellow software developer working on pipelines and build processes a lot of the time, are you sure you’d not rather issue a hotfix? This will be very sticky for those with payware aircrafts, and that’s before we consider how hostile this is towards less technically inclined users. (And that again is before we consider how some aircraft aren’t so straightforward to update with multiple configuration values rather than the one as mentioned.)
I hope the Asobo team, unless Sim Update 3 is finished on Monday, reconsiders, issues a hotfix, and considers hiring someone (like me!) to enhance the robustness of the build process.
Thanks again for the update, Jummivana.
6 Likes
I agree. I think a hotfix for just this issue would be good. This issue is a really big one.
That way Update 3 could focus on improvements not fixing a new bug.
1 Like