Litjan

If the "program closes" you have a bigger problem - usually it´s a hard crash that is associated to plugins not working correctly. The IXEG standalone is not known to cause and hard crashes of X-plane. You can possibly look in your log.txt after the crash for a reason, but most of the time in a hard crash the log doesn´t show anything. Standard protocol is to remove all plugins, then add them back one by one until you have found the problematic one. Cheers, Jan

I am not even sure what the problem is or how we could fix it from our side. I think it would be up to XPUIPC to ensure compatibility. Cheers, Jan

Hi Jack, the initial complaint was that the rest of the cockpit "disappeared" when looking up or down - not blank screens on the flight displays. Just to clarify, is that what you are seeing as well (look at the video, not only the still picture on the OP´s post)? If you have blank screens on the flight displays and mcdu it is likely that you have a different problem, either your plugin in not running or you have no electrical power to the aircraft which is probably not due to 11.30. Cheers, Jan

Hmm, never heard of that problem before... maybe check if you have any other plugins (x-camera?) running that could interfere with this? Note that there are certain keys associated in X-Plane to camera commands (W, C,...) so hitting any of those MAY affect X-Plane, although it shouldn´t if the input focus is not on the X-Plane window... Cheers, Jan

Thanks for the shot and the nice words! I admit, I feel the same way, even though I don´t use those other aircraft. For me the feeling of familiarity (after having spent 10 years in the real cockpit) is always striking... Cheers, Jan

Try to connect to the internet in a different way - sometimes a router does not work well (this happened to me) and downloading with the computer plugged in directly to the DSL modem worked better. Good luck, Jan

Thanks for the report - I don´t think I saw that with beta 2, but I only tested it very briefly. It MAY be specific to your hardware, but I will doublecheck my installation again (I may not have panned around enough). So far this is the only report about this I heard. But please report it to LR nonetheless! Thank you, Jan

Correct - I am testing our IXEG in 11.30 and make sure that it runs as it used to in 11.26. LR already fixed a few problems (trim not working, some lights not casting light...). There is some misunderstanding about the "new flightmodel" in 11.30. It actually comes in two different instances: 1.) Austin corrected the "ground effect" and "wheel traction" in 11.30 for ALL aircraft. You will always see this effect, no matter if you select the "new experimental" flight model or not. The ground effect fix affects the IXEG as well, flaring behaviour is much better now. It comes at the cost of a small drag increase which most people will not notice. The wheel traction effect does not, since we override the tire friction to achieve realistic crosswind capabilities. 2.) The "new experimental" flight model incorporates Austin´s experiments regarding bodies in oblique airflow. It changes aerodynamic drag for the fuselage, and adopting to that (which we will eventually) requires extensive re-tuning to get correct behaviour and will not start until some time after 11.30 is final. In the meantime it is important to NOT save the .acf file in the new (11.30) planemaker - this would stop the backward compatibility and - for example - would render some lights inoperative in 11.30 and on. Cheers, Jan

Yes, the "draw vortices" will be removed in a future update. It was a "fringe hack" of X-Plane technology that worked for a while. It won´t be needed with the new particles getting introduced with 11.30. Cheers, Jan

I had a similiar problem once - it was due to me connecting to the internet through an old router - once I connected my computer DIRECTLY to the internet, the download worked. Cheers, Jan

Verified and fixed the "low bleed pressure problem" - I think somewhere in the 11.25ish run Austin changed the engine modeling to output less bleed pressure. I did not notice, and since the engine puts out "more than enough" pressure in most phases of the flight, this went unnoticed - until now, thanks Alex! I can now achieve 25% N1 on the receiving engine with the providing engine running at 35% N1 (Sea level, ISA) Cheers, Jan

Hi Alex, I will double-check your reports - I only briefly tested the IXEG in 11.30 (and caught a quite severe bug with the stabilizer trim not working) but didn´t have time to do a real "thorough" testing because I am flying too much in real-life. Sound slider issue is known (it sets the sound of X-Plane as well)... weather radar has always been a bit of a hack, to tell you the truth, and I am surprised that it still works like it does after all these years and X-Plane changes. We will have to see if we can really modernize it sometime. Crossbleed used to work, so that is a surprise - the lights are possibly due to some shader/lighting changes in 11.30 and the oil pressure could be due to Austin changing the engine modeling. On a positive note - I think the "flare" behaviour has been improved (even with the default flight model) - no need to pull back so much anymore to keep the nose from dropping. I will take a look, viele Grüße, Jan

