Nemo

I'm I'm very close to reinstall MSFS from scratch because I have so many CTDs in recent times. Would this tool help to identify any conflicts of my current installation.

It seems that FSLTL makes my MSFS to crash in some areas/airports. E.g. FSLTL loads just fine at KLAS (FlyTampa) but crashes at KBFI (freeware). I have CTDs at some other areas too. I have not yet recognized any systematic that could cause it. Usually, I start MSFS, load a PMDG 737 at the airport before I start FSLTL. Shortly after some ai a/c have been injected the sim crashes. I have also AIG in my community folder, and FSLTL is using AIG liveries too. Any ideas what could be the reason, or suggestions to keep FSLTL working properly?

Anyone tested version 0.81? It appears that there is no need for the registry merge with this version.

Actually, it does only move 2.1 GB. This has been reported from many others. The real content folder with official and community folders is not gonna moved. So, don't worry!

After several experimental flights and trying different settings I have to say that this hack works relatively fine on my system (RTX 3090 + 13900K, NVCP: VertSync = ON, Frames capped at 58)). I still prefer the TAA mode though it can lead to extreme stuttering in some cases. But they can be cured mostly by going to DLSS mode and then back to TAA during flight. The only thing that bothers me a lot is the DX12 "texture shine through" bug at many airports. But this is independent from the FG hack I guess.

It depends when you installed MSFS on your system. Very early installs went into the WindowsApps folder later installs used the XboxGames directory. That's why I had to move it.

seems to be new, the obligate registration. Don't like it either. That's why I've asked whats the difference between 0.5 and 0.6.

anything else in v 0.6 better than in v 0.5?

see my post and the link to //42

You can move your MSFS installation from the WindowsApps folder to XBoxGames folder. I did that very recently and took me only a few minutes. I found a procedure on //42 homepage where they described it step by step because it was needed for one of their apps to work. https://parallel42.com/blogs/wiki/converting-my-sim-install-from-legacy-to-modern Don't be worried when you see it would require 150+ GB disk space. It does not touch your Content Folder if it installed elsewhere. In my case only 2.1 GB were moved into the new directory.

... as many other small issues. We got used to it ...

I'm regularly flying only with 5 or 6 different aircraft (payware and Asobo). As long as we don't have a personalized hangar (a/c favorites) I'd like to remove (uninstall) all that unused aircraft, keeping only 10-15 on my system. My question, would that do any harm? I'm not using any MS/Asobo flight challenges or scenic flights. For AI traffic I'm using exclusively FSLTL/AIG. As far as I understand, it should then be possible to remove most of MSFS/Asobo a/c without any disadvantages. Is there anything I forgot or I should consider?

Interesting topic. With a 13900k with 8 Performance Cores (16 threads wit HT on) I could disable HT I guess. But what about the remaining (active) 16 Efficiency Cores. Should I disable them too?

Thank you so much Rob! The move worked like a charm. Took more time to read and understand the //42 instructions than the move itself. I'm so happy that I can now access the content of that folder. Not only for the nvngx_dlss.dll replacement which was not so urgent for me. Much more important, I can now create MSFS profiles for two other apps which was not possible until now because these apps required the msfs.exe location for creating a profile.

How did you replace it? I have the MSFS Store version with C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe where the file is located. Cannot replace it. How did you?

The normal "save flight" function is pretty useless in my opinion. The only way it works is with PMDG because it saves flight plan and panel state separately. But you won't have the possibility to change the weather afterwards when you load the flight again.

the issue seems to be back. It was gone with the latest 2 or 3 betas but wit with the newest .21 ii is back. Nobody knows what is causing it.

I believe that too. I'm only using payware airports not sure what jetways they use. No GSX here. To repeat, the strange thing is, when loading into the airport everything is fine. But landing at the (same) airport no jetways are connected to ai a/c. Though, after traffic reset they get connected automatically. But that's not what I want to do every time. I'm just wondering why I cannot see any reports about this bug. Is it only on my install, then it could be possibly solved.

My pleasure, Vincent. If some "professionals" had the same enthusiasm as "amateurs" like you, that's what I wish ... Thank you!

That's not what I meant. It is true, when I start my flight at an airport, most a/c are connected and also arriving a/c become connected. But when I have just landed my a/c at the airport and taxi to the gates, I cannot see any a/c connected to the gates. This is with straight AIG too.

Whenever I land at any airport, none of the ai aircraft (FSLTL/AIG) is connected with a jetway. The only way to connect them is to reset FSLTL after landing. I'm not using GSX until now but would do if GSX connects them automatically.

Neither on store. Do they publish the release notes earlier than the new beta?

Jörg: Assistance reset bug is fixed by today.

Also ai a/c lights are like unreal squares too (not always). Does not look nice. It is on my list of "small" disturbing issues, PAPI lights (to weak), object LODs (pop ins), terrain LOD (washed out), ... . But obviously, most of us got used to it and don't complain anymore. Asobo/MS will never fix it.

Ok. All good again. There was a second PSXT folder in Appdata/Roaming. And additionally, the XML license entry was wrong. I deleted the older PSXT folder and manually added the license string in the today created PSXT XML.. Done.