Leaderboard

I found it works for me to use the classic version with the original Sperry and VOR to VOR navigation. The aircraft will make snake patterns in the sky and needs constant monitoring and fiddling of the Sperry to maintain VOR heading. Furthermore, each variant/livery must be as per loaded saved and activated in advance. ' This plane is full hands on and reflects the mastery of those pilots of old days. I managed twice to ditch it in the sea (due to fuel empty) and once a nose down crash landing.( for some reason my flaps wouldn't extend.) Probably the hydraulic levers. but the wheels did extend. Anyway, it is challenging. You can't do two things at once and that mistake may be fatal. My scroll wheel zooming seems not to work well or delayed. I think this is a XP12 issue that I have noticed with other add on aircraft as well.

Hmm, could not look at the video (it is set to private), but theoretically an unlucky combination of plugins, especially highly invasive ones like XPUIPC or FlyWithLua can theoretically cause all sorts of weirdness. Although they normally should not ;-)

I was able to reproduce the issue yesterday. I couldn't enter a GW nor a ZFW. Somehow, I was to resolve the issue. I can't speak specifically to what I did but it included downloading and installing a fresh copy of the aircraft. Don't know if this'll work for y'all but it might be worth a try. I also disabled XPUIPC -- I use X-Organizer; if you don't use it you'll need to remove the XPUICP folder from plugins. I don't know if this was necessary or not. I had chosen the non-KG option prior to, from the preference menu. Disregard the can't find preferences - I apparently suffered a brain fart when looking for the preferences menu. https://youtu.be/9xoVBRsYAWg Cheers,

Thanks for the screenshot and the log.txt. Ben is right, the error can be found in the log.txt - this will help in finding and fixing the problem. Greetings to Brazil, I fly to SBGR once in a while, but I would imagine that the classic 737´s hang out in Viracopos? Bom dia, Jan

GizmoLog.txt was retired. All info is reported in log.txt

Yup maybe. It will be weird though to call 10,000 ft and have a pop un menu... If not I can always turn on and off the no smoking... A minor change in the SOPS... Haha Cheers! PS thanks for the adjustment in the start engines reaching out 23% ish N2 at high altitude. Hopefully the new revised engine model in 12.0.8 will address the other issues of spooling too fast. Even the APU fires like a rocket.

I can confirm Pils' observations. As a result, when I was designing my own XMidiCtrl profile for this plane, I ended up doing direct dataref manipulation instead of using commands. Which, mind you, works fine (as long as it's the "ACT" dataref I'm using and I configure it to set back to zero when I release the button!), but it's "safer" to use commands because then any input limits can be controlled by you, the dev, rather than me guessing what those constraints should be. As an example, take the DH knobs. I can see from turning the knobs by hand that the limits are -20 and 999. But if I hadn't respected those limits in my XMC profile config, the knob will gladly keep going both down and up (and the EADI will happily show numbers above 999, though as expected it does blank below 0). So what this brings to mind is, when you're doing your re-evaluation, consider adding bespoke commands for everything the user may expect to manipulate in the cockpit. And I mean *everything*, which luckily seems like we're already well on our way for (most devs wouldn't add dedicated commands for the coffee maker buttons, but you did!). On the bright side, I've learned enough about the datarefs the 733 uses that I'm well on my way to being able to write a "persistence" Lua script (mostly so the lighting knobs are where I left them when I load in...), unless of course you'd like to add that functionality as well, which I would appreciate (but this is not relevant to the topic at hand). For reference, the commands I specifically noticed weren't working as expected this evening: All default autopilot commands (like OBS1_up, airspeed_up, etc) would change the relevant value but not animate the MCP knob. Bespoke commands for MCP buttons (CO_toggle, SPEED_mode_toggle, etc) would press in, but not "press out". Bespoke commands for the Heading knob specifically I know didn't animate the controls. I did not test the other knobs except VS, which *does* work. Those are the only ones I tested for sure.

Thanks for the report! I will try to recreate this so we can find and fix it - do you happen to have a screenshot of the error message or the GizmoLog.txt file? Thanks, Jan

I have created an "unofficial" one, with UV maps and AO layers. See if helps, until the official is ready. https://www.dropbox.com/scl/fi/cptz1ejcq2w8m8fbpo7w9/DC3_Paintkit.zip?rlkey=xof406hz2ax2amx066f1h0niz&dl=1

Completely agree - you really have to fly it - no "feet up, tray table out" here! I had to make a deadstick landing one time - forgot to monitor fuel levels, left engine died, sudden yaw to the right which got may attention, then the right died too, and by the time I'd checked the tanks it was too low to restart them, but managed to get the gear and flaps down and landed in a field!

Working to finish an quick update for a few things, and I will do that for the next one. Updates will in come very fast. If understand correctly, you would like something like up/down commands to move the lever through the 4 positions, cut off - auto lean - auto reach - emergency?