Litjan

Yes, that is correct - when you change the sounds using the IXEG´s preference panel, you are effectively changing the sound level of X-Plane itself. I think that is normal, though, there are no separate sound settings for individual aircraft in X-Plane, to my knowledge. You can´t fly the R22 helicopter and turn down the cockpit sounds and then open the Cessna 172 and expect the cockpit sounds to be at normal level again. The sound settings are global. When a custom aircraft uses it´s own sound engine (like we do with OpenAL), strange things can happen and I would not expect seamless switching between aircraft in one session, it is always good to reboot the simulator when changing between those aircraft. Cheers, Jan

I can´t really say definitely how these things worked on the Classic, it has been 11 years since I flew one... there have been a few changes going to the NG, though - and there are also software differences in FMC versions. I will see if I can find out more, maybe looking at some videos I made back then, but we didn´t do many non-precision approaches.

Oh, and I just checked - the "drum" on the standby altimeter for the "hundreds" of feet does not turn on the real 737, either:

I believe this is all correct. There is no info shown for non-precision approaches on the APPROACH page, only frequency for the ILS, if there is one. Even when not selecting the ILS approach. To delete the flightplan, enter a new ICAO into the ORIG field, even if it is the same one, it will delete the flightplan. If you select a TO derate, that is still considered "full takeoff power" - the engine is just rated at a lower thrust setting, but if you set 100% of that (lower) rating, that is still "full takeoff power" (TO). If you use the TASS function, you get a reduced takeoff power (R-TO).

Ah, I see the 100 drum not rolling...that is probably a bug and will be fixed! Here is a short video I took in my 747-400 just a few days ago: https://www.dropbox.com/scl/fi/sg081mflco67y1zadvarl/Standby-altimeter.mp4?rlkey=sjmttubm79cv793t4i1mhexuo&dl=0

The right one is the standby altimeter, it is inherently inaccurate - on the 747 I fly now it is often "wrong" in excess of 300 feet.

Your bug has been logged and we are going to look into it.

Tom explained it in the recent video he did with Q8pilot - he had to make a decision whether to continue developing the 737 or going down another road in his life to make money. And he needs to eat now, he can´t go hungry for a few months with people on the fence waiting if they want to maybe update or not ("I want to wait until they put in the holds..."). That is why we nudge people to pay the money now.

Hmm, could not look at the video (it is set to private), but theoretically an unlucky combination of plugins, especially highly invasive ones like XPUIPC or FlyWithLua can theoretically cause all sorts of weirdness. Although they normally should not ;-)

There are plans to move to FMOD in the future. I realize that you are not happy with my answer and would have preferred a solution, but I honestly ask you: What do you think this solution should be? Your problem is super isolated, I have not heard of anyone complaining about "distorted sounds" in 8 years of selling our product, feel free to search these forums for similar reports, I believe you will come up empty. Once in a while a user for any software will come up with some hardware/software/OS combination that does not work, and there is nothing you can do. So while I would like to offer you a reasonable solution, I honestly do not know how.

Thanks for the screenshot and the log.txt. Ben is right, the error can be found in the log.txt - this will help in finding and fixing the problem. Greetings to Brazil, I fly to SBGR once in a while, but I would imagine that the classic 737´s hang out in Viracopos? Bom dia, Jan

Huh, I think this must be something obvious...what number are you trying to enter? Into which field? I think a short video would go a long way in clearing this up. Have you watched some of the tutorial videos available?

Hmm, maybe I can talk Tom into adding the function that when you press the button again...the menu closes again. Would that help?

Thanks for the report! I will try to recreate this so we can find and fix it - do you happen to have a screenshot of the error message or the GizmoLog.txt file? Thanks, Jan

That sounds (haha) very plausible. I am not much of a hardware (or software) guru, so I can only guess as to what might be the core of the problem here . Maybe someone reading here with a more profound understanding of the issue can chime in here. Sorry that I could not provide a ready solution, I hope that you will find one! Cheers, Jan

The cabin crew knows nothing about V1, Vr and V2. They also don´t make any announcements, and why would they, there aren´t any passengers sitting in those seats!

I think at this point you may want to open a ticket with X-Aviation support so Cameron and his team can look at it, I have no idea what to advise you (except for the usual "update drivers, remove all third-party scenery, plugins, aircraft,..." I would not trust X-Organizer to disable plugins, you need to physically remove them from the X-Plane folder. Also using SimHeaven Scenery is a very heavy load on systems and has caused problems with RAM exhaustion before.

@Pils probably has the solution. The FMS will limit the range of allowable input, and if you have set the 737 to use metric units (kg´s), trying to put in 100000lbs (100.0) will not work, because the maximum weight in kgs is around 60000 (60.0). I don´t know exactly what limits we instated, but putting in a weight between empty weight and maximum allowable takeoff weight should work as long as you enter it in the units (1000s of lbs or 1000s of kgs) that you selected in the preferences menu. Cheers, Jan

Hi there, happy that you fly our plane a lot! We play our own sounds using OpenAL, and historically this sometimes clashes with other sound sources, especially if the sound hardware is somewhat limited in capacity. Usually this shows when certain sounds don´t play, but distortion could also be possible. To troubleshoot this I would first see if the sound drivers in your operating system are up to date. The second step would be to (temporarily) remove all your add-ons, especially those that also create sounds, like your third-party ATC, fly with lua, terrain radar, etc. I hope this points you in the right direction, Jan

That is a good idea and I think it can be implemented as an option!

https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users-version-15-for-xp12/

I am not sure now, but I THINK that the labels on the gauges always read lbs (even though the amount itself switches to kg´s if you select metric), I know it used to be that way and I am not certain if that has been fixed since (not at my computer right now).

This is a list of issues we recognize on version 1.51. For now it is listing only actual bugs, not feature requests, but we may include those in the future as the list of actual bugs hopefully dwindles down. Tail strobelight missing Wrong coordinates (with negative values) when putting certain navaid IDs into FIX INFO page Automatic setting of plastic speed bugs not working perfectly yet (does not set V2+15 and Vref + 15) Small error in APU fuel feed (feeds from left wing tank instead of left side of fuel manifold) Engine spool up during start looks weird (total time is correct, but initial ramp after fuel on is too fast - XPlane problem)

Have you tried turning off Zink?

Request is noted! Cheers, Jan