MDFlier

Not at all. It was obvious that PMDG would be modelling the entire MAX series for MSFS on the day that Boeing introduced the MAX to the public. That's like asking, "Wouldn't be funny if Ben & Jerry introduced a new ice cream flavor with a crazy name?".

I seriously doubt that PMDG cares.

It says that in addition to many other things. I wasn't speculating as to what the product does because as you state, it is all on their web page. I was speculating about the mechanics of how it was done.

I'm a bit surprised by some of the reactions that I've read here. This will be a day 1 buy for me. Active Sky has been on my "required flight sim addons" list forever (along with AIG and GSX). Damian just delivers. If he says it's in there and that it works, I believe him. I'm shocked that he's been able to keep a lid on it for this long. Didn't Seb (on second thought, it may have been Jorg) say something about "unlocking the weather APIs" a while back on one of the streams? At the time, it made me wonder if they had worked out something with Damian because as soon as I heard him say that, I thought to myself that Active Sky would be coming out soon after they did it. Maybe they did? Do we know for sure that Damian had to 'hack' his way into the MSFS' internals? Is it possible that the APIs were unlocked and AS is simply using them to control the individual weather elements instead of the internal MSFS weather engine doing it? A comment on the interface. It's perfect for what it is. I don't think I ever needed to access it during a flight. I only used it to set things up before the flight. Most of the time, it was left in live mode. I only used the interface if I specifically wanted to play around in a snowstorm or thunderstorm on a given day. It's been a couple of years, but I don't even remember having to mess with it to do a flight with historical weather. IIRC, Simbrief took care of that. The simple fact that the interface is the same gives me hope that the product itself will be substantially the same as it was. It worked great as it was. All I ever wanted was for it to move over to MSFS. I do not think the MSFS weather engine is all that bad for a default simulator weather engine. Asobo put in a weather engine that actually does please 80% of the users, and it does a good job for what it is. It's us in the remaining 20% or so that want a weather engine designed by a developer who wasn't also concerned with developing every other non-weather related aspect of the sim at the same time they are developing the weather engine. Can't wait. CCs all have no balance at the moment. Bring it on Damian!

