vgbaron

I echo all the sentiments posted. Living in SoCal, I have flown in the San Diego area for many years. Your work brings back very pleasant memories.

I've been using it for years - just doesn't look and feel the same when I fly without it.

Sorry Hans, I was referring to the MSCopilot excerpt in the posts above, which come from the release notes

I still don't have my head around this completely. Currently I have 3 community folders. The 2020 one in it's flightsimulatorxxxxxxccxxxx folder, the 2024 one in it's flightsimulatorLimitlessxcxcvxxx folder and the community2024 folder in "limitless". The doc says both will read from the same CF but only 2024 will read CF2024. I ASSUME if you needed, you could create a single CF and point both 2020 and 2024 to it and also have 2024 specific items in CF2024. I guess this would save space, I think I'll just leave my 2020CF where it is and ditto with 2024CF. The "new" CF2024 is empty anyway.

looks like it would be perfect for a small cabin, off grid with not too many electrical gadgets.

Can't see this one going anywhere but down. Interesting video, each side will make their own judgements.

I have no problem using the Turbine Duke in SU4. Perhaps something else in your community folder is interfering.

Total agreement Bert. A2A "early access" is better than many RTRM offerings. I'm loving it!

I can ban him, if you'd like! 🙂

I bought it. If I could get a refund I'd take it. Lack of documentation and flaky AP system make it an unenjoyable experience. Lastly, I can't quite put my finger on it but the panel gauges look strange, seem slightly distorted as compared to other a/c. When and if they have the initial patch, I'll revisit but for now - back on the shelf. The A2A Aerostar is a pre release and IMHO it's far better than this. EDIT: ok, I was in a bad mood - unfair critique. Finally figured out how to get some systems working and it's not as frustrating. Still think it needs some work but I wouldn't ask for a refund.

Since my 3 cats are indoor people, I don't have the issue. Also, I havent moved houses in 22 years. 🙂

Agreed!

Have you uninstalled it and reinstalled Could be corrupted.

Also double check that the video cable is inserted solidly. It's a longshot but something to eliminate. You need to beg, borrow or steal a second monitor. You can eliminate the video card etc by swapping parts.

Simply - According to Airhead, www.airheadatpl.com, when the propeller spins clockwise (as viewed from the cockpit), the aircraft body tends to rotate in the opposite direction (counterclockwise), resulting in a left-turning tendency. This is a direct application of Newton's Third Law of Motion: "For every action, there is an equal and opposite reaction".

It was hilarious. I pulled up between two cars and the looks on their faces was priceless. Tanks look bulky but they are surprisingly very maneuverable. Ah the old days!! 🙂

I once took an M47 tank into a drive in to get Bob's Big Boy hamburgers back when they had car hops. Caused quite a stir. Next day Commander issued an order that no military vehicles were allowed in public establishments. 😁

I'm puzzled. I have TDS GPS Manager 1.0.1.5 - I reinstalled TDS GTNXi Pro 1.3.0.0. I created a flight and loaded plan (import from file) into the 750. It also showed in the 650. I assume that would indicate crossfit was working BUT I only have tds-gtnxi-gauge (dated 5/18/25 in my CF. ?? Thanx

I found this - not at flight system so I can't try it: 1. TAWS Inhibit Mode: The G5000, like other Garmin TAWS systems, offers an "Inhibit Mode" that disables specific alerts deemed unnecessary by the aircrew. 2. Accessing Inhibit Mode: MFD: Locate the "TRAFFIC MAP" page and use the "MUTE" button to stop traffic callouts. TAWS Page: Find the "INHIBIT" button on the TAWS page to stop terrain callouts. Menu: Disable aural terrain warnings within the menu on the "heat map" page.

and to make it cleaner, delete all the unwanted custom profiles.

Works perfectly! Thanx! Vic

just doublechecked - mobiflight event module is there

Good to know. I've tried no community folder, no exe.xml, remove and reinstall app - same incompat issue. Log(in pdf form) attached for @Reset XPDR MSFS_AutoFPS20250524log.pdf

Hmm - I'm using SU3 Beta 1.5.3 and the last two test builds and the RC1 build fail the MSFS compat test. I tried changing MSFS settings etc, also did a clean install of the app. App recognizes SU3 and connects, then the sinconnect activates but when it gets to the session - error and close. I removed the MSFS cache, roaming downloads and scenery indexes - no help. Thanx!

Not on my system - still CTD