Downloading 1.8.3.0

Something is seriously wrong on my end, last night everything was normal, scenery looked perfect. Today, I open FS2020 up, it's not connecting to the scenery servers or market place and I have FSX looking scenery. My local Net connection is normal so that's not the issue. It's showing I have the indicated patch version but obviously it's not in the actual software. Something is very screwed up on their end fore sure. I also took note they were doing routine server maintenance today (at the same time as a major update???). I think somebody got their wires crossed over at MS. Well, we shall see if they manage to get this sorted out as some of us can't get the update nor use the Sim as intended.
 
Widespread reports of major issues with this patch borking the sim and likely to the point that once they do fix it in a month or two, you'll need th completely reinstall the sim and set up everything from square one. I'm not sure they have doing the major QC/Beta testing but boy, they goofed bigtime on this. SMH!
 
azflyboy said:
Apparently the patch completely removed the ability to set dead zones or sensitivities for a control axis, and introduced fun new bugs where some autopilots randomly turn off and refuse to reengage, the Baron G1000 randomly shuts off, and the Garmin avionics will refuse to load approaches for no apparent reason.

Given that it took two weeks to get the installer to work properly, I assume we'll be able to adjust control sensitivities again some time in October.
Click to expand...


Confirmed. Thought it was my update crash and reload that caused that. Clickspots in aircraft randomly disable after a few minutes of flying. Oh well.
 
Yeah, their support forums and Facebook are getting smacked hard over this. What a mess! Not sure what went wrong but until it's fixed, I am out of FS2020.
 
Weird, other than not being able to set the sensitivity curves for the control axes for now, I've been having a good experience with this update (already spent two hours making 4 flights tonight). It's probably just my imagination, but it seems to look even better than it was before (scenery/lighting), though all of the my flights were around late evening/dusk. Happy to see a control tower now at KSTP.
 
Looking into Packages\Official\OneStore, it looks like just about everything got updated in one way or another according to the last update timestamp on the folders.
 
Looks like the update went smoothly for me. I need a drink.
I always go deer in the headlights uploading/updating anything from MS.
PTSD

For reference: I'm running most of the settings in the high end range, ultra for pretty much everything.

Loaded an IFR in the Citation...flying that now. I got a faster boot for sure. System performance is in the green, no obvious negative impacts anywhere that I can find. Seems like the color has improved...less watercolor looking through real weather atmosphere. Color is richer for sure. Less screen tearing in the VC. Overall the whole thing was pretty painless, other than the fact that it took all day and we have quarter mile visibility under this smoke blanket, so I couldn't really go out and walk in the bush while the download ran.

Hope everything goes well for others. It's a new sim...gonna be buggy, so I guess we signed up for a little bit of pain along the way. That said...it feels good to have the new MS sim and Prepar3Dv5 running WFO with no real issues. Gotta say, since Mr. Venema released the ORBX TrueEarth product line Prepar3Dv5 can still hold its head high next to the MS sim visually.

IMO, as a sim enthusiast and developer I feel very privileged to have both of these stunning platforms at my fingertips. We've come a long way. :very_drunk:
 
Last edited:
As an anecdotal point, I just applied the update and flew out of KASH for 47 minutes. The only issues I came across were:

