Litjan

Hi Matt, then something may be up with your software setup - OpenAL library or some other Windows/Memory problem. I am not computer savy enough to troubleshoot this from afar, you could attach your log.txt here and maybe someone can glean some information from that? Cheers, Jan

No, that is certainly not normal We are using OpenAL for the sounds and on some systems the available sound channels are taken up which precludes playing "more" sounds. One way to troubleshoot is checking if you run any other plugins that might use or block channels or other resources. To test you can move other resources out of your /Resources folder or move the corresponding folders... or maybe even just temporarily disabling them in the plugin manager might work, although that is not a certain way to avoid the plugin starting up when X-Plane starts and acquiring the channels/resources. Let me know how that goes? Sorry to hear you are having problems, Jan

Update: I have found the first two tutorial videos on an old harddisk drive and will upload them - links in the first post of this thread. I will redo these and the other ones (3 and 4) soon when XP12 is out and we upgraded our 737 to work with it.

You first have to read the posts in the thread that you just posted in. At least the two above your own.

This. You can´t arm either one on the ground in the Classics. I think the minimum altitudes are 50 feet for LNAV and 400 for VNAV.

No idea what you are talking about, sorry. The sounds are in the aircraft folder, under sounds/custom. You can replace them if you don´t like them - I think the APU sounds just like the real APU I had to endure during outside checks for 10 years of my life - they are horrid .

I think that is the only way. In the real airplane the FMS resets after landing roll once you go below a certain ground speed, iirc. We specifically did not implement clearing out the PERF pages because sometimes people just "want to start over" on the flightplan and not fill out all that information again (as it probably hasn´t changed, or can be overwritten if it did). If you want to start with a totally clean slate, just "reboot gizmo" - either in Gizmo pop-out menu or you can even bind a key or button to it. Cheers, Jan

This is really weird, we are using OpenAL sounds which should just run fine on any computer... There have been some problems in the past where users had other applications running that would also use OpenAL and "block" all available sound channels. Some callouts etc. would not play in this case. The only other advice I could give would be to download and install the aircraft again - maybe something got messed up when trying to install it to the correct folders, especially for Steam X-Plane users this is often fraught with trouble since steam likes to install things in weirdly named folders (that is why I personally recommend to buy X-Plane from Laminar Research directly, it will give you much more control and flexibility with regard to installation and add-ons, including the ability to take part in beta trials of new versions much earlier, if so desired). Cheers, Jan

I can not spot anything obvious in your log.txt file. Do you have sounds when using the other planes in X-Plane?

Hmm - I don´t know and can´t confirm it on the real aircraft anymore. Currently our logic says "if you reset the master caution for a certain warning, the logic considers it acknowledged". It may be true what you say and the logic is considering warnings "system wide" and not only "single warning wide". Thanks for your report, we will consider it when updating the 737. Be aware that there is a special case for the center fuel pumps, they will only trigger the master caution if BOTH of them are putting out low pressure. Thanks, Jan

I think you may be suffering some interference from another plugin or add-on. To isolate the problem you would have to remove them (temporarily) and then add them back one by one. Also try to display the DATA OUTPUT values for altitudes on screen (small green numbers) to see what is going on. You screenshots are too small, I can not see what your altimeter is set to, but it looks like your Kollsman window value is different in the left altimeter - they should both be set to the current airport QNH value (or 29.92 and 1013 for standard conditions).

I think it is definitely fun to fly a holding manually - especially if you just use the Rose mode of the VOR or even the RMI ;-) But a good compromise is flying the holding with the aid of the autopilot, using CWS Roll (or Heading) mode and the stopwatch. If you use the FIX page you can draw in the inbound heading to the fix and possibly even the abeam position, this makes flying the hold fairly easy... Cheers, Jan

For some odd reason they got deleted by youtube...and I don´t have them anymore . I plan on redoing them with XP12 when that one comes out - there have been a lot of changes to our model since back then and also the new simulator platform warrants a better looking video, so might as well redo them then! Cheers, Jan

