Leaderboard

Hello all. Those who have followed know that the IXEG 737 develoment has been stagnant for a long time while I've worked on my MU-2 project and stabilize it after the release. That stabilization phase is nearly done. XP12 is imminent and I'll be porting the MU2 to XP12 beginning next week...and it should not be terribly long (I hope). After that, the 733 will move back into rotation as the primary focus of development with the port to v12 being the first priority. The IXEG is minimally operable in V12, but that's all we can say. We obviously had to make it baseline flyable in order to test/develop it with all the XP12 changes, which have yet to be addressed. As such, our official position for those who wish to try the V11 IXEG in V12 is "VFR joyriding only". I expect we'll set up a 'volunteer forum' where folks can give feedback as to their V12 observations as its better to have more eyes on this stuff; however, we request that nobody report any shortcomings of the V11 733 in V12. We are keenly aware of a lot of things that have to be changed....so we'll want to wait until we believe we've caught all we can find before other folks chime in; otherwise we'll end up with a massive stack of the same reports. So, certainly keep XP11 around if you wish to fly the IXEG seriously until we get it ported over. I've always kept "old version / new versions" side by side on my computer for these transitions. Long-time XP users know that after a major release to X-Plane, there is an inevitable debug period that goes on for some time, though many other devs have begun already, we're behind. ....but nice to have the process underway.....Below screenshot shows what the cockpit looks like in V12 daytime. -TomK

See pg 182 of the Systems Manual.

TBM isn’t supported on 12.

Please attach a copy of xplane/Log.txt to your next post. Thanks..

O.M.G.. I got it to work! The profile example had different cc values than the .toml, so I edited a few to match the .toml file and lo and behold, X-plane 11 responded! One quirk, the cc set function in loupdeck live appears to send two values, you can't send just one. The first is in a dropdown list, the second is typed by hand. I assume that the first, having labels, are intended to make selection easier because the labels would guide that value, presumably specific categories of actions, while the second selects values within that action. In the case of CMidiCtrl, the commands appear to use only one of these values, so I selected 127 as the second value and x-plane seems to respond fine. It receives both values but ignores the second. Seem right? Next step will be to modify the spreadsheet that shows the B737 commands and select the cc values, types, and commands it for what I want to do with the Loupedeck, which is to control the knobs of the G1000. I have the Honeycomb yoke and throttle quadrants that work fine for most things, including the autopilot, but controlling the G1000 knobs with head tracking on and in real time (e.g. flying IFR with PilotEdge) is too much of a pain, as is changing comm frequencies. I have been dreaming of control knobs I can program and it seems that I can finally get my way!!!

Do you have the text size/rendering scale increased in Windows display settings?

Did you cycle the active database to the Secondary? That is where the Navigraph database is until you manually cycle it.