12 minutes ago, RaptyrOne said:

This idea is noble for sure and I support it.... but not to throw cold water on it, there are well documented and known bugs in the code. These have absolutely nothing to do with your system spec. Dare I say that some people that say that they don’t see problems are just oblivious to them. Some don’t see the LOD issue for example, yet in their screen shots it’s pretty obvious that they have the issue.

Another good example is the avionics blackout bug. Too many people here said “I don’t have this problem, it must be your system, or you broke it by doing something.” The fact of it is that everybody has the issue. Some just had their settings set to where the bug is hidden (using generic AI for example). This is the beauty of these forums, people figure stuff out as a community and workarounds can be found. But bugs are bugs and no amount of formatting, reinstalling, changing out CPU, RAM, GPU, PSU etc will melt them away.

Good points. Not really focused on those issues. More focused on CTD and installation problems. 

Outcome: Working
OS: Windows Pro Home (64 bit)
CPU: Intel i7 4770K @ 4,3Ghz watercooled (coming from 4,5Ghz after turning on HT, ran too hot with HT on, HT gave a lot smoother gameplay in 1.7.3.0)
Motherboard: Asrock Extreme 4
GPU: GTX 1080ti 11 GB (driver 456.38)
RAM: 32 GB (2400Mhz)
Drive: SSD
Resolution: 2560x1440
Internet: 300 Mbps (max)
Joystick: Thrustmaster Warthog (stickbase replaced by VPC WarBRD)
MSFS Version: Standalone (no Steam)
Install Location: Dedicated drive (SSD)
Antivirus: Windows Defender (FS excluded)
MSI Afterburner: No
Process Lasso: No
Overclocking: CPU (Yes), GPU (No), RAM (No)

Installation and general gameplay:
1.7.3.0: Download and installation OK, lots of stutter, not smooth. CTD's when virtual hotplugging the HOTAS.
1.8.3.0: Would hang on various files while downloading, downloading same files over and again. Solved by reducing bandwidth on networkcard to 10Mbps/sec for the duration of the download. Gameplay: A lot less stutter in this version.
1.9.3.0: Did the 10Mbps trick before the download, downloaded in one go. Overall smooth gameplay, but terrible LOD poppin' now.

Never seen my 32GB RAM go over 13GB used in the sim.

 

Edited October 2, 20205 yr by Lange_666

I would really like to see some proper tests of internet speeds affecting actual performance. For most parts during flight I notice it rarely using over 2mbps.  Lets face it, most the world is ai generated.

Does slow connection really causing stutters or just slow texture loading ? 

50 minutes ago, RaptyrOne said:

This idea is noble for sure and I support it.... but not to throw cold water on it, there are well documented and known bugs in the code. These have absolutely nothing to do with your system spec. Dare I say that some people that say that they don’t see problems are just oblivious to them. Some don’t see the LOD issue for example, yet in their screen shots it’s pretty obvious that they have the issue.

 

I just proved yesterday with the help of other simmers that some world areas are simply bugged and causing freezes for no apparent reason.

I solved 2 or 3 issues just using 'search' here on avsim. Someone has had the same issue before  I did.

During Steam downloading patch 3, my internet connection weakened but did not die. And so at the end MSFS 2020 turned off my internet data stream, and did not tell me. So I wondered why my framerates and image had *both* deteriorated with the patch. I thought one or the other but not both could decrease, i.e. if I didn't have to waste computer power streaming data while playing, then the f.p.s. should be improving. Nope. Doesn't work that way.

I solved that one by the freeware configuration checklist here. Just double checked everything on the list, and found data was not streaming. Took 3 minutes after I had spent 2 hours on my own.

 

Edited October 2, 20205 yr by Fielder

8 hours ago, Rob_Ainscough said:

• Users tweaking things they don't understand (many users wanted to get away from this process , but that hasn't really changed much).
• MSFS updates not knowing how to deal with a file who's signature has changed (by end user).
• User setting MSFS files to read only.
• Users with extremely poor internet connections.
• MSFS introduced new bugs and taking features away and not fixing other issues.
• Updating with MSFS in Dev Mode has caused some issues.
• Dev Mode causing issues with 3rd party DLC (aka Orbx central not seeing MSFS).
• Overly aggressive 3rd partyanti-malware/virus software preventing updates/installs.
• Unstable hardware (overclocking) user side.
• Server load problems on MSFS side.
• Setting up a large rolling cache size and then quitting or shutting down MSFS before it's completed the task.
• Exceeding the capability of one's hardware 16GB RAM instead of 32GB RAM and turning off Win OS pagefile.

It's never really off (even when using the group policy editor) and I would NOT recommend turning it off unless you have an alternative running.

