wickedbacon

@Fly2021 I have rectified the issue, and tested with latest AIRAC. All procedures are available once again, I will push the update by Monday, as there are a few more items I want to address as well.

I'll be back on finishing the risidual structures and remaining skyscrapers after this upddate to KSAT itself! Should be finishing it this weekend, it's massive. In a great way, 3GB removed from package size so far, while increasing quality tenfold! Stay tuned!

Unsure of what you mean by Mud field, care to explain a bit more/send screenshots? What are your system specs, a screenshot of your in sim graphics settings if you can, and have you looked through some previous threads in here? this one specifically.

I do plan to add passengers, though it will not be in the next update as I want to do them a specific way which will take some time, next update is focused on finishing curbside properly and re-doing certain assets in a seamless manner to reduce texture size of the whole package drastically, here's a few screenshots of next update.

If you're available for a one on one via discord, I'm more than happy to see what's going on and what we're missing, just let me know, i'm here all day. discord username: Wickedbacon#5798

Just to be certain, you cleared the SceneryIndexes folder? I amended my original post where I mistakenly pointed towards the SceneryCache folder (that one is perfectly fine to delete as well) I've assisted two more users through the night, both of which have seen drastic improvements. One of which has the exact system you do.

Your terrain level of detail will be the main culprit, leave it at 100, photogrammetry cities weigh heavily on that, the photogram buildings are terrain mesh, not actual object mesh, they are all affected by that setting. What are your system specs, and did you follow and do my above recommendation to clear cached files?

I'm super happy to hear that! Terrain LOD over the course of the sim has turned into a massive stutter-enducer, hopefully they find a happy median!

I should be thanking you for your patience on getting it all running for you, so thank you for working with me!

HIgh uses 100% albedo (Color) resolution and 50% normal map/PBR map, it is essential especially with higher hitting packages, KSAT at ultra is somewhere around 6GB of textures, you cut that in half and lose barely noticable/un-noticeable quality. I would literally, only ever use ultra if I was running a 3090TI, with it's 24GB of VRAM.

Here is just before 1.0.7 release, completely stutter free, WITH 100% AIG traffic injected. https://streamable.com/ds3ip4

What GPU? I may be blind but I don't see it listed there. Even with my 2080ti, I don't touch ultra textures, that is most definitely the cause. Stuttering will be because of Terrain LOD, that's completely CPU based, and in heavy photogrammetry area, even with all the decimation, I leave it happy at 100. Here are my settings, System specs currently are: i9 11900k @ 5.3ghz 64gb ddr4 g.skillz RAM RTX 2080ti

Post your system specs for me, as well as screenshot your in sim settings.

Apologies! I pointed to the wrong folder, still completely a good idea to remove scenerycache folder, this is also regenerated on start when it is not present. The correct repository is right below it. SceneryIndexes. Attached below is a file view of the indexes folder, if you open yours, you will likely have a plethora of files in there that follow the naming convention such as "FIlexxxx" Those are depracated now, and users I've assisted the last few days have all had those files still present, as well as content.xml, which has the same naming conventions as they used to be in that xml, but separated as index files in the SceneryIndexes folder.

I owe you an apology! Though, deleting the scenerycache folder is always recommended on updates! This is the correct folder to delete, Rookie mistake, been explaining this for days! 😅 Attached below is a file view of the indexes folder, if you open yours, you will likely have a plethora of files in there that follow the naming convention such as "FIlexxxx" Those are depracated now, and users I've assisted the last few days have all had those files still present, as well as content.xml, which has the same naming conventions as they used to be in that xml, but separated as index files in the SceneryIndexes folder.

On my above post, this was explained. The further explaination, MSFS no longer uses the content.xml, it is GONE by default now. Only addons that require a content.xml to over-write base files can generate one. Navigraph is an example of an addon that requires the content.xml, and if you use it, load the navdata center app, there will be an update, and when you update the AIRAC, it generates the content.xml for you.

