Litjan

My hunch is that you are running an unusual hardware/storage configuration or have moved the plane manually to a different folder. Make sure that you are not trying to install it on an external drive or stick (possibly with write protection/encryption), and also make sure that you let the installer work normally so the plane and the plugin will go into their normal folders. If that doesn´t help please file a ticket with tech support at x-aviation, they have a lot more technical knowledge about the inner workings of gizmo and the licensing structure than I do... Hope this helps, Jan

Hmm, that should have solved the problem - did you reboot the computer and tried to run X-Plane in fullscreen mode? Lets see if that helps! Cheers, Jan

Hi Mike, are you running multiple monitors? We heard of some problems when the mouse doesn´t detect being on the very left side of the screen because the "left side" is on a different monitor, or X-Plane is run on windowed but borderless mode... Cheers, Jan

Hi James, everytime X-Plane runs it writes a file called LOG.TXT, which is located in the main X-Plane 11 folder. You can look at it after the crash and also attach it to a post here. It sometimes gives a hint, but often only says "this application crashed". Make sure you read/attach the file right after the simulator crashed - not after you run it again (as it would be overwritten). Also note that a hard crash of X-Plane is something that Laminar Research is very interested in - so it may be worth posting as an official bug report with them. Cheers, Jan

Hi James, glad you are enjoying the aircraft! If you experience a crash after a while that usually hints at some sort of memory problem. I don´t have world traffic myself, but just to troubleshoot I would recommend to bring down your memory footprint, both for RAM and VRAM. This usually involves reducing the scenery (don´t run orthophotos, HD-mesh, etc.) and also to back of the texture resolution. If this helps, you at least know where the problem is... Let us know how it goes! Jan

Hmm, that should not happen - the new flight model will "work" with the IXEG, but the performance numbers will be off (mostly the drag being different). For now I would suggest to use the IXEG with the "new flight model" option UN-checked. I have not checked, but the anti-ice behaviour should not be changed for 11.40. It sounds like you encountered icing, but the anti-ice should counter that. You can always "visualize" the icing status by using the on-screen display in numerical values in X-Plane. (Dataref output on screen). You can see the "icing" build up when encountering icing conditions, and you can also see the effect of the anti-ice removing the icing again. Cheers, Jan

Glad you got it worked out, Graeme! The speedbrake lever is one good example where it hurts to not have force-feedback or powered controls (the thrust levers are the other ones). The real speedbrake lever moves by "itself" (its servo motor) a lot - when it extends after touchdown, auto-retracts in case of a go-around or even auto-extends in case of a rejected take-off (without being armed). In all of these cases, the "virtual speedbrake lever" is out of sync with the physical joystick-axis, requiring some method of re-syncing. In case of the thrust levers we solved this with the "ghost throttles" (since most people have a physical throttle joystick axis), but for the speedbrake we don´t have that. To tell you the truth, I think the speedbrake is best manipulated with either button-clicks (like you did) or with the mouse or moved in the VR cockpit. Unlike the throttles there is little need to "finely manipulate" them. They are pretty much always in one of the 4 defined positions, even when manually flying the real plane. Cheers, Jan

Have you tried the "speedbrake retract one"? I think the X-Plane logic is: ARM - DOWN - FLIGHT DETENT - FULL EXTEND. Whereas on the 737 the "ARM" is between "DOWN" and "FLIGHT DETENT". So simply "retracting" the speedbrake past the "DOWN" position might get you to the ARM. Cheers, Jan

Hi, no, I don´t have the MFG Crosswinds (unfortunately!) - I am using CH Products pedals. Make sure you doublecheck your axis assignments, and also check that the correct profile is assigned to the IXEG 737 in X-Plane. This has confused me before, I set up my hardware to my liking, then switched to another aircraft, and it didn´t work anymore! I later found out that I had assigned a different profile to the latter aircraft... Cheers, Jan

I just tried and the brakes work normal on my end.. Cheers, Jan

I just tried and it works fine on my system. Coincidentially those switches are not "toggle type" but "grab and move" switches - as they have more than three positions. Could this be related? Cheers, Jan

