JimBrown

Free to use, pay for premium features. ...jim

I believe it has been mentioned in a couple of different places, including the FSLTL discord, that this is NOT an FSLTL problem. It is an MSFS problem. FSLTL simply injects the aircraft, MSFS is responsible for placing the injected aircraft. And, as has been noted, this occurs when doing a return leg to the original airport without restarting the sim. And, I believe I saw it mentioned elsewhere that the issue has been fixed in the SU12 Beta. (I could be wrong on that one...) ...jim

For Steam, custom camera views are stored here: C:\Users\[user]\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes\[specific aircraft]\cameras.cfg I'm guessing that MSStore stores them similarly. ...jim

The only caveat I can think of is that some 3rd party freeware/payware may use assets from a specific world update. For example, a 3rd party airport for somewhere in the USA may use assets from the Canada world update or maybe assets from the Italy world update. ...jim

I believe the DLSSG option is for nVidia 40 series cards to enable DLSS Frame Generation. DLSSGVR is the Virtual Reality version of that option. If you do not have a 40 series nVidia graphics card, then these options will do nothing. ...jim

Here's the deal with the Beta and why Chris had to re-install the entire sim. The beta updates the .EXE file that launches the sim. It may also update some core sim files (the stuff that is in the "Official" folder). When one backs out of the beta, only the .EXE file is restored. Any changed core sim files are NOT restored. Sometimes this will cause issues (It did for SU11 beta, and it does for SU12 beta). The only recourse is to replace the changed core sim files with known good backups. System Restore will not help here. If one has the space, before joining a beta, make a backup of one's "Official" folder. If one decides to leave the beta, after doing so copy the backed up files back to their original location. Note that those with a MSStore installation in the default location may experience difficulties with this due to the wacky permissions that are assigned to those folders. ...jim

You only have 2 versions installed? I have 12 versions. Which would be all of the versions (x86 and x64) from 2005 to 2015-2022. Why do I have all those versions installed? Because many programs written in Visual C++ target a specific version of the Visual C++ Redistributable packages. With all of them installed, I don't have to worry about not having a needed package installed when I download some older bit of software. You can find an all in one package here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ ...jim

This was committed to the DEV version yesterday: https://github.com/flybywiresim/a32nx/pull/7781 Looks like what you are looking for. If you are on the DEV version, use the FBW installer to update. Note: I have not tried it myself... ...jim

I believe it got moved a couple of updates ago. While in the cockpit, it should be somewhere in the toolbar, perhaps under something like "flight assistance". It's been a while since I used it myself, so not exactly sure where it is. ...jim

After some quick googling, I came across these two suggestions: ...jim

Depends on what was changed in the front end UI by MS/Asobo. Some updates have required an update to Wingman UI. Some have not. The author of Wingman UI does get an update out pretty quickly if needed, particularly if there has been a beta available. Personally, I have been using the Wingman UI since it first came out, and have been quite satisfied with it. ...jim

As best I recall, they have been there since day 1. ...jim

Might want to give this a try: https://flightsim.to/file/22352/ms-fs-2020-modern-ui-2-0 I have it installed and I like it. ...jim

No longer used. Uses SimBridge instead. Available within the FBW Installer. ...jim

Being retired has its advantages... I'm up to 1,564 hours. So far. 😉 Most of that in the FBW A32NX. I'm sure there are others with more hours... ...jim