25 minutes ago, hanhamreds said:

Just restarting the game.
 

So when I first ran the game FPS was fine in menus but when I visited 76T I had the 3 FPS issue, the only way out for me was to close the game. 

ran it again and had 3fps immediately in the menu, closed game.

ran/launched it again and frames came back in menus.

 

is 76T the new Roswell?

So you completely closed it three times

My guess is that it's a threading bug in the code where the code is merging on a single core thread. Something triggers it that is being processed most likely, which is why it's repeatable geographically, but maybe not always repeatable 100%. Hopefully they'll have a fix within a week. As upset as people are, I doubt they'll wait much longer, but we'll see.

 

Edited March 16, 20215 yr by Alpine Scenery

2 hours ago, Alpine Scenery said:

My guess is that it's a threading bug in the code where the code is merging on a single core thread. Something triggers it that is being processed most likely, which is why it's repeatable geographically, but maybe not always repeatable 100%. Hopefully they'll have a fix within a week. As upset as people are, I doubt they'll wait much longer, but we'll see.

 

I am hoping we get a detailed (within reason) explanation as to what is going now that there has been an acknowledgment of the issue - I will survive without one but man I am curious on this one…I was hoping a developer might chime in on what they think is going on but I haven't seen one myself yet......

Edited March 17, 20215 yr by marcg11

It's like something is issuing a draw call an infinite amount of times until you're clear of it's draw distance. Regardless of how powerful your rig is it's going to be using near 100% of resources whilst it's stuck in that loop.

A bit like the cards at the end of a game of Windows Solitaire.

 

Edited March 17, 20215 yr by Will Fly For Cheese

55 minutes ago, Will Fly For Cheese said:

It's like something is issuing a draw call an infinite amount of times until you're clear of it's draw distance

I'm not sure.... I experienced this yesterday while parked on the ramp. Fluid FPS one moment then the stutters (more like mini pauses) hit. I continued to ignore it as best I could and went about setting up the MCDU and after a short while (maybe 60 seconds), FPS returned to normal. Maybe not the same issue but I never got  this nonsense prior to Update 3 and often fly from this airport. It seems to me to be more random than draw calls on specific scenery areas.

17 minutes ago, RaptyrOne said:

I'm not sure.... I experienced this yesterday while parked on the ramp. Fluid FPS one moment then the stutters (more like mini pauses) hit. I continued to ignore it as best I could and went about setting up the MCDU and after a short while (maybe 60 seconds), FPS returned to normal. Maybe not the same issue but I never got  this nonsense prior to Update 3 and often fly from this airport. It seems to me to be more random than draw calls on specific scenery areas.

That's it. You got the bug.

See here;

https://forums.flightsimulator.com/t/issue-performances-issues/379531

 

Yes Asobo officially acknowledge there is a problem now. So for all those that were saying it's in our head or only affecting a few...

If this has been mentioned before, I apologize, but didn't see it above.  Remember when the World Update 3 United Kingdom was delayed before  being released because there was a rendering problem with the new scenery?  It was about this time that the dramatic reduction in performance took place.  I think they need look no further back than what they did to the sim during that interval to discover the problem.  My two cents.

 

I sent another Zen.desk support request and as usual I got the same guff about reducing render scaling to 80 BUT:

with a new line saying "While waiting for a patch". Hopefully this means the midnight oil is being burned and we'll get a Hotfix.

 

Hi Will,

This issue has been tracked in our internal bug tracker and is currently under investigation. 

While waiting for a patch, please try the following:
 

• Launch Microsoft Flight Simulator
• Go to Options > General
• Select Graphics
• Under Advanced Settings and scale down "Render Scaling" to 80 instead of 100 or above.

4 minutes ago, Will Fly For Cheese said:

I sent another Zen.desk support request and as usual I got the same guff about reducing render scaling to 80 BUT:

with a new line saying "While waiting for a patch". Hopefully this means the midnight oil is being burned and we'll get a Hotfix.

 

Hi Will,

This issue has been tracked in our internal bug tracker and is currently under investigation. 

While waiting for a patch, please try the following:
 

• Launch Microsoft Flight Simulator
• Go to Options > General
• Select Graphics
• Under Advanced Settings and scale down "Render Scaling" to 80 instead of 100 or above.

That line was not included in the reply I got on Monday, so as you say there is hopefully a patch coming.

Btw: For me it works better to adjust the "Terrain Level of Detail" slider than the "Render Scaling" slider.

6 hours ago, Will Fly For Cheese said:

Regardless of how powerful your rig is it's going to be using near 100% of resources whilst it's stuck in that loop.

Except that it's not anywhere near 100% of resources. When I was experimenting the other day, the worst spec was 80% use of 1 core. The fans didn't even kick up to high speed. It's slowing down on its own, not hitting a hardware performance limit.

Plus, I would think draw calls would be suspended regardless when you escape out into the settings pages, but the menus are just as slow as the sim when the bug hits.

 

I think I had the bug for the first time last night.  Everything was smooth, 30-40fps as I approached San Francisco and then I had several occupancies where the FPS would drop to 15, stay there for a minute or so, then return to normal.  I do run render scaling at 80 already.

For me the phenomenon has appeared for two days and it still appears in flight 2 minutes after takeoff but never on the tarmac.
I’m trying to scale to 80.

I wonder if anyone else is getting this - have had it with the FlyingIron Spitfire & Aerosoft CRJ 700.

Taxiing the 700 at Dublin Airport in cockpit view when without warning pressing the 'End' key to switch to Outside view does not work, hitting the Joystick key for brakes or parking brake does not work, yet aircraft continues to taxi. Pressing Pause does not Pause the aircraft.

Only way I could stop this was to hit the Escape key & the aircraft movement stopped. After about 15 seconds I could see some 'movement' behind the 'Boxes' on screen & pressing Resume with the mouse took me back to the now taxiing again aircraft, but I could change the view from Cockpit to External via the End key.

It did this 3 times before takeoff, then in flight it did it again, it locked into External view & I couldn't get Cockpit view.

T45

Q for folks have the CRJ up and running.

I managed  to get the CRJ up and running (It works sometimes) and I flew a full flight plan from Sim Brief from KDFW to KIAH. Did not read any stinking manual. HA HA 🙂

Used the Auto Pilot to navigate the flight which it did nicely but I had a hellaof a time maintaining altitude.. It was weaving up and down by pluss or minus 2000 feet. Been fighting with the throttle and VS to maintain altitude. 

I used the AP altitude tihngi like I would in any aircraft. Tuned in the altitude, pressed ALT button and then the VS and dialed in the VS feets per minute using the Down/UP rollon thingi. It started climbing, but went past my altitude and I had to take over to come down to the level I needed to be. andn then it started the descend, it was up and done the whole trip. But Nav was fine.

Any ideas? 🙂