I used the mod on my last flight and cruised over an hour between FL250 and FL300. Did you use the right folder of the mod? There are two, one for beta and one for release.
The current MOD on flightsim.to fixes the issue as others have previously mentioned, i’m currently an hour into a flight with no pressurization issues on SU1, i’m not sure if i can post a link to the MOD in here but its an easy find.
Can some please just confirm which version of the fix should be used with SU1? The old release version or the one created with the different folder name for the beta version
I’m using the public build. All good here
Public version.
The public version
This is spot on. Dont copy the original extracted folder but only one of the folders to the community folder. I had made this mistake myself
I have installed the mod from flightsim.to with public version, simulator with SU1 release version. After I cruise over 5 hours in career mode, the lower MFP, MCP, backup instruments and panel lights are all blacked out. What’s wrong with it? I also have checked the status of my plane, and all electronic devices are good. Is this another bug?
@TheRampantGoat – now that SU1 is live, should we be using the Beta build or the Public build? I would assume the former, since it presumably targets SU1, but other posts here and on flightsim.to suggest otherwise.
The public build is the right one, that’s the one I use.
Public build. They changed the file name back to the original before releasing SU1.
Even on beta
Same problelm for me.
After SU1 release, we should use beta fix, the only thing beta fix doing is change design_cabin_pressure
from 4.7
to 10.8
.
And don’t forget to rename folder name from microsoft_pc12_ngx
to microsoft-pc12-ngx
since the SU1 changed folder naming pattern. and also change the path
variable in layout.json
file
? The beta has ended. Everyone is back on the public version.
The only difference between the public and beta versions of the mod fix is the folder name. You’re suggestion to use the beta fix and change the name to the public fix results in the same thing as just using the public fix version in the same place.
the systems.cfg file between beta and public is not the same, diff shows that public also changes some avionics settings.