3 minutes ago, JRBarrett said:

This is something that has mystified me in all the complaining about the lack of Garmin updates by Asobo. I intend no criticism of you, but I am really curious... Why on earth would you, (or anyone), choose to use the stock G-1000 or 3000 when the WT mods are available? I could understand if they were payware, but they are absolutely free, have no adverse impact on sim performance, and take about 3 seconds to install.

For me, it's because I think MSFS is still in basically a public beta state since release. I want to evaluate how the base sim is doing with the stuff that's supposed to be working as default.

I'm especially reluctant to use mods that "fix" something that's broken or missing in the base sim. I'm not that desperate to fly with a temporary fix, because I have other sims where these things aren't broken if I want to fly with a working GPS or FMS. 

 

As great as the mods are, they unfortunately can’t address some fundamental issues with the underlying navigation logic. They do a pretty good job working around the problems, but there are limitations.

1 hour ago, TomCYYZ said:

Boy, I’m glad I haven’t updated yet. I’m going to wait ‘till a “fix the Update” Update is released. Not Using MSFS2020 until then. I’m no guinea pig. 😉

I’ve had no issues with it for what I do with it.

Edited March 10, 20215 yr by Tuskin38

29 minutes ago, JRBarrett said:

This is something that has mystified me in all the complaining about the lack of Garmin updates by Asobo. I intend no criticism of you, but I am really curious... Why on earth would you, (or anyone), choose to use the stock G-1000 or 3000 when the WT mods are available? I could understand if they were payware, but they are absolutely free, have no adverse impact on sim performance, and take about 3 seconds to install.

Jim, I'm flying all over the place IFR w/ sids/stars and not using any mods in the TBM.  What does these mods offer?

Any one else seeing crazy flaps issues ?

27 minutes ago, Tuskin38 said:

I’ve had no issues with it.

Thanks, just a little friendly sarcasm. I am currently performing the upgrade now on Steam @ 9.44GB. Not sure if the liveries are installed in there, but I don't care too much about that anyway. When done I am going to close and go back in and try a test flight into DFW with the 737 as "Manny" did and see what I get. I know he had performance problems. BTW as it is updating it is showing the version number 1.14.5.0.

Edited March 10, 20215 yr by TomCYYZ

I just tried a quick look at the new update. At my usual, local real life GA test airport in the 172, I noticed a severe drop in frame rate down to 30 fps from what I was used to, when sitting on the runway ready for takeoff. This is a small rural GA airport with very little scenery.

I backed out to check the settings, and sure enough... the update enabled Vsync with a 30fps lock. I turned that off, and I'm back to the usual 50 fps I'm used to seeing at that location. Actual flying over more complex terrain is usually more like 35-45 fps, normal for previous patches.

This is beyond stupid. They really need to stop resetting the user options with each new update, unless they enjoy hearing about "frame rate drop." I can't imagine a good reason for messing with the user settings like this.

P.S. I'm using no mods.

7 minutes ago, Paraffin said:

I just tried a quick look at the new update. At my usual, local real life GA test airport in the 172, I noticed a severe drop in frame rate down to 30 fps from what I was used to, when sitting on the runway ready for takeoff. This is a small rural GA airport with very little scenery.

I backed out to check the settings, and sure enough... the update enabled Vsync with a 30fps lock. I turned that off, and I'm back to the usual 50 fps I'm used to seeing at that location. Actual flying over more complex terrain is usually more like 35-45 fps, normal for previous patches.

This is beyond stupid. They really need to stop resetting the user options with each new update, unless they enjoy hearing about "frame rate drop." I can't imagine a good reason for messing with the user settings like this.

P.S. I'm using no mods.

I've only had this happen once since release and over 200h OTC.  It was today's update, and it put me back to pre-set weather whereas I always leave it on Live.  I checked all other settings and they were untouched.  I seem to always be blessed--not CTD, everything works, looks fabulous and performance is good.  I have had a couple of sessions where I had ample CPU and GPU headroom yet frames tanked, but that was a glitch of sorts, not recurrent, and maybe was related to the area I was in in Bavaria.  Clearly they're not resetting them intentionally, which indeed would be stupid and it's obviously variable per user so it's a glitch they may not be aware of.   Do you use Steam, or Store?  Fortunately it's a simple matter to check settings after a major update.  

