Litjan

Hi and welcome to the IXEG 737 - if you are new to the 737, you will likely run into a few things that could give you a little headache. I make this list here to help you avoid that: When changing or modifying the route in the FMS, the simulator framerate gets really slow. This is your antivirus at work, live-checking all in and out data operations. Create an exception in Windows Defender or other antivirus software for the whole X-Plane folder. I can´t move the throttles. Often this is the newest version of XPUIPC interfering, downgrading to an older version works. It could also be the autothrottle having "control" of the thrust levers, in this case you need to first turn it off, then "re-align" your hardware throttles with the virtual throttles in the cockpit to regain control. Where do I set weight and balance and load the fuel? This is done in the default X-Plane menu for now. I can´t engage the autopilot, or it won´t keep the modes. Often that is the joystick not being centered. Just like in the real plane, moving the joystick(yoke) will revert to CWS pitch and/or roll or even disengage the autopilot (and prevent engagement in the first place). The altitude alerter does not sound the c-chord "acquisition" tone when approaching my selected altitude. This is actually an airline option, the plane we model will only sound a warning if you approach the selected altitude "too fast". Note that our triggering tone when deviating from the set altitude is 250 feet - again a different option from 300 feet. When sitting in the cockpit I see the ugly pilots heads. This means that your product was not activated correctly and Gizmo is not running. Gizmo is the interface script that allows us to code the systems and also handles the DRM (digital rights management). I get tiny microstutters every second or so. This is Gizmo´s lua garbage collector (memory cleaning) function at work. You can try to tweak this in the right-side pop-out menu (GC tab), where you can set how much data garbage collects before it gets cleaned and how thorough the cleaning process works. YMMV. There is a new gizmo version in the works that will greatly improve this... The instruments are off and I don´t have electrical power! There is a problem with the activation of the DRM module, this will display as a "Level 2 DRM check fail" in the log.txt file (to be found in your X-Plane directory), this should get fixed shortly I can not enter or change vertical or speed restrictions into my route! This is limited functionality right now and the plan is to enable that in the future. Why is the weather radar and terrain display not working on the FO side? This is a limitation of the OpenGL implementation of those functions and so far we have not been able to overcome this. We hope to find a way in the future. Where can I find the ZFW (zero fuel weight)? Just enter the GW (gross weight) from the X-Plane weight and balance GUI into the FMS, it will calculate the ZFW for you. Where can I find the trim value to set before takeoff? Use the %MAC value in the X-Plane weight and balance GUI, enter that into the CG field on the FMS takeoff page and set the displayed value in trim units on the elevator trim. How do I map a button to TOGA? Please use the default X-Plane command "Autopilot take-off and go-around" I have found a bug, is this one already known? Please check the "Support" forum, there is a subforum called "Bug reports" and it has a subsection "IXEG confirmed" where I keep a list... https://forums.x-pilot.com/forums/forum/206-ixeg-confirmed/ I can´t seem to set the sound levels in X-Plane, they keep reverting! Make sure you use the sound level sliders on the IXEG preferences menu to set internal, external and airflow sound volumes. I can´t enter a speed or weight into the FMS! The FMS often has an allowable limit for entries to avoid typos, make sure that you are within the allowable range (i.e. no speeds < 110) and that you have selected the right units (imperial or metric) in the preferences menu. Video showing how to set up the most important controls and preferences can be found here: https://youtu.be/ehOXR__e9rU

Hmm...lets see if that is fixed for you with 1.31. Tom changed a lot of manipulator types to make the cockpit more compatible with VR, so maybe that is why we are seeing the difference. Cheers, Jan

Hi Marcin, that is not the way it should be - but probably coded that way back then. The regular "pointers" should always display in all modes. When the VOR/ADF pushbutton is on, these pointers will be replaced by the segmented lines in MAP and CTR MAP modes. When Nils coded this, he probably understood that "when button is pressed, only show these lines in MAP and CTR MAP modes"... Thanks for pointing this out - I will put it on the list. Lets see what happens first - all NDBs getting abolished or us fixing it . Cheers, Jan

