Xbox X, PG on, 32GB cache, 1Gb hardwired internet, free flight only, comparisons to released SU1.
C172, 115KT GS, 2000ft AGL. Draw distance >10nm looked smoother. Planes around airports were visible from very good distance, EFB functionality improved. Load time to start a flight varied from extremely long to never.
C700, 480KT GS, 2000ft AGL to FL320. Draw distance was HORRIBLE. No details at all beyond 1-2nm. Near airports low and slower can’t see anything beyond 1nm! Load times long to never.
No CTDs but after just spending over an hour trying to start a flight anywhere with the C172 and never being able to fly at all anywhere I had no choice but to leave the beta and go back to SU1.
If you don’t mind me asking, what kind of flying do you do that PG makes such a difference? I have yet to find where and when it makes much difference that I can see. Thanks for sharing.
I have almost the same configuration, the difference is 64 GB DDR5 ram and a higher resolution because of triple monitor config.
I have less problems with Vram on high settings, but i have set trees, grass, rocks, fauna and depth of field on medium, live traffic and ATC off. I use BeyondATC for that.
Very occasionally I see higher Vram usage in very crowded and detailed scenery areas, but most of the time i am below 9 or 10 GB.
I fly with DLSS on Quality and FSR3 Frame generation.
At the moment i have the Nvidia 572.83 driver clean installed and nothing set in the Nvidia app or profile inspector.
I know you were not asking me so apologies for answering out of turn . In my case I love to explore new places I hope to visit in real life flying VFR low and slow. AKA sightseeing. PG, as bad as it is in some places, gives me a much better view of how things really look vs the fake buildings generated when it is off. It’s the main reason I left Xplane and came back to MSFS with 2020. But to each his own… It’s just what I enjoy.
Cheers
Interesting, because in trying to understand exactly what PG is and is not, one explanation I have read more than once is that PG is intended to be viewed from high altitude, where those strange melted chocolate conflagrations are not visible as such. Those explanations go on to say that PG should be turned OFF when flying down low. Thoughts?
I do get the sightseeing thing though, I enjoy that too!
I agree that I wouldn’t fly without PG. I tend to fly mainly below 1,000’ AGL and usually in helicopters.
I’d compare PG to procedurally generated buildings the same as 3rd party airports to default procedurally generated airports. They’re both a fair representation of what exists in the real world but if you know the area the differences are obvious. I want my exploration of the sim world to be as close as possible to what actually exists in the real world. I often chose to fly in particular areas because I’ve seen photos or videos of the region and want to “see” it for myself.
No doubt PG looks worse the closer you get in many cases! I think there is a sweet spot at about 2000ft AGL where the buildings, houses, skylines and streets look more realistic with it on. Get any closer and they turn to wonky clay.
The recent PG is a much higher quality where you can even read hotel and bank names or advertising on some buildings. Admittedly not as sharp as procedurally generated buildings but getting better all the time.
I had PG off until SU1. It improved a lot since release on XSX, the definition of terrain elevation was alot better and the melting of trees and buildings much much less than November release build.
It’s something I’ll probably have to keep testing with each SU build. Because we seem to go backwards sometimes in terms of LOD and memory
Maybe not the best place to have this conversation but enjoyable… I know that MS has much more up-to-date and detailed PG that one can see with Bing maps. I am hopeful the better detail will make its way into MSFS soon. Frankly cannot understand why it’s not there already.
Right, to keep on-topic, are folks finding the PG in SU2 to be improved over SU1? With the improvements in memory usage, there should be a corresponding improvement in either PG quality or playability with PG enabled, correct?
Better PG? Not at all. I think the underlying PG data is the limit. In some low and slow cases the draw distance was slightly better. But up close the exact same rendition of the exact same low res elevation data and photo texture map. IE, drawing lumpy clay in SU2 still looks like the same lumpy clay that SU1 could draw. Only difference seems to be that SU2 can’t always draw it from as far away.
Because I am a crazy person, I thought I’d test out VR.
I reset VR settings to defaults, so I have not tried any of this foveated business (everything around here is now “foveated” — the dog, dinner, your mom…), so I don’t know if it behaves beyond whatever defaults the sim chose for my setup, but WOW, it’s freaking awesome!
I had not flown in VR in quite awhile. Dang this is totally rad.
I did have some issues with CTDs when clicking the ready to fly (is that what the button says?), so I just remained in 2D until I got into the cockpit and then switched to VR and it worked great.
I’ve just tried out the venerable C172 G1000, but still it is really stinking cool.
I had to leave the beta because of blurred textures, poor PG and constant CTDs mainly in menus but a couple in flight too. I’m hoping it’s just server side tweaking needed as it all seems to be related to streaming.
I wouldn’t expect the PG quality to improve in SU2 though. I’m sure I’m getting what they send and the same base PG is being used. I would expect a performance improvement though. Some areas where I get good performance in the Bell 407 can give some stuttering in the Huey. I’d hope to see an improvement in the Huey once SU2 is usable. That’s my usual test flight over LA and LAX as I know it’s marginal.
Pleased to report that I just completed a KDCA to KBOS flight in the Fenix 320 + BATC with no issues. Two key things: get on the su2 branch for Fenix, and remove FSLTL from community, seems that’s a major source of CTD right now. Will have to wait on traffic injection with BATC. Used DLSS with no issues. 14700k/3080FE/64GB RAM, on newest nvidia driver.