Probably many other possibilities that are inherent in an uncontrolled PC environment ... this is where XBOX X will resolve many of these issues.

Cheers, Rob.

EDIT: For windows defender, if you have concerns about it's performance draw, setup folder exceptions so it will not interfere.

 

 

Also, updating without first removing add ons from community folder (including any Orbx in com folder)

41 minutes ago, roi1862 said:

I just proved yesterday with the help of other simmers that some world areas are simply bugged and causing freezes for no apparent reason.

This is also caused by some scenery add ons.

5 minutes ago, SierraHotel said:

Also, updating without first removing add ons from community folder (including any Orbx in com folder)

Don't think this matters, after updating from 1.8.3.0 to 1.9.3.0 i forgot to remove my stuff in the community folder and it was completely empty after the upgrade.

Edited October 2, 20205 yr by Lange_666

1 hour ago, RobJC said:

It would be nice to have full info, if you get a chance. 

This does work, I set mine to just 5% and works fine with A320

a noble effort, but its not going to work.

it so much easier to blame the program than something at my end.

i see this happening  and a lot of games, its not going to change.

8 hours ago, bean_sprout said:

We can't assume that simmers have all the required knowhow to troubleshoot issues.  It can be hard if not daunting for some.  Maybe a basic checklist with detailed steps would help.

One other problem is that the sim is not totally stable IMO so troubleshooting will change over time.

 

Regards

bs

 

Before going to a PC...I was  an Atari and Apple guy.   Those systems (G.U.I., not older DoS based)  were and even Apple muchly to this day are closed systems.  There weren't too many choices in the G.U.I. to mess around with files in folders, or the O.S. itself.  Today...wow...you can bury yourself in trouble, in no time.  I think no matter how great the idea is...that we won't be able to reach a User Commonality....for everybody to get a great whatever MSFS experience, unless...it does come from the coding side of the Devs...you install, you run...and it runs great...bypassing any impetus for a user to want to GET it to run, as they think it should.  The features, work...the planes fly...the instrument panels cook it....and until MSFS is at that stage...people are sill gonna mess around...at their end.  Stability has to be inherent in the software....to make it a Nirvana Experience.  It's up to Asobo. Not the end system.

i7-3370 cpu 3,4 ghz   oc 4ghz

RAM 32 Gb DDR3

Motherboard  Asus P8Z77-V

Drive: SSD

rtx 2060 Super 8Gb  1920x1080

Joystick: Saitec Pro Flight

Internet: 100 Mbps (max)

Antivirus: Windows Defender

Settings : All Ultra,  Cockpit Refresh: Mid

Addons :  No

FPS :  25-30 ,  London EGLL 20-25

Traffic: 50%

Weather  Live

A320 Nero

No Problems, No Stuttering

 

 

 

Well, I know one of the problems some of us were having was stuttering that didn't exist before. Turned out this was caused by the latest (September 17th) NVIDIA driver, not Asobo's patch. So people with AMD hardware, or those who didn't update their NVIDIA driver, didn't experience this problem.

 

10 hours ago, RobJC said:

 

 

Bit late to the party on this one but in terms of actually flying the planes, the A320 has been many user's Kryptonite from Day 1. However there are numerous videos circulating on YT (not pre-release either) from people who seem to be flying without issue, the latest one I caught was a guy claiming to be a real A320 driver doing a circuit from Edinburgh airport.

So last night I loaded in a flight with the A320, then before doing anything I actually spent 10 - 15 mins poring over the various knobs and switches on the panel. Now there's no doubt this thing is overpowered, take-off was more like lift-off with the usual 5000fpm climb out. However with a bit of deft knob twisting and pushing was able to get settled into a 1800fpm climb, albeit at 320 knots rather than my preferred 280 knots. Settled into my FL290 cruise. At that point I had to save and come off, so withhold judgement on aspects such as the FMC retaining the flightplan and any issues related to approach and landing.

However that said, some of the issues must still go over to Asobo/MS. They chose the A320 as their short-medium haul airliner and then proceeded to model the AP/AT system as is, which is quite different to Boeing or the "Acme" as I term it, default auto systems in previous FS'. The biggest difference being AT is really semi-AT and you have to adjust the throttle  according to the phase of flight. So really, having made this choice Asobo should have included a tutorial flight(s) to familiarise users with the quite different Airbus procedures and, of course, this would have been ideal study material if they had given us a blooming manual.

In conclusion, there's no doubt the A320 has issues as do most of the default planes but it's (maybe) not quite the demon it has been made out to be.

You guys saying you have zero issues, I'm assuming this doesn't include all the actual bugs in MSFS that have been confirmed by Asobo itself? Otherwise you're saying the sim is perfect (it isn't) and every problem is the user's fault (also false).