I have a mid-range computer at best - i5-9500, NVDA 1060, 32GB RAM, so I don’t expect miracles. I can usually fly in the low 20s frame rates even in some of the more complex airports, cities. I have tried flying repeatedly from KBOS to KEWR. I start of the flight is in the 20s and continues over Boston. Just southwest of Boston, by Norwood Airport, frame rates drop into the teens and then single digits. I haven’t had time to complete the flight, but this continues through to at least the LI Sound.
Anyone else having similar issues in the area?
I assume you’re flying a jet and it would sorta make sense as you climb and head southwest that the sim would begin modeling NYC which is a chore?
I’m constantly around KBOS but I’m always in GA so the sim has plenty of time to paint the pictures ahead of me.
I’ve noticed this as well on a flight to DC. The photogrammetry in that area is super poorly optimized I think causing it to drop to single digit FPS even at 15000 ft and above.
I’m frustrated at how bad the sim runs now in any photogrammetry areas. Looks pretty but it’s not usable in any way.
I just finished the flight. Again, single digits from Norwood to the LI Sound at 6000 ft. Then FR picked up to the low 20s. Approach sent me over KJFK then a hard right to KTEB over Brooklyn and downtown Manhattan, then straight into Rwy 22R at EWR. FR in the high teens, mostly low 20s until 1000 AGL where it stayed 15-20fps.
So again. that area SW of Boston and RI…
Yes, I’ve seen that on a flight into KBOS in the TBM 930.
I’d like to try your route since SNE and the Tri-State are my usual haunts. Are you using high level IFR? Can you share your PLN?
Just made the flight, no issues, in fact I was surprised at performance.
The only thing I can think I definitely am doing different is I have no idea how to fly the plane.
I sorta stumble bummed my way up to 5k and managed to get the alt hold and heading hold working.
All the rest of it was best guess hands on flying.
No contact with ATC other than leaving their airspace initially either.
Had one minor hiccup, a single stutter and took screen shot of task and resource but nothing exciting
So far ok. Ryzen 5 2600 RX580 16GB RAM
IFR Plan Enroute is FL150
KBOS BLIZZR4 SID KEWR
There was a hiccup just between Milbury and Auburn, dropped to 9 fps at the lowest then picked up again, running high 20s low 30s.
I can’t tell what the new traffic slider is doing (it’s partly busted after SU4), but I have plenty of offline AI traffic that’s probably consuming cycles that could go to FPS instead. That’s one of the things to check and validate - what’s your performance with offline traffic and preset weather vs. online?
@CasualClick you asked for my .pln file. Attached below…
KBOS-KEWR.PLN (7.8 KB)
Must be all that rush hour traffic on Rt. 20 and the Pike 
1 Like
Well we wont know until they model the WBZ copter.
Yes, just tested in the Piper Arrow. Dropped to 10 FPS over Norwood Muni and still there ten miles later. I did see a crack in the terrain around there not long after take off from Boston, but I don’t know if that’s related.
Hi @LarrySinNJ
I flew the plan, no single digit or teen drops around Norwood or after. I hawked the FPS counter (Steam) - there were momentary drops to as low as 22 just before Norwood but perhaps that happened twice. Overall high twenties, low thirties - I flew the route as far as PVD. Offline AI, Live Weather.
One of my performance test regions.
Lots of tree’s, lots of photogrammetry.
Usually fly this is smaller GA aircraft like VL-3 or Pitts.
It’s not as bad as Atlanta but it does perform quite poorly.
I think it’s the photogrammetry which then has layers of trees growing out of buildings and stuff.
Bingo finally someone that gets the idea!
Even Fenway Park has trees growing in the stands, and the field looks like it hasn’t been mowed. Looks pretty funny actually.
There is unrest in the city and the people all have fled for the buildings want more sunlight but the trees just shake their heads… bass riff
1 Like
Confirming that I am also getting low FPS southwest of KBOS. I had thought it was general performance degradation after repeatedly testing a KDCA-KBOS flight (see here: Help - performance plummets on approach), but I did a KDCA-KMIA this morning and it didn’t have the same degradation.
