So 13 is my lucky number and it appears to me that my luck is holding up with this release. While I did lose some frame rate during this 2 hour flight, it was less than the prior two releases and with acceptable control resolution for hand flying a brisk crosswind approach to KIAD (GlideslopePro 2024 version) in the Max 8. Frame rates are as displayed by Nvidia app overlay (Alt-R) to avoid activating Dev Mode (as I am also testing to see if my logbook entries still disappear in .13).
Departing KMSP (Flightbeam 2020) had 55 FPS or better up to my 60 FPS monitor refresh rate maximum with butter smooth panning inside and outside the cockpit.
Flight time
1:26 @ T/D 52 FPS 30 (1% L) stuttering panning inside the cockpit began
1:37 BETEE 47 FPS 30 (1% L) with stuttering outside the cockpit on the STAR
1:45 ELLLA 46 FPS 30 (1% L) with stuttering outside the cockpit on the ILS
1:50 @ 3,000â 42 FPS 24 (1% L) off A/P at 2,500â when fully configured to land
1:54 ET/on the ground 35 FPS 15-24 (1% L) with enough control to taxi normally
At gate FPS recovered to 40 FPS 20-30 (1% L).
While not enough or the right kind of data to posit a VRAM fix, this is performance enough for me to be satisfied with .13 over all previous SU2 beta releases on PC.
Nope, that message was added very early one, maybe as part of the first or second patches after the sim was first launched back in late November. I havenât seen it personally since those initial few weeks when it seemed like every day was a new set of problems and long sim loading times were common.
I tried the new 13 patch earlier for only a little while as I was getting ready to go on holiday. Took off from John lennon and wow, it looked amazing, flew over the mersey, over the wirral, over the river Dee and onto my hometown. The browny colours of the rivers were near perfect
Latest startup time with 1.4.13.0 is 2:23, down from about 3.5 minutes back in November, whatever Beta was in effect then (SU1?). Things seem smooth with FSR3, AFMF, although maybe not as smooth as with 1.4.12.0, and FPS maybe a little less. Overall, itâs quite good, though. I do experience an occasional CTD or freeze, however.
My experience with pretty much all of the Beta flightings, up to .13, has generally been good:
Load times are great: even with FSLTL models, load to menu is around 1:15. From menu âStart flightâ to âReady to flyâ around 30 sec.-ish. Note that I typically do not do multiple flights without exiting the sim so the ârepeated flights slow downâ is not a concern to me.
Frame rates are the best I have ever had. Flying GA low-ish (1500 - 2500ft AGL) and slow-ish (110 - 175kts) over PG still delivers 40 - 60FPS, depending on what is in view. Capped at 60 FPS, virtually never goes below 40FPS
I still experience some stuttering on landing, in spite of good framerates. Not awful but enough to be annoying. Typical CapFrameX capture for landing:
VRAM is still dodgy. Loading into hand crafted airport with airliner still bumps up against available VRAM on my RTX 4080 Super with attendant sudden plummeting FPS.
Air traffic is still dodgy. At for instance EGLL, parked, taxiing and taking off FSLTL traffic is fine. Landings are still rare with âlow passesâ the norm. Otherwise traffic looks good: at EGLL for instance with FSLTL
Something I have to look into in detail: I have an issue with CTD when spawning at a gate @ KJFK. I tried a number of times to spawn at C1004 - cannot for the moment recall who it was but SOMEONE used that as a benchmark some time ago and I get consistent CTD there. Tried with Inibuilds A320V2 and A321. Seems OK if I spawn at the runway with decent FPS though: refer KJFK screenshot under bullet point 5 above.
Detail at small airports is just gorgeous. Couple of examples at 3W5 Concrete:
For my GA type flying the sim is generally extremely good at the moment.
PS: Should have included my specs!
Summary
Hardware:
ASRock X670E PG Lightning
9800X3D
Gigabyte RTX 4080 Super
G.SKILL Flare X Series 64GB 6000 CAS 30 2x32GB
OS WD Black SN770 500GB
Game WD Black SN850X 2TB
NVIDIA 566.36 driver
I must admit that, until you pointed these out, neither of these two issues were apparent to me: my ignorance is clearly showing. As is my lack of âmeticulousnessâ as quite frankly, for a small rural airport, I am quite OK with how it is represented in the sim.
Runway numbers:
Yep, after you pointed it out, further checking indicated that indeed it isnât 100% correct. Sim:
Not sure Iâm following except for the runway numbers size. The rest seems to look correct to me. The magnetic headings of the runways will drift over time since the magnetic north pole is not stationary. At some point they may re-number the runways in a future AIRAC update.
My last post was in response to CharlieFox00âs comment that âthe runway needs to be realigned to the aerial and the runway number is incorrectly applied and mis-sizedâ.
Just had my first CTD in the sim menus in a while. I had just loaded up, selected Free Flight and then accidentally clicked a spot on the globe (if it matters) and the little UI widget popped up as if I was selecting a starting point. Immediately after that, when clicking on the aircraft icon to change planes, the sim crashed.
and I get consistent CTD there. Tried with Inibuilds A320V2 and A321. Seems OK if I spawn at the runway with decent FPS though: refer KJFK screenshot under bullet point 5 above.
