somiller

During install I believe it offers an option to start Couatl with MSFS - either select yes or you will need to start Couatl manually. In Windows Start menu you should have an FSDreamTeam folder and within should be a Couatl shortcut to start Couatl. If you right click Couatl in the start menu, select "more" then select "open file location" which should take you to the shortcut. Right click the Couatl shortcut then select open file location which should take you to the the location of Couatl64_MSFS2024.exe. Try double-clicking Couatl64_MSFS2024.exe to see if it launches.

Please go back to "old" avsim format prior to about 3 days ago.

Scott, The ignore feature on AVSIM works REALLY well...suggest you try it.

I've also seen the freezing aircraft. sometimes on taxiways, and other times on runways - after lining up for takeoff, and also after landing rollout.

I'm really curious about the aig-aitraffic-effects_CVT_ , what is it? I don't have that one in my AIG install.

SayAgain, Karens gotta Karen - they can't help themselves. The idea that culling landing gear at a certain distance is going to improve performance when landing gear represent infinitesimally small percentage of vertices in an airport environment is so ludicrous it's really difficult to try and speak about it with any seriousness. I'd like to hear the argument that was used to incorporate this idea into MSFS 2024. Even on my week system it's not like I see a performance improvement when landing gear disappear. And as SayAgain mentions how hard would it have been to included a slider setting that allows us to control the aggressiveness of the culling.

I'm curious for those that use multi-monitor setups - how do you handle monitor calibration so all monitors color-match? To me there is nothing more annoying/distracting than multiple-monitor setups with monitor colors that don't match.

LittleNavMap aircraft labels used to show origin and destination for most PSXT controlled AI with MSFS 2020, but origin and destination seem to not be available for PSXT controlled aircraft when using LNM with MSFS 2024.

Absolutely NOT 1300 feet away. If it were 1300 feet away I'd barely be able to see them, if at all on my 1440p monitor. I'd go along with maybe 300-500 feet, but not beyond. I wanted to test what I wrote above so I loaded a flight in MSFS 2024 and found something VERY interesting that seems to have solved the gear problem, at least for me. I use ChasePlane, but the same thing can be done for views setup in MSFS - I use a zoom factor of 0.76 to provide a realistic field of view (magnification) calculated from a tool here https://www.avsim.com/forums/topic/669373-how-to-easily-set-up-a-realistic-field-of-view-fov/#comment-5440264. I use ChasePlane but views setup in MSFS can also be customized to alter zoom. From my cockpit view with zoom 0.76 landing gear on AIG AI appear at quite a long distance - further than I can distinguish on my 1440p monitor. From an external view with a default zoom factor of 0.53ish landing gear are missing beyond a range of roughly 300-500 feet. When I went into CP and changed the zoom to 0.76 for my external views...all the missing landing gear appear and are visible beyond ability to distinguish whether they are there or whether they aren't. So zoom may affect gear visibility. I messed with OLOD and could make gear appear and disappear at varying distances, but not equally on on AIG models. On some the gear disappears within 500 or so ft. at OLOD 100, and yet other models the gear doesn't disappear beyond my ability to see them on my monitor. So I think we have several factors affecting gear visibility, including inconsistencies between models of AIG aircraft. As far as path to default models I'd say here: MSFS2024\StreamedPackages which contains these:

SayAgain is referring to the landing gear culling issue that we all see with AIG, FSLTL, etc. liveries. At a certain distance (which is a rather short distance) the landing gear disappear from AI traffic. We've all been dealing with this for some time and it really looks ridiculous to see aircraft taxiing around you with no gear looking like they're magically levitating. I've done some tests while sitting at a gate a moving around in external camera and as you move away from AI the gear disppears, then if you move closer they reappear - all very repeatable. Clearly it is caused by MSFS 2024, I suspect for performance, but I would argue there are other scenery areas of lower importance that could be culled instead that would provide an equal performance improvement. The worst thing about it is that those with high performance systems don't need the performance help from culling, and some of us with lower spec systems would be happy to give up a small bit of performance to NOT see levitating AI.

I would suggest you will probably need to add an lfolder entry pointing to the location of stock MSFS AI, then try unchecking the automatic checkbox and run a livery scan. Throwing darts but that is where I would begin.

As part of a support session I had with WINCTRL they indicated there should be no issue starting SimAppPro AFTER MSFS 2024 is up and running, including starting SAP after one has fully loaded a flight. Give that a try - that is my standard workflow on most flights and SAP connects to MSFS and the aircraft with no issue.

And PLEASE use the spoiler (eye icon) when posting logs. Good grief it's almost impossible to scroll these threads with full logs!

ChasePlane provides the body movements etc. and the amount is selectable. You can assign your keyboard shortcuts to the views in ChasePlane but you'd probably have to do it individually for each aircraft. Admittedly I haven't spent a lot of learning many functions of CP, but I use it every flight and have custom view settings for every aircraft.

Don't give up. I installed 2024 for the first time less than 6 months ago and after about 30 days I finally got the courage to uninstall 2020. With correct settings 2024 looks so real it's almost hard to believe. You have a strong system so pay attention to shadow, reflection, ambient occlusion and raytrace settings...turn them up - they make lighting of objects look very real. You won't believe how good the PMDG flight decks look when you get your sim lighting settings right.

No, I think you're the only one. Nice of SWS to make an aircraft just for you.

Flightplans go here: C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-738\work\Flightplans and weather/wind files go here: C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-738\work\WX

I just wish they'd give us an option for UI location on the monitor - sometimes it pops up on the left side, sometimes it pops up on the right side. The other issue I have now is most functions in the UI require that I try 2 or 3 times or more before my request is acted on - never experienced this before the latest hotfixes.

It is but I've found it worth the effort. AIG installer is a lesson in how NOT to build a user interface. It has to be the most confusing, backward UI of any software I've ever used outside my job at UPS - now THEY know how to create garbage UI's.

I had the same issue last night RT Direct. Started PSXT and it just sat there...didn't connect to MSFS 2024, didn't verify RT license...nothing. So I switched to RT App, restarted PSXT and started RT App and same thing. Then I wanted to switch back to RT Direct and it was greyed out and I couldn't change it. Closed and restarted PSXT, then I could select Direct and then it connected to MSFS 2024, verified RT license and all worked perfectly. My issues occurred around 0100 UTC. Never seen this before last night.

Good to know - I'll make sure to kill my saved panel states and recreate them. As a matter of fact, did that just now, and in options.ini I replaced my custom startup state with COLDDARKGPU which is a PMDG installed state.

What is this Gemini of which you speak? More broadly, what is the subject of this post?

The windscreen window fit/alignment is terrible on the -700. Also on the pillar exteriors between the glass there are remnants of low-res screws. Has to be one of the laziest efforts at high detail I can imagine - what a joke. I bought it since I owned the 2020 ver. and it was only 30 bucks - good thing I had no expectation regarding the "high detail". The downside is that it is less performant on my rudimentary system. I get great performance with the -800 and -900 and would GLADLY trade their definition of "high detail" for that performance.

I've highlighted in yellow what SAP is looking for, specifically: 1.) "wgs" folder 2.) "Microsoft Flight Simulator 2024" folder 3.) "OneStore" folder 4.) "Community" folder Select the 3 dots at the end of each field and navigate to and select the folder indicated. If you have selected the wrong folder, or an invalid path, the text in the field will be red. For each path that is correct the text will be white. That should be all you need...but of course I have assumed you have the MS Store version...if not simply do the same thing for the Steam fields.

Nope, still now idea what you are carrying on about...looks like another opportunity to use the ignore function so kindly provided by avsim!