Hi Ian, at the risk of repeating myself - you will NOT use the DH for a Non-Precision (VOR, LOC, NDB,...) or ILS CAT I approach. It is ONLY for CAT II or CAT IIIa approaches. These approaches have a DH of ca. (depending on the elevation around that spot) 100 feet RA and 50 feet (always exactly 50 feet because that is over the runway) RA. For all other approaches you will use the orange "minimum" bug on the altimeter. Set it to the desired minimum (so for 2000 feet set it at the 12 o clock position) - you have to remember the "thousands"... in example the position of the bug would be at the same position for minima of 690feet, 1690 feet, 2690 feet... remember you are flying a Boeing, come cerebral activity is required and expected . Cheers, Jan

Per definitionem you will not hear the takeoff config horn while in the air. Being on the ground is one of the preconditions for it to sound. Confusing this caused the loss of the helios flight 522 https://en.wikipedia.org/wiki/Helios_Airways_Flight_522 The intermittent warning horn in the air means excessive cabin altitude. You need to make sure your pressurization is set up correctly. Jan

Thanks for the report! I will investigate this and file a bug report with Laminar if needed... Cheers, Jan

Hi Dazza, I am not a programmer, but the last line of your log says "G64: 620.776: Memory Allocation Error: Run(timer): xs_sound_engine: not enough memory". I think you run with 16GB of RAM, that should be enough for regular use (no orthophotos). Do you have any other programs run simultaneously that may take up a lot of your memory? Its worth a try trying to reduce the memory footprint - if only to find out if that changes anything. At the same time I would encourage you to post a short description of your problem and the log.txt in the SkyMaxxPro forum where the devs can see it...maybe they can understand better than me what the problem is!? Thanks for getting back to me with those results, Jan

Glad to hear that you made some advances with this - let us know if you find out what was causing this! Cheers, Jan

Hi fastmover, that is weird, indeed! Unfortunately I can´t open your Log.txt for some reason (nothing happens when I click it) - but the standard advice is: 1.) Try to remove all other add-ons and plugins (also ortho or other add-on scenery to rule out memory problems). 2.) If that does not help, report the crash to Laminar Research as well (standard bug report) 3.) If you can identify the plugin causing the conflict, let us know (and the dev of the plugin) of the incompatibility 4.) Try to "repair" your steam installation of X-Plane (I had some steam applications somehow get corrupted, but the repair function worked). Let us know how it goes, Jan

Glad this helped! I think the perfect setting varies for everyone - depending on hardware and personal preference - but I am very happy that Ben, the developer of Gizmo, provided this tool to finetune the experience. Cheers, Jan

You can adjust one cause of this stuttering in the gimzo control menu on the right side of the screen. There is a setting for the "garbage collector" - you can increase it´s setting for a smoother flight, at the cost of framerate. Try to experiment with that, especially if you have enough RAM. Cheers, Jan

Hello Mushtaq, the default navigational database that ships with the IXEG 737 is fairly old and may not contain newer airports. Many users update the database with the current AIRAC cycle database - but you have to buy this from a supplier like Navigraph or Aerosoft. It should include the new airport. Cheers, Jan

Hi Ian, yes, some stuff has changed in the way that planemaker saves the aircraft (lights) - we will have to adapt the 737 to make it compatible with the new planemaker. Cheers, Jan

Thanks, Ian! You guys know that I am always quick to answer any questions in this regard, but here some things in the OP´s post just don´t add up for me to warrant a response - besides this one . Cheers, Jan

We developers typically don´t get involved into these sort of problems. If the machine ID is locked, that means that the person with access to the customer credentials locked it by typing FREEZE after getting asked to pick one of three already authorized (=with IXEG 737 installed on them) machines - typically when trying to install the 737 onto a new computer. The process is fairly straightforward and only comes into play when trying to install the 737 more than 4 times. There is a chance to misunderstand the process, especially if english isn´t your first language. In those cases (accidental locking of intended target machine) only the customer support of X-Aviation can help, which requires to file the problem with them and waiting until the problem can be reviewed and a descicion to the legitimation of the request can be made. This is up to X-Aviation, and given how ingenious some people are when coming up with stories why they need more activations...can result in a denial of the request. Cheers, Jan

Yes, it can perform GNSS approaches to the LNAV minimum - in other words, you have to fly the approach in LNAV but control the vertical path with V/S mode of the autopilot. You can not use the VNAV PTH mode (you can technically, but it is not certified to do so). Cheers, Jan

The alternate nosewheel stering switch was something not all of our 737´s had. I think it was omitted for the newer variants, I have to check my old manuals at home. Since we are modeling a newer variant, we omitted it (saved work, too! :-)) Cheers, Jan