Litjan

Yeah, I am not a computer expert, but I gather that the amount of free RAM or VRAM is not the issue - it is the amount of "file calls" that the operating system can handle. It´s like having a hospital with 10 doctors in it. You could easily add a few stories to the hospital, it still couldn´t handle more patients. So the idea is to whittle down the number of things your computer is trying to do at the same time. Running plugins, loading scenery, doing other things (background programs, browsers, etc.) I am pretty certain that other customers with identical hardware have run the plane just fine, so the interesting question is: What is unique about your setup that brings out these errors... Cheers, Jan

No, it is likely related to running the beta version of Gizmo. It may work fine on one day, not on the next, or even the next session. Has to do with memory assignment and such... Unless you accidentially set the option to "hide pop up window" it is likely due to running the beta gizmo. Jan

We need to eventually animate the .5 kHz... Cheers, Jan

Maybe some out of memory condition that won´t allow loading additional sounds. Try to load the plane at TXKF and see if you get the same errors there?

Just wanted all VR flyers to know that I have spent pretty much the last 3 days with Mmerelles (Manuel from Patagonia, of all places!) to get the plane VR ready. We (well, mostly him) made a vrconfig.txt file and Tom is right now converting a lot of manipulators that gave us trouble to modern and VR friendly manipulators. I know that I said in the video that we won´t support VR control of the thrust levers in 1.31, but it turns out that we will - there will be a "clickspot" on both levers (towards that center gap) where you can grab and push them simultaneously. The only obstacles remaining to flying in VR that I see now are: poor resolution (depending on your headset it can be hard to read exact values off the instruments) inability to access the IXEG pop-out menus (need to do your flight setup in 2D) Need for rudder pedals (you can steer by grabbing the tiller, but for real crosswind operation you would need hardware rudders) Inability to "trim" easily in VR (although you can grab and rotate the trim wheel very naturally in VR, no pop-out handles yet, though) Necessity to return yoke to neutral to engage autopilot (it won´t snap back to neutral when you let go as it would in a real aircraft). We will have a dedicated thread for VR when 1.31 ships to collect feedback and ideas for improvement. Thanks again for helping, Manuel and also a big thanks to Matheson from VrLabs who also gave us valuable insight and helpful hints in making this happen natively. Cheers, Jan

It looks like you are still running the "MarginalGround traffic" plugin. From your log.txt: Loaded: Custom Scenery/KLAX - Los Angeles International HD/plugins/GroundTraffic/mac.xpl (Marginal.GroundTraffic.KLAX - Los Angeles International HD). Try without that, please? Thanks, Jan

A lot of ADF receivers don´t have a 0.5kHz setting, I think. Usually setting within 0.5kHz is enough to ensure reception (try plus or minus). If you can´t receive that NDB it is probably broken or dismantled and you need to find another approach or divert. Yes, our ADF receiver is old - just like this one: https://www.texasairsalvage.com/main_view.php?editid1=231824 Cheers, Jan

Well, I haven´t in 10 years...but of course we would like to get it working reliably. If the knob gets pushed in, it shouldn´t rotate, but the speed cursor shouldn´t change, either. I will talk to Tom, maybe we can change the "In Out" motion to a simple click, so it isn´t so easy to push when you try to turn... Cheers, Jan

Let us know how that goes! Cheers, Jan

Glad someone noticed! Tom worked over that left one as a "tech demo", so to say - and he will do that to all parts of the cockpit, eventually! Cheers, Jan

Hi there, please read: and Cheers, Jan

Thanks Ian! Version 18 of Gizmo should be included in your installer (choose "stable" instead of "beta"). There are a few versions of Gizmo buried in the developers thread...and it doesn´t help that different versions seem to work for different people...AND also change behaviour from time to time. So the official stance is: Use the stable version (18) that is included in the 1.3 installer. There is no single repository for Gizmo with all legacy, current stable and beta versions, unfortunately. Using google I was also able to find this: https://www.dropbox.com/s/nvgwe6ro40oahb3/Gizmo64.plugin-18.02.12.0240.zip?dl=1 and this: https://www.facebook.com/G64xpl and you may also be able to get advice here: https://forums.x-pilot.com/forums/forum/114-general-discussion/ Cheers, Jan

Hi Oliver, IXEG is fully compatible with fly with lua - it is just when a user runs a script with it that messes with some datarefs, things go south. So it is up to the user to make sure that his fwl scripts don´t interfere with the operation of the IXEG 737. It could be that they are setting the "engage starter" dataref to 1 - so the engines would start turning without doing anything in the 737 cockpit, for example. So if you see something odd happening, this is what you would need to rule influence of 3rd party out: There are many plugins out there that are REALLY awesome (like fly with lua) but unwanted interaction is always possible. Per definitionem no plugin can be considered "standard". Viele Grüße, Jan

Hi Oliver, yeah, Ben stated that the problems with the new betas are due to memory conflicts - so it can be running fine one day, not the other day... YMMV. Regarding the engine spool up - make sure that you have no other plugins interfering, especially fly with lua, etc. Cheers, Jan

Ouch - did this happen when you just crossed a waypoint? I think there is a problem when you have a route modification "open" and then cross a waypoint...

Hi, I ment to make this post for a long time...so here it is : Cheers, Jan

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?