Litjan

Known issue, it is on my list. The APU does not get fed from the left tank (this is a common misconception), it is fed from the left side of the fuel manifold. Otherwise balancing could never work as the fuel could not reach the feed line (there is a check-valve to prevent inadvertent transfer of fuel into the tanks). This misconception is what caused us to code it like this at first (I also believed it was fed from the left side tank).

I am not really sure what you are talking about. There was no update.

Just change that in the preferences?

Nah, we don´t believe in streamlining the opinions on our forums or censorship (as long as people stay withing the framework of a civilized discussion that isn´t rated R). Alles Gute, Jan

@Ian I know you well from the "old" times and I value your feedback and opinion! In our defense I can only add that a lot of things were in flux and changing, and therefore we had to take back/amend some things we initially planned and announced. I get it when you say that we initially said X but then later did X+Y... sometimes plans don´t survive contact with reality and have to be amended. It is unfortunate that you did not receive the updated notice of the limited time frame and I can understand if you refrain from purchasing again - although I must say that I will miss your contribution and always great feedback on the forums. Cheers, Jan

Yes, you have to go to the DEFAULT X-PLANE weight and balance menu, scroll all the way down and then you can set a "de-icing holdover time" - the plane will stay free of snow, ice and frost for the time you specify. This is like it works on real aircraft, too. Sometimes the hold-over time runs out while you wait in line to take-off and then you have to go back to the pad and do it all over again

Hello belevezero, we do not have any dedicated custom code for the toe brakes in the IXEG 737. If they work on the other aircraft, they should also work on this one. You have to make sure that the hydraulic pressure for the brakes is available, though. Also make sure that you have not selected a custom control profile for the 737 that might have different assignments for your pedal axis. One surefire thing to check what is going on is to display the DATA OUT numbers for "gear and brakes" to the screen, you can then see the value for brakes go from 0.0 to 1.0 if you have mapped everything correctly. Cheers, Jan

I believe you - it is just the "art controls modified" that is weird. One last thing you could try is to update your GPU drivers to the latest certified...and you have no overclock running, right?

Icing.

I believe that a clean installation should not have this flag in the log.txt - it is used by Laminar Research as a telltale sign that the user has installed or altered something that affects the "inner guts" of the simulator that should never be touched...at his own risk (but probably unknowingly when installing something). --=={This application has crashed!}==-- (Art controls are modified.) Here is the snipped from the settings.txt file that warns users about modifications to it: ################################################################################ # # S T O P ! ! ! # # This is X-Plane 12’s settings file. This is NOT your preferences. You # should not edit this file, delete it, or modify it in any way or X-Plane # may stop working. If you do accidentally touch this file, simply re-run # the updater to get a new clean file. Your preferences are in # Output/preferences. # # This file contains low level tuning for X-Plane's rendering engine; it # is set up by Laminar Research before X-Plane ships. Please close this # file now!! # # # # # # Still here? You're a hacker? The documentation that follows is for # the use of LR's internal dev team. You're welcome to poke at this file # in the privacy of your own home, and if you find a tweak you like, you # can email LR. But please: # # - DO NOT make an add-on that requires this file to be modified. The # format is completely unstable and subject to change without notice. # - DO NOT contact tech support or LR if you change this file and bad # things happen*. If you tweak this, you're on your own. # # * Bad things include: X-Plane crashing, X-Plane hanging, X-Plane failing # to start, rendering artifacts, your whole computer hanging, your # computer catching fire, and highly trained monkeys stealing all of # your underwear. # # You have been warned. # # ################################################################################ # This file maps X-Plane rendering settings (as seen by the user) to art # controls that actually affect the rendering engine. The file contains: # - Basic UI info, e.g. the setting strings and tool tips. # - Tables that map particular setting choices to particular art controls. #

Thank you, same to you!

