Litjan

Hi, I don´t really know what advice to give you - besides the obvious, like turning up the volume, setting up the speficic audio levels in the PREFERENCES menu correctly, making sure your hardware works correctly, Windows and X-Plane and all drivers being up to date, etc. We have heard infrequent reports of some folks with specific audio hardware running out of sound channels, so they can not hear some sounds like the radar altimeter counting down, but we have never had a report like yours... Cheers, Jan

https://forums.x-pilot.com/forums/topic/17981-version-133-known-bugs-and-workarounds/ https://forums.x-pilot.com/forums/topic/16091-ixeg-733-development-status/?page=2&tab=comments#comment-161748 Cheers, Jan

There is no change in rate of progress to report. Cheers, Jan

My reply was strictly limited to the A318 suggestion...but it extends to all other Airbus models as well. As for other aircraft - sure, it could be possible. We will stay with X-Plane (if that was what you were hinting at with the "changing environment"). Going to another simulator is just as out of the question as doing an Airbus model .

No - that is not going to happen...ever.

Again, I am unfortunately not an expert on these things. We use the basic, default datarefs for throttle and other controls (brake, speedbrake, flaps, etc.) interaction, though - so theoretically there should be no problem interfacing with our 737 if it works on the default one. Cheers, Jan

Hi William, I really have no experience with that - but I can offer the advice that some versions of FSUIPC are not compatible with the IXEG - they make the throttle not responsive. But some are... We offer the functionality to assign each thrust lever to a separate throttle axis. Cheers, Jan

Let me expand a bit on this: The VNAV part of our descent calculation is not perfect yet. It can work on simple descents, but will not handle multiple or complex restrictions, nor will it factor in head- or tailwind. This may cause the VNAV calculations/predictions to be erroneous and the pilot needs to monitor the distance/altitude/energy state of the aircraft and revert to selected modes (FL CHG, V/S, manual flight) as warranted. There is a "descent calculator helpsheet" included in the documents for the AviTab free add-on in the airplane to help with calculating the descent profile. Here is some more reading regarding the state of the current version: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users/ and some videos I made recently: https://www.youtube.com/channel/UCJJ1M9epDJiGKmXConLp3Ew

Hi, I have tested our plane in 11.53 and have not noticed any change in the sound effects - nothing is impossible, but the changes to 11.53 should not have any effect on the sounds. One possible solution would be to delete everything in your folder Output/Preferences (this will also delete your joystick/keyboard settings) and run the X-Plane Installer again. Cheers, Jan

Not sure.

Ok, I believe you.

Also make sure that your N2 is above a minimum value... I think like 15% or so. Otherwise there will not be enough airflow and you can get a hotstart. 260kts may not be enough, the non-normal checklist asks for 275kts above FL270 and 300kts below FL270. For some reason X-Plane expects the thrust lever to be at "idle" during an engine start, so if the engine fails to start, make sure the respective thrust lever is in the idle position.

I do not recall such a requirement nor do I find any reference to this in my Operations manual.

It works as expected: Fly with V/S at -1500fpm and then set MCP SPD to 210 kts. At 15.000 feet (descending) the IAS will stabilize at ca. 231 kts IAS. Now pull speedbrake to FLT DET. Airspeed starts reducing (in my test it is 215kts by the time I reach 11.000 feet).

I have tuned the flightmodel and the speedbrake effect to match my personal experience flying this aircraft. If you feel that it should be different, by all means go and change the model in planemaker to your liking.

The reason the approach category will be CAT1 with one engine failed is not the failed autothrust (it isn´t failed) - it is the lack of redundancy in the electrical system - you need two engine driven generators for a CAT2 or CAT3a autoland approach. Hint: It takes more than access to some engineering manual and electrical diagrams to fully understand the capabilities of an aircraft. You will find many things "wrong" with our model, but there are also many many variations in variants and models, even from airline to airline.

I am taking the effort to check back and I am one of the developers.

The problem with your reports is that they are (mostly) not bugs - they are user error, not reproducible or misunderstanding of intended behaviour. This is why it is hard for us to determine if you just don´t know what you are doing or if you try to shed a bad light onto the product by claiming false facts. I applaud that you dabble into the non-normal procedures of this aircraft, we have put a lot of effort into getting the systems right. I am happy to help with understanding the aircraft and the systems, but the bug report forum is for bugs, not for getting help in using the product.

I have just tried, this does not happen on my system.

This is correct, that is why it is called the "preflight" menu. If you want to adjust things like fuel and weight, use the "ground services" menu.

I just tried and it works fine on my end. Make sure that you don´t "fail" with the engine or have a fire in it with the X-Plane failure menu, this will disable the engine and it will not relight.

To expand further on what Cameron wrote: We know and don´t claim that our 737 is perfect. Any model of an aircraft for a flightsimulator offered on PC will have limitations. I am also happy to discuss these things, but if a user writes "windmilling start not working" - all I can write is "windmilling start works", and that is not a productive discussion. I would suggest that you make a list of the things you think that are "bugs" - including steps of what you are doing. You need to "back up" your claims with an exact description of what you are doing (steps, pictures, video), otherwise we can not verify what you are reporting, nor can we find out why things don´t work for you. Our aircraft has been sold for several years to thousands of users, and you are the first one to find out that "PFD and HSI are blank if changing from outside view to inside view"? Don´t you think there is a chance that there is something wrong on your end?

With all due respect: Sure. Whatever. Happy flying.

I am sure it does... Go ahead and display the "Aerodynamic forces" (field 64) in the DATA OUTPUT tab so you can see the little green numbers for "drag". When I fly at 230 kts, the drag is roughly 6100 lbs. When I deploy the spoilers to the "Flight Detent" the drag goes to 7100 lbs, when I go further (not allowed in flight) to the "Full extend detent" the drag rises to 7700lbs. N1 increases accordingly.

Not sure which 737s you flew, but that is not how it worked on the one´s I piloted for 10 years. I doublechecked in my manual, there are only three instances of automatic autothrottle disengagement (except for power failure): * two seconds after landing touchdown * thrust levers separated by more than 10 degrees after FLARE has been annunciated in a dual-channel approach * when a thrust split occurs and flaps are less than 15 degrees and more than half the A/P roll authority of the roll spoiler is used During single engine flight you can readily use the autothrottle. Cheers, Jan