I did a bit more research. It seems that we have code running that allows XPUIPC to override our throttles. There are three datarefs: ixeg/733/hardware/xpuipc_overrides ixeg/733/hardware/xpuipc_thro1 ixeg/733/hardware/xpuipc_thro2 ...that are available to do that. I assume that the older version of XPUIPC maybe sets that variable - otherwise you can use dataref editor to toggle it yourself. There are older versions of XPUIPC for download here: http://fsacars.com/downloads/xpuipc/index.html Cheers, Jan

Yes, this is correct - as long as the FCC (flight control computer, either AP and/or FD) is in APP mode, it can not be deselected or other modes engaged. This is also signified by the light in the APP button extinguishing when the mode engages in both LOC and GS. It is a safety feature. The way you did your ILS followed by a circle to land is exactly right. Use VOR/LOC and VS and then you can switch to HDG SEL and ALT HOLD for the break-off. Alternatively you can fly the ILS in APP mode, but will have to disengage the FCC (both AP AND FD) to fly the break-off (you could engage the AP at that point again). A very remote possibility would be to toggle the GA mode and then change to ALT HOLD and HDG SEL out of that - but that is a violent maneuver that you would not really do in the real aircraft. Cheers, Jan

Ah, ok - I misunderstood. Seems to be turning fine here... MASI bug turning.avi

If you have windows...you do. Check your windows defender settings? Another possibility could be using X-Plane from an external drive, accessing the navdatabase can be slow, depending on how it is connected. Cheers, Jan

Hi Alax, for some odd reason our throttles don´t work with the newer version of XPUIPC, but they work with an older one (not sure which version, I don´t use it)... Cheers, Jan

Try downgrading to the latest stable version of Gizmo (18....) and let us know how it goes?

I specifically tried LSK on my system after reading you had problems with it - and it works fine here. So not sure what is going on with that...is anyone else having a problem with it? Cheers, Jan

And this is from your LOG.txt that you sent when everything wasn´t working... 0:00:00.000 G64: Gizmo64 Script Engine v20.05.29.0708 Windows 0:00:00.000 G64: built: May 29 2020, 07:09:33

Unlikely that those are newer. The 20.05.29 is TADA!!! from the 29th of May 2020. The latest installer was cut over a week ago.

Are you sure? As far as I know this is the very latest beta! Which version did you use that is newer than that one?

Glad to hear its working for you!

Nah, that is fine - happy that it works for you - and hopefully we can get the new Gizmo working for everyone, soon! Cheers, Jan

Yeah, that looks odd. Maybe it is JUST about missing that waypoint so it is turning back to make it? Try to put in a speed of 160 kts for VAXOB and see if that helps? Cheers, Jan

Try to follow this standard troubleshooting and reporting protocol - that way we can possible gain a bit more insight and help you. Cheers, Jan

This could be an OpenGL problem, then. Maybe try to disable other plugins (especially fly with lua)... Also not sure what this does? "Application was launched with the following command line options... '/high"

Maybe a lingering dataref after the automatic extension that doesn´t get reset properly (like a combination of replay, etc) - I will try to investigate myself.

Hrm - this is getting weird... If you are running an unusual monitor configuration it could be that your window is now outside the viewable boundaries? Here are the values from the prefs.txt: mainMenuX = 180 mainMenuY = 284 Thats the only thing I can think of. If all else fails, also delete (or move away) the IXEG_user_prefs.txt to test. Cheers, Jan

Maybe also try the very latest version found here.

No idea...never heard of that before. Try to follow standard troubleshooting protocol:

Hi, the log looks like the problem was with BetterPushback...but if you say it crashes with SMP, it may be due to some memory overflow as well (lua). Maybe Ben R. can shed some light on this. Cheers, Jan

Just uploaded the very latest beta from Ben in this post below...maybe go and try to see if that helps? Cheers, Jan

Yeah, PROGRESS page is WIP - sorry that its not working right yet. :-/ The way a "runway" shows up on the route or legs page is determined by the way it was coded. If you depart from runway 09, you don´t want runway 09 to be your first waypoint, as you would otherwise make a full circle, fly back to the threshhold were you just started your takeoff run and then continue on your route . Every SID will end with a route discontinuity until you finish building and connecting your flight plan. A route discontinuity is the FMC´s way of asking you "and where do you want to go after this?" Cheers, Jan