Well, you have a leg or two up on me regarding IT - I simply fly 747s for a living and have a hard enough time programming the FMS . I will leave the troubleshooting to you in this case - let me know when you have found the reason. Cheers, Jan

Which may just be the problem in this case - hence my request to install it on a different machine with a totally "normal" internet connectivity.

The period in which a special upgrade price was offered has ended. There were many many emails sent out to existing customers to alert them to this fact.

X-Aviation is aware of this issue but can neither reproduce, nor determine what causes it. It is a very isolated issue (3 people affected out of several thousand) and the log provides no hint as to the root cause.

I can not spot anything out of the ordinary in your log - except that you seem to be running very expensive and possibly very specialized server type hardware. I am not enough of a computer expert to know if this would play a role in your problems, but it is something I haven´t seen before (and I must have read about 200 logs or so in the last months). Now it is unlikely that there is something as "too capable" hardware, but maybe something running on your computer (network connection, etc.) is a problem for the validation process that Gizmo is attempting? Do you have another computer you can install the IXEG on? Like a laptop or your brother´s computer or so? Just to try? Cheers, Jan

it would But Laminar is working on a native implementation of a better weather radar and who knows, maybe this will be something we can employ for our aircraft (and bring functionality to both CMs that way).

The weather radar on the current version (for XP12) works the same as the weather radar on the XP11 version. It is not a full physics implementation of a weather radar, but it does simulate ground returns, including being able to spot lakes and rivers (less reflective), it simulates "overscanning" (by reducing returns in cold air where frozen particles provide less reflectivity) and it simulates real scanning and display speed. It has a tilt knob for that and will display the actual X-Plane precipitation. It is - however - only active on the left (CM1) side for technical reason, neither the EGPWS ground symbology NOR the weather radar picture can be displayed on the FO´s (CM2) side. This is a technical limitation and not planned to be solved anytime soon, so if that is of big importance to you, I would hold off on the purchase. Cheers, Jan

Yes, the X-Aviation store will provide you with the XP11 version if you file a support request for that. It may take a few days, sometimes, make sure to not file another support request asking why your first one takes so long - it will just bump you back to the end of the queue.

Your test isnt really conclusive as you move the camera around - this results in varying render load which will in fact alter your framerate wildly. I see that you are using the EDDF custom airport - it is one of the most demanding airports on framerate out there. I would ask you to fly from TXKF and see if the framerate fluctuation is also happening there. In general we do not get any complaints about Gizmo dropping framerate periodically anymore and I also believe that our 737 is one of the "lighter" aircraft out there as impact on FR is concerned. Your hardware is also pretty poor, so I am very surprised that you get "30-40fps in Toliss Airbuses" in the same situation. Set up the 737 at TXKF and see if you can reproduce the problem there. Cheers, Jan

1. Yes 2. Yes 3. Yes (using Avitab) 4. Yes (on CPTs side, only) 5. Yes 6. No 7. For normal operation and normal failures only (not maintenance procedures)

Unfortunately I don´t. I don´t even understand what the problem is - if your whole system freezes up there is possibly some hardware or operating system problem on your side. There is also the possibility that you don´t understand how the autothrottle works - and we never had a "click spot" for the FMC, either. So I am confused.

Entering winds has no effect yet. It should take both 360/36 and 000/36 and this will be fixed when the cruise wind entry becomes relevant for the FMS.

It looks like the cockpit door is open in your picture? If it isn´t, then the camera position should govern it - we have to "fake" the cockpit door blocking the light because the lighting engine in X-plane does not allow solid structures blocking any light besides the sun (and even that not always). So we "fake" the door blocking the light by checking wether the camera is in the cockpit AND the cockpit door is closed. If this is TRUE, we turn off the galley light (even though the switch is actually ON). But if you move the camera out of the cockpit (like in your screenshot), the light goes back on and will illuminate the cockpit a little bit.

Wow, I don´t know anything about those validate files, but I am happy that you managed to figure it out and can now enjoy the 737!!