Litjan

Thanks for the feedback - I will let LR know. Jan

My money is on your joystick being not centered when you try to engage the autopilot. This is modeled according to the real autopilot which can not be engaged when the control wheel is deflected from zero. You can adjust the size of this "zero zone" in the preference settings, if you have a spiky joystick this may be necessary. Let me know how it goes, Jan

Ok, I am seeing the exact same thing...I wonder if this bug has always been there or if it was introduced by a recent update. Fabiosko, you said that you only saw this happening after updating to 11.41? Thanks for any further info, I will file a bug with Laminar Research... Jan

Ok, interesting - I will see if I can reproduce it on my machine! Thanks for the report, Jan

Unless you have a hardware (or gfx driver) problem of some sort it has to be something you added to X-Plane beyond the vanilla install. Your report is the only one regarding this problem - if it was a systemic one we would get more reports on this, I am sure... Cheers, Jan

Turn OFF the option "show vortices" in the IXEG preferences menu. It is not compatible with the latest X-Plane versions anymore. Cheers, Jan

Yes, this is the only time I have heard about this - are you running some sort of lua script or anything else that changes the artwork or light intensities? Let me know how the further troubleshooting works out, but I don´t know what else could be causing this... Cheers, Jan

Hmm, the landing lights should have no effect on cockpit lighting...are you running with HDR on or off? Cheers, Jan

I have never seen those - maybe they are the "cockpit tooltips" that come with X-Plane? Or you have installed something else that is causing that. Maybe someone else knows?

Hi there - I once had a similiar problem when trying to download ActiveSky - it turned out that the problem was the way my computer was hooked up to the internet - I had basically two routers to pass through, and once I hooked my computer directly into the first one (bypassing the second one) it worked ok! Maybe something to try... Cheers, Jan

Mmerelles is right - the PROG page is not working properly - we have not implemented an accurate fuel planning (including wind, enroute fuel burn etc.) so the page is just showing some rough values... The ACARS function will not be implemented, it won´t work without simulating a background "operations" backend that would provide the info that ACARS usually shows. The used fuel button and reset fuel buttons should work - note that you need to press it for a while and I think you need to have the engines shut down or be on the ground or something like that (just like in the real aircraft). It is normally only used during the preflight cockpit preparation, not in flight. Cheers, Jan

Hi Mike, it could be that your gizmo plugin is not working - because something went wrong during the installation, like a wrong path specified or such. The default startup state for the 737 would be with engines running - if it starts up looking "dead" that means that you have not installed it correctly. The DRM is the "digital rights management" query where you have to enter your unlocking credentials to register your computer and unlock the plane. Cheers, Jan

Hi Mike, this is the first time we have encountered this issue without being able to solve it with the above steps :-( I really don´t know what else to suggest, in a "normal" configuration moving the mouse against the left top and right top screen edges should result in the menues popping out. Is the aircraft running normal? DRM registration worked? Are you running any sort of third-party programs that change your mousepointer, Windows desktop, etc? Cheers, Jan

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