Litjan

I made A tutorial for WED - I assume there are many out there ;-) Cheers, Jan

Hmm, this reminds me of the problem others had when using the (now defunct) option of "show vertices". The "show vertices" option was a dubious addition playing with some OpenGL commands that where "not officially supported" at that time by Laminar Research. It worked, though, and looked kinda cool, so we added it. Over the course of many years Laminar changed some inner workings, and now the "show vertices" option makes the 3D cockpit disappear from time to time - this option will be removed in a future update. For now we ask to manually uncheck that option in the preferences menu of the IXEG 737. Let me know if that helps, cheers, Jan

Jean is correct, there are no datarefs for that. I will add it to the list of requests - maybe those can be added in a future update! Cheers, Jan

Very glad to hear that! And please make sure to post here if we can be of any further assistance! Happy landings, Jan

Hi, it doesn´t sound like licensing would be your problem - thats a good thing! I haven´t heard of anyone having a similiar problem - the values on the MCP should be changeable by grabbing (left-click) and then moving the mouse laterally. Make sure you don´t have any third-party stuff interfering - especially notorious are "fly with lua" and python scripts running and influencing datarefs. Also make sure that you don´t have hardware interfering (like programmable consoles or joysticks/throttles). Last but not least make sure you have fuel - the fuel state is saved between sessions, and if you forget to refill the tanks, your engines will spool right down after respawning, even when picking the "ready to fly" state. Let me know how it goes, Jan

Hi Seb, we used a two-class cabin configuration - but that was a flexible arrangement! There was a curtain that would be moved back and forth, according to demand. Business class had the same chairs as economy class (after they finally did away with those pesky seatrows that could be changed from 3 abreast to 2 abreast), but in C configuration the middle seat had to stay empty. Maximum seats available was 123 in all economy config. A typical DOW (dry operating weight) for the 737-300 was 34.000 kgs (give or take a little dependent on catering group). Cheers, Jan

Hi Kinma, I can not speak for the A320 as I don´t have it - but our 737 performs very close to the real aircraft performance parameters. This includes time, distance and fuel to climb. Cheers, Jan

We have those sounds. I just verified it. Cheers, Jan

Hi, you have loaded your X-Plane with plugins to a point where something is bound to give and break. The usual suspects are fly with lua, python interface and ground service plugins. I would start with removing those and see if that helps. If it does not, you have to remove all your plugins and test again - then once you are stable, you can add them back in batches to identify the problematic one. Often users are running an outdated plugin and can fix the problem by updating to the newest version. Good luck, Jan

Thanks for letting us know! Cheers, Jan

You can´t assign those as an axis? Or assign the top position to a different "button" from the bottom position?

We used to have a compatibility problem with Xenviro a while back - I thought there was some sort of update that fixed it? Make sure you run their latest version... Cheers, Jan

Hmm, why don´t you just operate it with the mouse? You only need to operate those fuel cutoff switches when starting or shutting down the engines, so its not really that important to have them on a HOTAS setup. Second - for a realistic start sequence you would need to move them one by one anyway - you could turn them off simultaneously, though. Maybe you can experiment with the command "Mixture lean a bit" and "Mixture rich a bit" - maybe they control all engines at once? Cheers, Jan

Hi Mooze, those switches are controlled by the "mixture" setting, iirc. So assign the buttons to "mixture more rich/lean" or even to "mixture cutoff/full rich". Cheers, Jan

You need to remove all other third-party plugins (addons, scenery, etc.) and then try again. When you see that the crashing stopped, you can add your third-party content again one by one and find out that way which one is conflicting. Cheers, Jan