Hi Sabreman, sounds like you found a genuine bug there and I will add this to the tracker - you are right, as soon as you get the gizmo log with the error the "game is over" - the simulation MAY still run after that, but everything may or may not work any longer. The only way to safely continue the flight is to "reboot" gizmo (little arrow symbol), then quickly set up the plane again (you can do this mid-flight with a little practice). Cheers, Jan

Well, something is clearly out of whack with your system or the way you fly the plane - but its hard to tell without seeing a video or so. Here are some ideas: 1.) Runways are possibly icy (check weather) 2.) Asymetric thrust (check that both N1 values are the same). Sometimes (when assigning two throttle axis for left and right engine) one thrust lever gets "stuck" - retard both to idle and then back up to "grab" the stuck one. This is part of the logic to allow "retarding" one lever during an engine failure for people with only one axis for thrust (oh the poverty out there...) 3.) Check nosewheel getting assigned to some axis you are unaware of. You can check in the external view if this is the case. 4.) Check that brakes are both released. Again, one brake could be assigned to some axis you are unaware of. You can display "brake data" with the DATA DISPLAY tab in the X-Plane menu. 5.) Strong crosswind that you are not aware of. Some people put a wind layer at 30.000 feet like 140/80 and then are not aware that this wind will also blow on the ground (unless there is another layer below it). Let me know how it goes, Jan

Double check your fuel load - the plane "saves" the last fuel state - so if you have like 0 fuel on board, you will experience the same thing over and over. To remedy: After the plane "shuts down" just select the "ground services" menu, then fuel your plane. THEN you should be able to either "reload plane" or pick the "ready to fly" scenario again. Let me know if that helps! Cheers, Jan

You can still see my big, freightened eyes in that picture! No worries, I have done worse in real life... Cheers, Jan

Great pictures again! Long flight, eh? Thanks for posting, Jan

Great pictures, thanks for posting - reading along with great interest! Cheers, Jan

Excellent work, Ben!

The problem you describe coincides with the autothrottle system taking over control - either as a normal combined mode reversion (i.e. when ALT ACQ becomes active, the autothrottle will automatically engage MCP SPD mode) or due to a alpha-floor reversion (where the autothrottle goes from ARM to MCP SPD to avoid a stall). Once the autothrottle is active (a green mode displayed), you can not control the throttle with your joystick throttle. Cheers, Jan

I think the solution to your problem is that you are doing something wrong . Look at the instructional videos (or youtube videos of the IXEG out there) to see where you are doing things different from the other thousands of users that don´t have that problem. Happy landings, Jan

Not decided yet. Cheers, Jan

Also note that in the current (11.26) version of X-Plane you need to pull A LOT to avoid the nose dropping when you get very close to the ground. Watch your pitch very closely and be ready to pull ca. 75% of your yoke travel when about to touch down. This is more than in the real plane but a by-product of some new aerodynamic code we got in one of the recent updates. I have been working with Austin on this and he said that he tweaked the code again for 11.30. So we are waiting for that - along with some other aerodynamic changes 11.30 brings. I will revisit the 737´s flightmodel once 11.30 is out and - if warranted - incorporate some tweaks in an update. Cheers, Jan

Hi Jean, for the landings - practice, practice, practice . For your SID departure I would have to see a video of what is happening to really be able to help. It should work the way you describe, but there are a few pitfalls that may prevent VNAV engagement (including failure to fill out the PERF INIT page, etc...) Cheers, Jan

Yes, I remember that we had our "own" TOGA (and some other) commands - but then we consolidated back to X-Plane default commands where possible. People were confused that the "regular" commands didn´t work on the IXEG. So you are right, it is a bit of a mix. I will be here to help if you get stuck again! Cheers, Jan