1. I couldn't see my liveries until I exited the software after the update and restarted it
2. It appears the lights on the radios are now tied to the Taxi Light switch and the Dome light does not turn on (maybe they're simulating a burnt out bulb?) on the C-152. This could, however, be related to the fact that I am using the C-152X addon. I'll have to remove it and see if that fixes things.

Also, why is the landing light so dim on the C-152?... I might switch to using the Taxi light when doing night landings, which is MUCH brighter, which weren't exactly super easy to do without any lighting in the cockpit... Had to set the plane up by feel.
 
I know I'm REALLY loving these fluid frame rates!

50351404197_cfabe71d12_h.jpg


For the record, I have Clouds and Ambient Occlusion set to Ultra, and the rest are in the medium/low settings. Someone either here or the MS forum posted a link to a rather long video that compared every level of just about every setting option. I wish I could find it now. There are so many items on the list that have very little real difference between low and high settings, but clouds set to low look like someone took a bag of cotton balls and launched them from a potato gun.
 
When I installed the update yesterday, which went very smoothly, I first made sure that there were no addons in the Community folder (I put them in a different folder temporarily). I also made sure that there weren't any modifications to the official files (I only had one - the reduced tree file - which I replaced with the original file prior to the update).

One of the recommendations, if you have repaints, is to make sure that the Aircraft.cfg files are up-to-date. I have looked through most of the Aircraft.cfg files in the Official files folder and none of them appear to have changed, so I think all of the repaints are fine with their current Aircraft.cfg files. Not sure about the major mod packs for some (like the A320 and C152), as I've stayed away from those.
 
Bomber_12th said:
When I installed the update yesterday, which went very smoothly, I first made sure that there were no addons in the Community folder (I put them in a different folder temporarily). I also made sure that there weren't any modifications to the official files (I only had one - the reduced tree file - which I replaced with the original file prior to the update).

One of the recommendations, if you have repaints, is to make sure that the Aircraft.cfg files are up-to-date. I have looked through most of the Aircraft.cfg files in the Official files folder and none of them appear to have changed, so I think all of the repaints are fine with their current Aircraft.cfg files. Not sure about the major mod packs for some (like the A320 and C152), as I've stayed away from those.
Click to expand...

I gotta say, it does seem silly to me that you need the whole aircraft.cfg file just to add some [FLTSIM.x] sections, especially since it precludes them updating the aircraft.cfg sections just so we can have repaints.

Of course that doesn't preclude us wanting to actually change the aircraft.cfg data, as, for instance, C-152X does. I just don't see why they are in the same file.

Seems like there should be a Repaint.cfg file... which, I imagine, could very easily be implemented by us by adding to the .json file the requisite file? I wonder if the software is looking for an "aircraft.cfg" file to find the contents of the file, or is it just looking for the data structures contained in the aircraft.cfg file, which could in fact be in any file, which is what I would do....
 
CAUTION LADS.

The Patch is broken in what seems like many ways.

One thing is clear - Empty your Community Folder (just shoot the contents over to another New Folder) before accepting the Download.

Information further coming but for us at the SOH - it totally breaks FSX Airframes - maybe deliberately, maybe by accident - who cares.

APPROACH WITH ABSOLUTE CAUTION - PATCH 1.8.3.0

If your MSFS is running to your satisfaction - then don't let it in.

My prediction being that ASOBO will Patch the PATCH within a fortnight.
 
Tom Clayton said:
It comes up as mandatory. No way around it.
Click to expand...

Your Avatar - with the scary mask - really frightens. It's not funny, entertaining or anything - especially with your screwed up facial features - it's just horrible.

In these times that we live in - perhaps you could think of something a little less scary and demonic and a bit more friendly.
Honestly, every time I see your avatar it sends me a little further away from this place. I love your posts and I love what you generally have to say but. . .

I'm not kidding - your avatar looks really horrible.

I'm asking.

x
 
Ganter said:
CAUTION LADS.

The Patch is broken in what seems like many ways.

One thing is clear - Empty your Community Folder (just shoot the contents over to another New Folder) before accepting the Download.

Information further coming but for us at the SOH - it totally breaks FSX Airframes - maybe deliberately, maybe by accident - who cares.

APPROACH WITH ABSOLUTE CAUTION - PATCH 1.8.3.0

If your MSFS is running to your satisfaction - then don't let it in.

My prediction being that ASOBO will Patch the PATCH within a fortnight.
Click to expand...

I certainly hope they fix it. At present, I believe I will end up having to do a complete uninstall/reinstall when all is said and done.

BTW, does anyone know where the controller settings config is saved? I was hoping to save my settings and then move them over once all is sorted so I don't have to re-bind everything. I hate asking questions on their support forums as you get your head chewed off by some of the drive-by posters there.
 
Ganter said:
CAUTION LADS.

The Patch is broken in what seems like many ways.

One thing is clear - Empty your Community Folder (just shoot the contents over to another New Folder) before accepting the Download.

Information further coming but for us at the SOH - it totally breaks FSX Airframes - maybe deliberately, maybe by accident - who cares.

APPROACH WITH ABSOLUTE CAUTION - PATCH 1.8.3.0

If your MSFS is running to your satisfaction - then don't let it in.

My prediction being that ASOBO will Patch the PATCH within a fortnight.
Click to expand...

Again, anecdotally, I left everything in my Community folder and have not experienced any issues other than what I said previously. I wonder if it has something to do with the wide variety of ways people have installed the software. I'm on MSStore. I did have an issue after the FIRST update, where the area surrounding last airport I flew out of prior to the update was stripped bare of trees (not buildings). I had initially installed in the WpApps directory. The only fix that I could figure out was to uninstall and reinstall. This time, I installed to my own directory, and noticed none of the files are encrypted when you don't install in the WpApps directory. I wonder if this has something to do with my smoother update this time?

Is there any common theme for people who have had problems as to where it's installed and where they purchased (i.e. Steam, WpApps, etc.)? I wonder if encryption and file ownership issues, and files people may have edited in the official directory, are screwing up the reliability of the install. For instance, I wonder if some sort of file caching issue that wasn't cleaned up properly combined with encryption/file ownership issues screwed up my first update. And by my now owning all my files made my second update go better.
 
Did a few flights tonight with the patched sim, no problems except for not being able to calibrate the controls anymore. But then again, I fly in Alaska, with twins and not jets and have no mods whatsoever.
I thought I'd wait a good few months before starting to look at add-ons..... :untroubled::untroubled:
 
You must log in or register to reply here.
Back
Top