I still have this issue, I got an email via Zendesk saying this was classed under the “photogrammetry not loading correctly for some users” category and was under investigation. Ultimately with PG turned on my sim is unusable when below 300ft, above that its smooth as silk.
Out of curiosity, as this came after the Xbox implementation, are all users who are having the issue also using this on an Xbox? I can confirm I am. It’s probably a complete red herring but wondering if there is a link between the two?
Just a quick edit as this is first time in about 4 weeks I’ve had chance to spend any time with the sim, whilst truning off PG removes the issue, so does setting TLOD to 10, I’m assuming the two settings are linked?
I use a PC, not XBox, and have had the same problem for several weeks now.
On or near the ground (all planes + all airports) sim ususable witrh photogrammetry switched on. All fine if PG switiched off.
Yes it seems that it has something to do with LOD and mesh loading. Did you report that to Zendek? When I filed my report I did not know that yet and just explained about photogrammetry ON/OFF and above 300ft being super smooth again.
I am having issues with photogrammetry, too, after SU6. At the start of the flight it’s no problem, but when I fly over PG cities the FPS gets worse and worse, and even worse when I approach an airport near a PG city. E.g. last two flights where FPS dropped considerably over time were to EDDF and EGLL, the latter overflying several german PG cities additionally.
I do not have rolling cache, so that must be a server problem (or a memory leak introduced in SU6).
That’s something I noticed too, I think it’s a memory leak, if I restart the game at the same airport everything is fine again, but this problem existed even before SU6.
I managed to reinstall Windows 11 (while doing a factory reset to my PC). I also used the opportunity to add in a new secondary SSD drive to install MSFS. I installed the game through the Xbox (GamePass) app, Standard Edition. I actually had to do it all twice but that was my fault…
The whole process was a giant PIA, but at this point I had tried everything with no luck and decided to do a factory reset. So I felt like I had no choice. I really hope I don’t have to do this again anytime soon.
As of now, with the game fully “stock” - no world updates installed or anything… I took off using the Asobo A320 from KMCO. The game now runs very smoothly at the default “high” graphic settings and with photogrammetry on. (I have not tried to play with additional data and graphic settings yet).
I plan to slowly add additional stuff in; most likely in the following order NVIDIA Control Panel (to cap FPS), World Update Files, Marketplace purchases, Navigraph software, Volanta, Little Nav Map, A32NX, then my payware 3rd Party planes and airports (PMDG, Aerosoft, Just Flight, Orbx), by adding them one by one; most likely on a “as needed” basis. Finally when I’m comfortable with that, I’ll add my freeware community folder files I had previously downloaded from FlightSim.to.
So this may take some time but I will try to update this thread if/when I get unexpected results… But I suspect my issue is most likely fixed, using the solution that @Ixoye56 had originally suggested.
Amazing! Thanks so much for the info. So then what the heck is causing this in windows that affects photogrametry? I am still hopeful that someone will be able to isolate the issue that prevents us from having to do a clean install of windows.
I solved the Probelem by reinstalling Windows. However you could try to delete the MSFS2020 completely. I think that through the normal uninstallation still data and paths remain.
Try for example with the “Revo Uninstaller Pro” to remove MSFS2020. The program is available as a trial version and also deletes remaining files and registry entries.
I did just that before I reinstalled Windows, I made sure there was no trace of MSFS left on my HD before I reinstalled the game and tested it in completely vanilla state, but the problem remained, then I decided to do a clean install of windows as a last resort when I suspected that the problem must be in Windows and not in the game, and I had reason to believe that because I had a power outage while patching the game.
This is interesting. [PacificSet90456]
There is something badly broken here that might be different than other posts about poor performance.
The FPS counter shows 2.0 FPS or 500,0 ms to render a frame and send it to the display. The FPS counter shows that RdrThread is the bottleneck because it takes 1067.6 ms for the RdrThread to process a frame (or whatever it processes). If the display gets a frame every 500 ms and the RdrThread takes 1067 ms to do its processing, the GPU is displaying 2+ frames for each RdrThread frame processed. (assuming the FPS counter is accurate) Could the GPU be sending duplicate frames while it waits for the RdrThread to finish? Without understanding the internals of the graphics pipeline, it is impossible to determine what is happening.
