Litjan

I think I may be on to something... If you want to make sure this doesn´t happen for now, reboot gizmo during your stop at the gate (pick "turnaround" as a spawn option). Cheers, Jan

You would turn the switch to FLT as part of the "After start flow". If you forget it is not a huge deal, because the pressurization switches to FLT automatically as you lift off. You would just get an uncomfortable "pressure bump" during rotation, as the airstream rams into the (wide open) outflow valve. If the switch is in FLT, the outflow valve is mostly closed (to maintain the slight pressurization), so that this bump is avoided (passenger comfort). You would also notice the cockpit windows "rattle" during take-off run (this is not simulated ;-)). After landing, the Captain calls for the "after landing intems" when the runway is vacated. The FO does the flow, putting this switch to GRD is part of it. Cheers, Jan

Wow, that is a new one... I believe this line in your log hints at the problem: 1:04:12.947 G64: error: Run_MouseClick(xp): OnMouseClick: [string "ixeg.733.gui.lua.ra1"]:65: attempt to index a nil value 1:04:12.971 P/GVA: Updating position time from every 3 to every 2 frames (fps=42) 1:04:12.971 G64: error: Run(gui): OnDraw_Windows: [string "ixeg.733.gui.lua.ra1"]:218: attempt to perform arithmetic on a nil value So I will see what Tom says about this. Thanks for letting us know...and if you can reproduce it, we would be grateful if you told us how. Cheers, Jan

There have been reports of this happening on subsequent takeoffs...I have not been able to narrow this down, but it could be related to speedbrake position. I think that maybe the "speedbrake extended" position is retained in memory and not getting reset. Maybe related to the replay code. I will do some more testing. When it happens, try to pull the speedbrake up and then push it back down all the way. Thanks for the report, and compliments on the professional way you handled the aborted takeoff! Cheers, Jan

Ok, this is the second key on the right side? We haven´t seen any problems with it internally, I will doublecheck. If it happens again, try to tell us which page you were on and what you tried to insert, maybe with a screenshot? That would help us narrow it down. Thanks a lot, Jan

Yeah, this particular bug is still under investigation and not fixed with the latest Gizmo beta. Cheers, Jan

Hmm, some things crop up in your log.txt that may hint at the problem: A:\Xplane/steamapps/common/X-Plane 11/Resources/plugins/xpInsider32.xpl : Error Code = 193 : %1 íå ÿâëÿåòñÿ ïðèëîæåíèåì Win32. Failed: A:\Xplane/steamapps/common/X-Plane 11/Resources/plugins/xpInsider32.xpl. (This file is missing, not a DLL or could not be loaded due to another missing DLL.) Failed: A:\Xplane/steamapps/common/X-Plane 11/Resources/plugins/xpInsider64.xpl. (The plugin refused to start by returning 0 from XPluginStart.) You are also still running Marginals ground traffic plugin for various airports, could you try to remove that (temporarily) just to test? Did you change anything related to your shaders in X-Plane? Run any alterations to the way it "looks"? A lot of people have made tweaks to the art assets (either with a plugin, or manually) that will enhance the way X-Plane looks. Did you try with the "stable gizmo" version? You could also try to go back to OpenGL for rendering or even downgrade to 11.41 again (to check). If all else fails, try to re-install X-Plane (put a copy of your old installation in a safe spot to restore it later), and then just install the IXEG 737 and see if that works. No other idea at this point... Cheers, Jan

No, unfortunately not. This is something that would be nice - but it would require us to save every position of every knob and dial and also all the values (datarefs) that get affected by it. People would also expect the FMS to be in the state they left in, and that would be incredibly complex to do. Cheers, Jan

Yeah, I think the airspeed pointer should be at 0. I will set that up for the next patch. However - when you apply power - it will drive to zero. The dashes on the DME fields signify "no data" - I don´t remember if there were dedicated flags. Cheers, Jan

We used the rotary AC meter switch after engine start to check the generators for nominal output. But that was it. Yes, the FLT/GRD switch was always used - to FLT after engine start and to GRD after leaving the runway. Pretty important, too, for various reasons (like slightly pressurizing the aircraft before takeoff and depressurizing it after landing to enable opening of the doors). Cheers, Jan

Are you sure that you have turned electrical power on? That is the only thing I can think of. If that does not help, please follow the standard troubleshooting protocol outlined here: Cheers, Jan