Another test with TAA, and loaded in FSTL traffic just for the added strain. FPS meter and nVidia overlay to show. But here's the real showcase, here's prior to 1.0.7 release, in the PMDG, with my normal settings on previous post, and 100% AIG traffic injected. Day and night, no stutters even when yanking the camera at a speed not likely for normal users. https://streamable.com/ds3ip4 If you use discord, please reach out to me, Wickedbacon#5798 I'm more than happy to screenshare and assist in managing performance, optimizing settings that are not-so-optimized/ready in the sim. The 7 or so users I've done a one-on-one with, all have immensely increased their performance not just for KSAT, for the entirety of the simulator. With a variety of systems, some more dated than others, KSAT for instance, in it's whole phase of development, it was entirely created on my old i7 7700k, 32gb of ram and 1080ti hybrid.

@zburns896 Along with my settings here

Screenshot your settings for me please. My system currently is an i9 11900k, 64GB DDR4, RTX 2080ti. Current FPS as I sit in the PMDG 737-700.

You likely need to clear MSFS's roaming files, after SU10, 99% of users files were not re-newed, and doubled up, since content.xml no longer structures sceneries.(drive):\Users\(you)\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCachein here, you will need to delete these two items in the below screenshot. (If you are hesitant on deleting these, just move them out of this folder onto your desktop, or somewhere, for peace of mind.) *NOTE - Upon deleting these files, re-run Navigraph NavData center, there will be an update if you have not done so since SU10, and re-install your AIRAC cycle, this will re-generate the content.xml for navigraph only, as it relies on it.Load up the sim, these files will regenerate upon restarting MSFS. 9/10 users will see a massive performance increase across the entire sim.Also note, this is not something specific to KSAT, or iniscene packages specifically, it affects every package you install as well as the base MSFS packages, performance increase across the board entirely. This should be done EVERY update MSFS receives, to ensure nominal performance. Worth mentioning, if you utilize a roaming cache, delete and re-generate it every update as well, or opt to not use it, as I do.

@alxvown You likely need to clear MSFS's roaming files, after SU10, 99% of users files were not re-newed, and doubled up, since content.xml no longer structures sceneries. (drive):\Users\(you)\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache in here, you will need to delete these two items in the below screenshot. (If you are hesitant on deleting these, just move them out of this folder onto your desktop, or somewhere, for peace of mind.) *NOTE - Upon deleting these files, re-run Navigraph NavData center, there will be an update if you have not done so since SU10, and re-install your AIRAC cycle, this will re-generate the content.xml for navigraph only, as it relies on it. Load up the sim, these files will regenerate upon restarting MSFS. 9/10 users will see a massive performance increase across the entire sim. Also note, this is not something specific to KSAT, or iniscene packages specifically, it affects every package you install as well as the base MSFS packages, performance increase across the board entirely. This should be done EVERY update MSFS receives, to ensure nominal performance. Worth mentioning, if you utilize a roaming cache, delete and re-generate it every update as well, or opt to not use it, as I do.

I'm finalizing the uploads, here's the results on my end. i7 7700k @4.5ghz RTX 2080ti 32GB DDR4 Asus Z70E Complete stress test, kicked the graphics up to Ultra, from 2k-4k, high to ultra for everything else. AIG traffic at 100% in the PMDG 737-700. And aiming toward the problem areas. Please do report if you are still having issues after this update is released, look out for an announcement. Fingers crossed, thanks everyone.

I'll be pushing another update today, i've tracked down the root cause of the issues, and the residual that followed. FPS on my end has returned to better than pre-release builds, adding more optimization to areas around the field. To enlighten, the main cause of the issues were sloppy old terraforms, paired with the modeled highway underpass and overpass which are all road collision objects, in the middle of photogrammetry, anytime you'd look towards it, you could see the fluctuation. Happy to have minimized that drastically. Will report back when i've pushed the update.

If you have some time for some debugging, I will be around for a little while longer, have some things for you to try to get started on a fresh community structure and clear cache what not. here's a build being pushed out here soon that has more optimizations, there will be a few updates to come with more optimizations as I find them.