Leaderboard

Hello, it was the 124thatc plugin that was causing the "Level2-fail licence invalid" problem. After removing this plugin, the 737-300 works normally. Thanks to the Ixeg support team for their help.

@AngelOfAttack I have identified and fixed the reason for the weird pitch during takeoff and landing. It will be fixed in the next version, so dont get too used to the effect ;-)

Hi Jan, I just completed a successful flight (KLAS-KLAX @ FL240) with no pitch problems, using VS to initiate and modify FPM when needed to maintain the proper glide, so that seems to be the key/best way to manage descent....which is basically the same way I do it in XP11. Roger that about FLCH! Thanks, Jim

With regards to your observation of the exterior sounds...our sound engine makes no distinction between interior vs exterior with regards to the software...its simply a "sound" in all cases. All our sounds are effected only through: "play", "stop", "adjust volume", and "adjust pitch", nothing more. When you open the window from the inside view for example, we simply "ramp up the volume" of some sounds...they are already playing. Moving the camera around the interior has the same effect on other sounds...you get closer to the panel, the fan noise "ramps up" too...yet doesn't cause a crash. I think there's something more sinister going on; however, as Cameron mentioned......X-Plane and plugins is real chemistry. It only takes one unique combo to create a reaction and finding the catalyst can be a challenge. We are certainly dealing with that here in my opnion and getting Laminar to help find data points at this stage is a prudent step. Ceratainly we want to add this one to our knowledge base. -TK

It works with buttons and also keyboard assignments (sending the command repeatedly), but before it also worked with switches (sending the command only once). Tbh I only noticed it since I had those assigned to the engine fuel flow switches on my Warthog throttle (simple two way switches).

Is there an update on IXEG 737 for XP12 ready? I am still with the version 1.5 with some issues mentioned in this thread topic. Pat

I made the same mistake

In a long conversation with BBA yesterday we learned that BBA advises to equalize left and right mains BEFORE departure using the L (usually) to AUX pumps, even if the difference is lower that the limit of 400 lbs. This in order to avoid CAS fuel imbalance messages after departure which could be triggered by banking and 'sloshing' in the tanks

Hello Phil, The issue you're experiencing, where X-Plane hangs upon exit when certain plugins or add-ons are active, is a known issue and has been observed not just with IXEG but with other third-party content as well on Mac systems. We believe the root of the problem lies within how X-Plane manages plugins during the shutdown process. We've communicated this with the Laminar Research team, and we're hoping for a resolution in future updates of X-Plane. For the time being, the only workaround is the "Force Quit" that you mentioned, which we understand is not ideal. We're keeping an eye on this situation and hope it can be resolved soon.

@tkyler Wow! Thanks so much for looking into this. You're absolutely right I forgot to mention that the Crz Alt was set in the Perf page. I work in tech and I know the pain of dealing with a bad bug report. Shame shame shame ding ding. Glad you found the fix and that it was ultimately simple. Looking forward to the next update and thanks for the workaround!

I've just tested the fix, a short hop between Porto and Faro, with no issues to point out, besides the already reported bugs. I'm thankful to IXEG team for bringing my favorite 737 to XP12!

..oh noooo ,thanks Jan and Jude ,my mistake ,i turned the upper knob of the HSI That's the problem when you don't fly a plane like that often enough

So....good example of why this port to XP12 is a pain. ..and this is just one of a lot. Went over this for a long while yesterday and just had trouble trying to code around it. Took it directly to Laminar and sure enough, the acceleration ramp between lightoff and idle is simply inaccurate. The acceleration curve shape between lightoff and idle is hard coded and not tweakable via PM. Below is the N2 ramp for the default 738 (which has the same problem). This is Laminar's own data of N2 vs. time (but my overlay comments). You can see the very rapid rise of N2 after lightoff...getting to within 80% of idle in a few seconds. So you may ask, "well why don't you custom code it"...and we do to some extent, but there is a limit. Some parameters, if we decide to override, means its all or nothing. So if we "override the engines" for example..then we have to write the entire engine model for all regimes and that is almost a product in and of itself. Besides, Laminar's model is mature and pretty good...no need to reinvent the wheel.....to me this is simply a "plane-maker design issue" oversight. A 'coefficient' should have been provided (and is what I'm lobbying for) to shape this curve...like a lot of curves in PM can be shaped. The good news is its official, we're filing a ticket to Austin. Also good news (but not perfect) is I've coded a workaround for the next patch to get us through.....because I'm sure it'll be some time before the next update to XP comes out with this fix. The limitation on my patch will be "don't mess with a running engine while the other one is starting". If you do, then the starting engine will exhibit this "rapid rise" behavior somewhat. ...but many folks may not notice it. and these kinds of sweeping modeling changes are all over the place, and have really wreaked havoc with the accuracy of our performance. BUT....we're working on that too now. TK

Yes it will, though we will probably continue to provide the one avail now in parallel. So you'd have two ACF files...where the only difference will be the exterior objects. I expect we'll paint up the same liveries we do now, in high rez form, but of course new ones will have to be created for other liveries. This is probably annoying for "livery consumers" and great news for "livery painters" -Tom

Hi everyone! Thanks for everyone´s support and feedback for our initial launch of the IXEG 737 in XP12. This post will detail the bugs that were reported and confirmed by us. This post will be updated regularly and shall serve as a tool to check if something you observe has already been reported. Activation issues with the DRM that revolve around the "Level 2 check" failing - fixed Wiper switches not working - fixed for next patch Standby airspeed indicator drum not moving - fixed for next patch Bullseye windows on doors 3L and 3R too far outboard - fixed for next patch VRconfig.txt file missing - fixed for next patch Starter not strong enough at high density altitudes - fixed for next patch Engine start process going too fast - improved (total duration matches) but fix in LR´s court Wing illumination light not working - fixed for next patch Visual texture glitch on underside of left wing - fixed for next patch Taxi light a bit too dim MCP backlighting a bit too dim Window heat OFF logic reversed for right side windows - fixed for next patch No turnoff light for right side - fixed for next patch INVALID ENTRY message when trying to manually enter a V1 on TAKEOFF REF page - fixed for next patch Pitch up moment change during liftoff and landing too strong - fixed for next patch Idle fuel flow too low - fixed for next patch No CDU backlit keys - fixed for next patch. FMC / Gizmo crash when executing VNAV calc with only one waypoint in LEGS - fixed for next patch. ECAM gauge needles not lit up at night - fixed for next patch. Added four commands to command the fuel lever to idle/cutoff. For hardware binding to buttons/switches. Linked to default XP commands to connect/disconnect/toggle the GPU. Helpful for VR users. Cockpit door default to pen in the Turn-around mode Cockpit door occludes front galley lighting at night when closed. Fuel Crossfeed annunciator dimmer (less bright) when crossfeed valve open. Was too bright. - fixed for next patch.

I've found it's best to create a fresh profile for the Honeycombs with no binds at all for the Challenger, then gradually add the ones you need. Saves all sorts of gotchas like this.