Yep, this is how we did it. The fuel pump for APU was not really a requirement, although some technicians used to do that. The APU ran fine without it. Engine bleeds were not touched all day. Too dangerous to forget them on subsequent takeoff. Cheers, Jan

I am very happy with the way it handles. Have flown both Cessnas and this aircraft. You can absolutely tweak the flight model using the planemaker, of course! Cheers, Jan

Be aware that using the "start with engines running" in the X-Plane menu has no effect on our aircraft. You need to set up this in the IXEG menu (PREFLIGHT) - pick the option "READY TO FLY". Cheers, Jan

Hi Joni, thanks for keeping us on our toes! 1.) The Nav lights are off on purpose. You would only turn them on at night or in bad visibility, thats why I chose to leave them off. I am open to debate, though ;-) 2.) I can confirm the UV map problem on the upper and lower side of that plate. Thanks! 3.) The reverse thrust is limited in N1 - so the fuel flow is throttled at about 3000kg/h. This is the same in the real aircraft. The "jitter" you see is our code artificially limiting the fuel flow, it is a bit more elegant in the real plane. Although I must say that I rarely looked at the fuel flow when using reverse thrust in the real aircraft. Cheers, Jan

Making the manipulator hotspots bigger in the middle and smaller for each single lever is a good idea. Although I never "accidentially" grabbed the single spot when I tested. It works pretty well, but of course we can improve that in a future version if warranted. The "wiggle" to break the levers loose is actually a remnant of our regular "align axis via ghost-throttle image" procedure, and is somewhat required in case the user has a joystick throttle attached as well. Because otherwise we would say "ok, autothrottle releases control - user takes back control" - and then the thrust levers would snap back to the user´s joy axis position. This happened during takeoff, for example (when THRUST HOLD) is active...with undesired results. So for now we require user interaction "wiggle levers" to tell the system "I am here and ready to take control of thrust!". Cheers, Jan

By the way - any posts in this thread that are off-topic will be deleted without further comment .

Noticed this myself - I guess people work around this by setting up the flight in 2D and then switching...but I agree, having this in 3D would be great!

Hello mcflyslim, Your english is very good, I understand perfectly! I think making a 737-200 will not be in our future, it is just too different from the "Classics", and there is already a very good model out there by FlyJsim (I envy those guys because they did not have to make the FMS ). I like "Chique" for the Classics, and I can very well see ourselves make a -400/-500 DLC at some point in time. But let´s bring this one up to completion, first. Cheers, Jan

Hi everyone, Patch 1.31 is bringing improved VR compatibility to the IXEG 737-300. We have spent a lot of time on this and think it works pretty well - but things can always be improved, so we would like to hear your feedback, discussion and suggestions related to VR and our aircraft. I have made a short movie, explaining and showcasing some of the features we added and how they are ment to be used. Let us know what you think!

The whole concept of lateral and vertical navigation ties into the Progress page. The 4-dimensional position of the aircraft, environment, weight and operational parameters will all affect what is shown on that page. It is not simple, unfortunately. The ground speed is the basis for the progression of the aircraft along the lateral path. This will determine the time estimates along the route to the destination. The ground speed for each segment of the flight is dependent on aircraft speed (operational), aircraft altitude, temperature and wind. It may be changing at several points along the route. The fuel flow for each segment also changes with altitude, airspeed, temperature and weight. Of course this is just the "planning progress". Now, as the plane advances along the route, you have to recalculate (every few seconds), because now the actual airspeed and actual wind have to be factored in (and faded out along the route towards the planned value). So we have plans to implement all of that - we believe in getting a feature right instead of somehow approximating it - wherever possible. Cheers, Jan

Running out of lua memory could be pretty random - happening one flight, not the next one. We haven´t changed any code that would increase load on lua memory, so seeing it now may be total coincidence. Or you have added stuff to your installation recently that increases the load. Other products may not rely on lua in the way the IXEG 737 does, so you wouldn´t see it with them. Try to clear out at least some of your (many many) plugins when running the 737, there are a few that you won´t need when flying it (like extra FMCs, etc) Cheers, Jan

The same goes for this one.

Hi and thanks for the nice words. I am sure you have seen this video, where I answer the question you are asking in detail (it has been up for a few days...)

You have run out of memory, your last line in the log says: G64:1177.568: Memory Allocation Error: Run(timer): xs_sound_engine: not enough memory You need to reduce the number of add-ons you run, especially other plugins that compete for lua memory allocation. Cheers, Jan