Hi exergon, your list of plugins loaded is filling two pages - I had no idea there were even so many plugins in existence! If your X-Plane installation was a house, people in white suits with breathing gear would show up with three big containers to clear it out One of those plugins is not compatible or hogging OpenAl resources, or something. Run the IXEG on a clean installation of X-Plane without any other plugins at all - check if sound plays. If it doesn´t...I would be very surprised. If it does, start adding in your add-ons one by one to find the conflicting one. Cheers, Jan

First thing that comes to mind: You are deflecting your joystick, or your joystick is sending a jittery signal that makes the autopilot think it is deflected. When the yoke (or joystick) is not at neutral, the autopilot can not engage (just like in the real plane). You can let go of the joystick - and if that still does not work you can increase the "nullzone" in the IXEG preferences menu (bump your mouse against left side of screen to access it). Cheers, Jan

RNAV approaches must not be flown with VNAV on the 737 classic - you should use LNAV and V/S down to the MDA.

Some things to try: Set up your own coroute and save it - see if you can load that? This could hint at a problem with the simbrief file format that gets refused to load. If you can´t even load your own coroutes this could hint at a file access rights problem. Cheers, Jan

Hmm - one thing I could imagine happening here is that you have "failures" enabled and suffer from a blocked static port... or some other plugin interfering with it and writing a wrong value to the dataref of the CPTs altimeter. Or... is it not powered? Maybe send us a screenshot? (also one of your overhead panel)? Cheers, Jan

No, the real scrollwheel can turn infinitely - and thats what we will also have in the next update! Viele Grüße aus Butzbach, Jan

Hello Roberto - this is good progress! Let me know if you find any other gains to remove stutters further! Cheers, Jan

Hi Roberto, Just to rule out some other problem I would: 2.) Remove all other plugins (temporarily move to another folder you make) to rule out any interference 3.) Windows defender is causing a problem when you "modify the route" in the FMS, i.e. every time you enter or change a routing - this accesses the navigational database and Windows Defender is trying to analyze every access...which slows things down. Just enter its settings and exclude the X-Plane folder from "live checking". 4.) You can check your VRAM usage (it has nothing to do with the computational load of your video card) in the X-Plane "graphics setting" - it will say how much VRAM you use under the "texture" slider. 5.) March 2021 version for Gizmo should be fine... I am wary of programs like "Riva Tuner" if a user is not an expert on computers it is likely to turn something on or off that hurts performance in an unexpected way. Also do the "graphical output" thing I told you so we can see if you suffer from generally bad framerates or just temporary stutters.

There could be several reasons for performance problems, I will try to mention them so you can rule them out: 1.) Not using Vulkan 2.) Interference with other plugins 3.) Failure to exclude the X-Plane folder from Microsoft Defender surveillance 4.) Exceeding VRAM (often due to other add-ons with extensive textures, like some airports) 5.) Gizmo garbage collector settings (you already tried that) You can output the framerate as a graph if you select the corresponding checkbox in the DATA OUT tab, then trigger the graphical display with ctrl-g. This will help you judge how "smooth" your framerate really is. Let me know if this helps? Cheers, Jan

Hmm - can we get you to attach your log.txt file here so we can take a look and possibly guess what happens? It could also be some plugin incompatibility - but the log would let us give you a bit of advice which one could be problematic. Thanks, jan

Hi, if you have no sounds at all...something is very wrong. We have had reports from users with weak soundcards that could only play a certain number of channels and some callouts and such were dropped...but no sound? No idea. I don´t want to go through the obvious (do other airplanes make sound, did you enable your speakers, did you actually start the aircraft so that it can make sounds,...), I will venture out on a limb and say that if you have no sounds at all, you have set something up wrong with your computer/X-Plane installation. Cheers, Jan

Older TCAS systems can select IF they want to transmit Altitude information or just the transponder code. I think newer systems will always display altitude information, there really is no reason to NOT transmit it (unless you want to bust an airspace and not get caught!) The ABV and BLW governs the DISPLAY of traffic on your EHSI, it does not change how TCAS reacts to other traffic. If you select BLW you can see traffic far below you (range +2700/ -8000 feet, iirc) - if the switch is in the normal position the altitude range is +/- 2700 feet iirc. only.