I had a very similar experience (and I'm also using the linker). After the the model update failed to turn the button green, I went into settings and did the verify setup option, which fixed it right up.

I had a similar issue once with a different program. It turned out that I was running MSFS as administrator, and the other program was not running as an administrator. I fixed it by not running MSFS as admin, and I've had no problems ever since.

The presence of a padlock icon on hard drives in the Windows 10 File Explorer indicates that the hard drive has been encrypted using BitLocker or Device Encryption programs. Are you (specifically, your username on the computer) the owner of the files?

Were you using Fenix2GSX before Fenix V2 was installed? If so, did you remember to stop using it when you installed Fenix V2? I'm only having one problem with GSX in Fenix v2. It won't start deboarding after the marshaller walks away without restarting Couatl. Everything else works fine. Nobody else seems to be reporting that, so I have been troubleshooting it as a local issue.

Same here. I've probably done 30 flights in a row in her. Landings are so much fun now. The announcements are a great addition, and the GSX integration is the icing on the cake.

Oh lord... please... no. Not the same AI that drew a picture of George Washington that looked like Sulu from Star Trek? They'll be pumping fuel into the trash cans, marshalling the GSX passengers, and loading suitcases into the catering vehicles. They need to unwoke it first.

Thank you, sir. I missed the part about it being the VGDS only.

Deleting previous comment.... The one thing that I have seen screw up GSX is if MSFS runs out of simobjects. There's a limit as to how many it can manage. I'm experiencing something like this right now after landing. Everything works great until after the marshaller walks away. The GSX loaders and baggage carts disappear. The airplane's doors open, but the jetway does not connect, and de-boarding does not start. I restart Couatl, and it works fine. I think it's because I've been setting up GSX while in the air. I've always got a few extra seconds before capturing the localizer, so I usually pick my gate in GSX then. I've had my AIG TC slider set in the 60-70% range, so there's always lots of traffic already spawned around me (and getting thicker all the time as I regularly fire up the AIG installer and let it add new airlines when I'm not using my computer) so I think MSFS isn't loading the GSX objects. I think there are 2 versions of each of the GSX models, a static one and an animated one, (I might be misinterpreting something I read a while back) and I'm thinking MSFS can't load the animated model after the static one gets deleted at boarding because there are too many simobjects. I've been lowering my TC slider a couple of percent after each flight when I see the problem. If I do the same flight during less busy airport hours, it usually works fine. It does not feel like a GSX problem to me. It feels like MSFS is struggling to do something. One last note. I haven't flown any PMDG aircraft in a couple of weeks. Aamir fixed a problem that was apparently somewhat unique to me that was preventing me from being able to successfully complete most flights in the Fenix since last August. She's working fine now (Thanks Aamir!) so I've been making up for lost time. I'll have to do a few 737 flights to see if the issue happens with it. Okay. Two last notes. I am loving the fact that ever since Fenix2GSX got released, automated flows based on the Simbrief plans have become standard.

AIG all the way. I tried FSLTL when it first came out and didn't see anything better than what I already had with AIG. The old interface was fine with me, so so I went right back.

I've had the same problem for a long time, but I have not seen it for the last 2 weeks. I'm not saying that this is a fix, and it may be a complete coincidence, but the problem has not shown up on another Fenix flight after I installed the "2023_TFHT_2 + Firmware [System Requirement: Windows® 10 / 11]PC" package from Thrustmaster's T.16000M support page. I didn't even know this driver existed as I simply plugged in this stick and started using it last summer. The only change that I notice is that the Windows Control panel now opens up a customized Thrustmaster control panel instead of a generic joystick control panel.

I read about that before. IIRC it was because the flight plan had coordinates in the it somewhere instead of a named waypoint.

Well, to be fair... The primary problem with that was that MSFS kept pointing at a different folder than where the users had their sim installed by default, and people weren't noticing that before hitting install so they ended up with 2 installations. That bit me one time. After that, I paid attention to where it was installing and I never had any other issues ever again.

I'm in on day one. Unless they decide to release it during boating season in which case I'll get it as soon as the weather cools. The only question for me is about the drive it'll be going on. I usually buy a new hard drive for a new flight sim, but the 2TB one I bought for MSFS still has 1.1TB of free space. I'm still deciding if I want to make a new top level folder for FS2024, or add another new drive.

Have you read this??? -> https://kb.fenixsim.com/gsx-integration Just want to make sure that you are starting off with everything set up correctly before offering suggestions. I think most of us assume that everyone has seen the information and followed the instructions in it. If you haven't, then we're gonna miss something.

That was a perfectly acceptable answer with a perfectly valid point about giving a business 24 business hours to reply. I get voice mails at 3 or 4 in the morning for work all the time. If they leave one at 4am Saturday, you can bet it won't get answered until Monday morning my time. I think leaving negative comments about it in multiple forums in less than 24 hours is a bit unusual.

I'm wondering if they did something with the missing DX12 textures. I'm on my 2nd flight since the update and I haven't seen any missing textures at all 4 airports in either flight. Might just be a coincidence.

Exception code: 0xc000001d is an "invalid instruction" error. All of us are running the same version of MSFS, so there obviously isn't an actual invalid instruction or we would all be seeing it. Therefore, you most likely have an issue with a supporting routine, like the VC runtime libraries or an OS module that is out of date. If it was me, I would start by making sure that Windows was fully updated, and that all my Visual C libraries are fully up to date. I just noticed the CPU upgrade part. Try updating the chipset drivers using the motherboard manufacturer's update checker.

I think that this is the issue that I was having. The sim keeps running but the airplane controls become unresponsive and it stops following the flight plan. Then everyone dies. It happened to me on nearly every flight where the flight plan had a disconnect. The ORCKA SID out of KLAX, for example. Not sure why everyone else wasn't seeing it, but I usually set an RTA in every flight and Aamir said that he found & fixed a bug with RTA while I was working with him. So if that was the bug referenced, it is fixed. I just flew that flight for the 3rd time today and had no problems at all. Haven't been able to fly it since last August.

I am super happy with this update. Performance is great, and the long standing problem that I've had has been corrected (thanks Aamir!). I've done two LA to Las Vegas flights today, and they've been absolutely perfect. On my last flight, I had a 26L approach with winds of 24007G21. Flew a fairly decent crab to the runway and was able to drop the nose right on the center line. I still need to tweak the rudder a little to help with the taxiing, but other than that I think she flies great now. I'm also pleased that they fixed the panel lighting. On my system, the initial default brightness was over the top bright. Now, full brightness seems correct for daytime flying.

I'm in the can't go wrong with Micro Center camp, I'm fortunate to live about 7 miles from one. They stand by warranties, and if you can afford to add the purchase protection, do it. I done that on some larger items, and it has paid off twice. They've always made good by me.

Yes sir. I just attempted the flight again this morning. I managed to get to Vegas before meeting my maker. Unfortunately, the aircraft froze up after passing BERBN and I crashed on a mountain. Is there any way to tell if a crash log was sent? If so, is there a way for me to help you identify which one is mine (assuming you're getting them from others as well)? I did some additional playing around after the aircraft became non responsive. Throttle levers, gear lever, buttons, and knob animations all work without affecting their associated systems. The flaps themselves do work. I was able to extend and retract them several times. The landing gear does not extend or retract. The click sound does play when buttons are pressed. I have 5 crash logs. They are full of many copies of this entry about Prosim and flight plan: 3/2/2024 8:30:02 AM * :FenixSystem FenixSim A320 2.0.0.378, commit fc8ffd4ce4 build 2.0.0.378 Assembly=v2.0.0.378, OS=Windows 10.0.22631 Intel Core i9-10850K CPU 3.60GHz, 1 CPU, 20 logical and 10 physical cores Process Environment Information: Runtime=.NET Framework 4.8 (4.8.9181.0), X64 RyuJIT GC=Concurrent Workstation Unhandled thread exception. Shutting down. at System.ThrowHelper.ThrowKeyNotFoundException() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at ProSim320.FlightPlan._CUtrUNAfVtZGCFEb4yDvkgTciqr(Nullable`1 , Dictionary`2 , Dictionary`2 , Dictionary`2 ) at ProSim320.FlightPlan._1KLitIqwIYxlJLAeniVvbSlIPtR(DateTime , Nullable`1 , Dictionary`2 , Dictionary`2 , Dictionary`2 ) at _3ydxw6n0wXoCLCSA8guz3jAQIjE._hnuU6ymqtMvk9Bg3yoDka41TkGf._H379Pex92PqwUW5fRvvelA1AjYi() at System.Collections.Generic.List`1.ForEach(Action`1 action) at _3ydxw6n0wXoCLCSA8guz3jAQIjE._cW59b7ckBhEdyzWjz6dQDWSera8._db3w23olJ4ailFSUDmJMs90UJB() at _3ydxw6n0wXoCLCSA8guz3jAQIjE._Llm29YNlYpqdk3dsycAPmHkebWb._ShrWtyN1vPRdr5n2I2KdMuTXdBU() at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() Edit: there are 6 log-system_*.txt files. They are also full of the above entry. Edit 2: @Aamir I submitted a support request a couple of minute ago. Thank you.