Litjan

Awesome! Happy landings! Cheers, Jan

Great to hear that, thanks for the feedback! If you can´t see the "ghost throttles" (move hardware throttle rapidly to trigger them), make sure you don´t have that feature turned off by accident in the preferences menu (bump left screen to access it). Cheers, Jan

I am not an expert in computer things, but it seems that the license file could not be written to your harddisk. Maybe you don´t have the administrator rights to save/read files in the folder that the license data is saved?

Hi, after you disconnect the autothrottle you must "regain control" of them by moving your joystick throttle until the "ghost image throttles" match the position of the throttle indicator. At that point you can see the 3D throttles in the cockpit move again. Do this in time before touchdown - normally the pilot should not fly manually with the autothrottle still in control. We say "Manual flight = manual throttle!" If you leave the autopilot engaged during landing, it will automatically enter the "RETARD" mode at 27feet - even while in manual flight. 2 seconds after touchdown it will disarm automatically - but this procedure is only recommended for automatic landings with both autopilots engaged. Cheers, Jan

Hi arenaza, It is hard to determine from your description and your screenshot what is going on. Normally - if the license activation is not sucessfull - you will see the pilots figure when in the cockpit. It is strange however that your activation box keeps popping up, normally it should not do that if the activation was successfull. Maybe the data does not get saved and you have some file access rights problem on your computer. Your picture shows some instruments powered, others are dark (like the navigation display below the artificial horizon). This is very unusual and maybe some other plugin or software interferes. I would try to uninstall both the aircraft and Gizmo (found in the Resources/plugins folder) and then reinstall both. Make sure you remove all other plugins and third-party programs (temporarily) to see if they cause the interference. Once the 737 works, add them back in to see which one causes the problem (unless the activation of the license was the problem). Cheers, Jan

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.