16 minutes ago, Paraffin said:

I just tried a quick look at the new update. At my usual, local real life GA test airport in the 172, I noticed a severe drop in frame rate down to 30 fps from what I was used to, when sitting on the runway ready for takeoff. This is a small rural GA airport with very little scenery.

I backed out to check the settings, and sure enough... the update enabled Vsync with a 30fps lock. I turned that off, and I'm back to the usual 50 fps I'm used to seeing at that location. Actual flying over more complex terrain is usually more like 35-45 fps, normal for previous patches.

This is beyond stupid. They really need to stop resetting the user options with each new update, unless they enjoy hearing about "frame rate drop." I can't imagine a good reason for messing with the user settings like this.

P.S. I'm using no mods.

I just noticed after reading your post, that you can't use the frame rate limiter now without turning on V sync, I used to leave V sync off and limit FPS to 30, but now when you turn off V sync, frame rate limiter is grayed out. 

5 minutes ago, Bobsk8 said:

I just noticed after reading your post, that you can't use the frame rate limiter now without turning on V sync, I used to leave V sync off and limit FPS to 30, but now when you turn off V sync, frame rate limiter is grayed out. 

It's always been like that. No way you could use the internal limiter without vsync being on. 

Just now, devgrp said:

It's always been like that. No way you could use the internal limiter without vsync being on. 

Oh, OK, didn't notice that before. 

While I'm glad for the advances in another update, this "major" update feels like it is full of fiddly fixes (I have not doubt some may have been challenging to address). Bottom line: I'm waiting for the weather system to be more fully functional, proper ai to make the world feel more alive, continued flight model improvements, flight instrumentation (eg. gps) to be updated, substantive sdk improvements so we can have more complex aircraft and other addons.

None of that has occurred in this update. : (

Makes me feel like it's a looooooong way off.

26 minutes ago, Noel said:

Do you use Steam, or Store?  Fortunately it's a simple matter to check settings after a major update.  

MS Store version.

Sure, it's easy to check if they've messed with user settings, but I can't emphasize this enough -- it's not normal for any simulator or game to mess with user settings that affect frame rate with an incremental patch!

It's begging for a flood of tech support tickets. I've never seen it before with any flight sim or computer game, because it causes headaches for the users and the developers both. 

1 hour ago, snglecoil said:

As great as the mods are, they unfortunately can’t address some fundamental issues with the underlying navigation logic. They do a pretty good job working around the problems, but there are limitations.

Based on what WT is doing with the CJ-4, I suspect they may eventually replace the dependence of sim Garmins on the underlying Asobo nav system with something completely independent, that allows procedures to be entered and flown exactly like the real Garmins. There are individuals on the WT team with real world avionics design knowledge and experience (that Asobo lacks) which is why I have my doubts that left to their own devices, Asobo will ever be able to do much with the Gxxxx systems beyond what they already have.

Asobo would be better served to simply subcontract the entire Garmin emulation to WT, but since they are freeware developers, and doing so would probably require Microsoft to grant access to the proprietary source code of the sim, that is unlikely to happen.

8 minutes ago, Purr said:

While I'm glad for the advances in another update, this "major" update feels like it is full of fiddly fixes (I have not doubt some may have been challenging to address). Bottom line: I'm waiting for the weather system to be more fully functional, proper ai to make the world feel more alive, continued flight model improvements, flight instrumentation (eg. gps) to be updated, substantive sdk improvements so we can have more complex aircraft and other addons.

None of that has occurred in this update. : (

Makes me feel like it's a looooooong way off.

Some of it is ...  note how many bugs simply say "backlog" ...  Third party access to the weather system is simply "not planned"

 

 

Edited March 10, 20215 yr by Glenn Fitzpatrick