Litjan

Same problem as this one - thanks for reporting!

Hi Alex, thanks for checking and reporting back! Glad you found the conflict. Sanfte Landungen, Jan

Hi Andreas, That part of the FMS (like the VNAV) is still mostly "WIP" and the values can be considered a placeholder only for future improvement. We are working on making that work right! Cheers, Jan

No no no, I was just talking mousewheel support in the GUI, not the aircraft, of course . Removed it just the same, thanks!

Hi Jo, I just checked here and the buttons (commands) Flight Controls/Basics/ Landing Gear up and Landing Gear down work just fine. Even when the gear lever is in the OFF position. So maybe somthing else is interfering (FSUIPC, FlyWithLua, etc.)? Cheers, Jan

Thanks, I missed that reference when I edited the original post!

I do not know. I don´t have this problem. Nobody else reported it for the IXEG 737. I would love to help you, but I can´t because I don´t know. Jan

Hi everyone, thanks for the feedback and reports regarding our 1.33 update for the IXEG 737-300. Naturally some things slipped our quality control and some things we simply *** up . Rest assures, we are working on fixing those, for some there are already workarounds. I will post, update and maintain the list here for you - so if you encounter a problem, check it against this list and if it is already known, you can save yourself the time to post (unless you maybe have some further information for us!). Test button for leading edge devices on aft overhead panel does not work Fuel quantity test button does not work Gauge for brake accumulator pressure on modern instrument option always shows 3000psi (steam instrument option works ok). When reconnecting the GPU to the AC buses after they have been powered by the APU or the engine generators, the left bus will not be powered by the GPU anymore. There are several other things not working right or missing (Doors, FMS, Wingflex, etc.), and of course they are still slated for improvement in the future. You can doublecheck your issue against this list: http://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v13/ Cheers, Jan

Sure, following along your investigation with great interest! Please let me know as soon as you have found out what the problem is. All the best, Jan

Hi Rob, the option will not appear if you do not have the avitab plugin in your X-Plane plugin folder. Doublecheck that you have it and that it is enabled. Cheers, Jan

That is correct - the cockpit manipulators take precedence. The workaround for now - as cumbersome as it may be - is to hold down your right mousebutton and move the view until the window is not in front of a cockpit manipulator (or the avitab) anymore. I will talk to Tom about it, maybe there is an easy solution to have the menu have "priority". However: Once the menu appears (this is also true for all "secondary" menus when using the pop-out option), you can drag it wherever you like and it will remember that position. So if you don´t like it in the middle of your screen, just drag it to the bottom left corner, for example. Cheers, Jan

Its on the list. Although I must say that some of the "entitlement" posts I read about the need for a Vrconfig.txt did not exactly push it way up. We are only human, after all. Jan

He is just posting these to show that he is indeed a great simulator pilot. I can not assess his skills enough to confirm or deny this. This in turn proves that the problems he has with the IXEG are not his fault, but because the update 1.3 is genuinely defective. I do not believe so. I have resorted to taking note of his bug reports - and once I can confirm them on my end or get more reports of the same kind - will set about fixing those with the utmost dedication and tireless tenacity. Jan

Confirmed, we will fix those. Doors are coming as well! Thanks for the feedback, Jan

Ha, you found it! There were quite a few 3D objects on this plane with a UV map problem (I don´t understand to this day what a UV map is) - but they would show up in certain lighting conditions...there still are a few, and I am making a list for Tom to fix them. You are seeing one of the flap drives, it is bleeding through... we will fix it soon. Thanks, Jan

Thanks for the confirmation, axmiha! Cheers, Jan

Ha, finally! I have the same problem (it works the first time, but not when I try again) - and Tom has been totally unable to reproduce it. We compared all of our scripts (byte count), I sent him videos, we screenshared...it doesn´t happen on his system. So thanks for confirming I am not crazy! We will certainly keep investigating. Maybe some crazy peripheral interfering (I run a full HOTAS thrustmaster setup)... For now I just pretend the ground power source is bad and is missing a pin or something...I can live with the GEN bus off (transfer bus still works), until I start the APU. AND it only happens after some other source has powered the bus (I call it the bus-virginity-problem)... Cheers, Jan

Wow again - and we are working on adding more datarefs for sure! Cheers, Jan

Thanks for the feedback - afair the TOGA command is the default TOGA command from X-Plane... I will doublecheck. Cheers, Jan

Go to the X-Plane Joystick or Keyboar menu and assign a button to this function (you can use the search box to find it): ixeg/733 toggle main menu ON/OFF Cheers, Jan

I just checked, you are correct - direction is reversed! Good find! Cheers, Jan

Not sure what is causing it - maybe someone from the XPUIPC team can shed some light onto it? Cheers, Jan

Nicely done!

Make sure the autothrottle is not controlling them - you cant move them while it has control over them. Jan

Wow, I think you broke the record for a "loaded" X-Plane. I am not sure if there is a plugin that you don´t have installed? I can´t see anything clearly that points to crashing, but I am sure it is some sort of incompatibility with either a plugin, lua memory exhaustion or memory overflow in general. The only advice I can give is to stop all your other plugins, then run the IXEG and see if it still crashes. It it doesn´t, add the plugins back in batches until you can indentify the one that causes the problem. Viele Grüße, Jan