Litjan

Hi James, I don´t think you can find them on the internet... Before we used computers to calculate those values, we had "Runway Weight Charts" in the cockpit - several charts for every single runway, they were thick folders. The actual TASS depends on the environmental conditions and the runway lenght plus the obstacle situation - and the path the plane would fly after an engine failure. This was calculated by every airline (depending on their engine failure procedures), so there is no standard chart for a runway. We had "sample airports" in there, that assumed no obstacles and just different runway lenghts at different altitudes - those could be helpful to give you a ballpark setting. Mostly the TASS on our aircraft ranged between 35 and 50 degrees - it was rare to do a full power takeoff. When we started using the laptops in the cockpit, the TASS increased by ca. 5C on average, I would say. Just due to better calculation (less conservative). Cheers, Jan

I don´t think so - if you apply electrical AC power to the aircraft (and the radio digits are lit and can be seen) the radios should be working... Check that the correct "side" of the com radio is selected (little white bulb indicates this) - and also make sure that you have the transmit select button for the desired radio selected and also the correct receive button lit as well. Cheers, Jan

Hmm, I don´t have xpilot or Vatsim - but could it be that there is a 8.33kHz option somewhere? Our radios are now working on 8.33kHz spacing, maybe this is the reason? Cheers, Jan

I agree! I have a few "enhancements" planned out already, your "quick alignment" option is actually #147 (added in June). Other things: Add option to synchronize CPT+FO´s altimeter setting, speed bugs, minimum carot Add "wheel chocks" option so plane won´t start rolling if brake pressure depleted (as for hyd brake cylinder precharge check). Make "standby altimeter" circuit breaker operable, so one can stop the vibrator from making the "woodpecker" sound... Cheers, Jan

Hmm, you can see some weird graphics in the display windows of the mode-control-panel (MCP) when using Vulkan. That is not normal. I don´t know if your graphics card is able to run Vulkan? Do the displays work ok if you run in OpenGL?

Hi Beachdog, here are some "stickied" posts that will answer all of your questions, I believe. If there are any still open after reading those, I am right here and will be happy to answer" Cheers, Jan https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/ https://forums.x-pilot.com/forums/topic/17981-version-133-known-bugs-and-workarounds/ https://forums.x-pilot.com/forums/topic/18101-faq-for-new-users/

Hi airfrance, if you could pinpoint the problem somehow to a certain SID or so that would help - I have not seen this myself, but it could be isolated to a certain procedure and/or navdata provider. At any rate, we should never see a lua error, so I would like to pin this down, even if the "speed limit not resetting" will probably be fixed when we rewrite the VNAV functionality. Cheers, Jan

hi canadaclipper, and welcome to (exclusive!) club of 737 Classic pilots! mmerelles has the answer - here is a picture. This switch will only be used if a "symbol generator" (think graphics card) of the FO or the CPT fails. In this case he/she can regain instrumentation (EADI and ESHI) by switching to "both on left" or "both on right". The light is there to remind him, because obviously redundancy is lost in that case. Cheers, Jan

Happy to get it to work. There is no setting on the IXEG to turn off reflections. And it should not cause any devices to flicker - you may have some other plugin or artwork alteration installed that causes this. You can turn off reflections in the X-Plane "display" menu. Cheers, Jan

Hello pmatten, when saving a situation in X-Plane, only certain parameters (called datarefs) are stored in the .sit file (the saved situation). So what you describe is how it works with our aircraft as well - we can not store certain parameters (like whats loaded in the FMS), but the "basic" setup gets stored. You would have to load the aircraft in "ready to fly" scenario, then load the situation. The plane would be at the correct position, altitude and speed. You would then engage the autopilot and autothrottle, raise the gear and then go from there. You can reload a saved .fpl flight plan into the FMS, so that helps a bit with not having to enter the full route again (it does not store the SID, STAR or approach, though). I hope this answers your question, if there is anything else I can help you with, I am right here ;-) Cheers, Jan

I think the system does not model the correct behaviour of the outflow valve when the mode selector is placed in the "check" position. I have entered an issue in the bug tracker for this - thanks for the report! Cheers, Jan

The place bearing/distance waypoints are working. Example: REDGO170/25 or EDDF355/33. You can also make "geographic coordinates" waypoints, like N50W050 or N5333.5W05030.8 The along-track pilot-created-waypoints are not implemented yet. Cheers, Jan

Hi mizra, this may be a good thing to add to the FAQ, thanks for bringing it up! There are two different options for airlines to choose from. The one we portray does not sound the C-chord tone if you approach the altitude in a normal way. It will only sound if you approach it very rapidly (looking like you may not intend to level off). It will also sound (and flash) if you divert from the set altitude by more than 250! (not 300) feet. Cheers, Jan

Hi Antares - now that you mention it...I see it, too. I don´t think it was ever any other way. Hmm, what kind of excuse can I make up? Ah, it is the light from the instruments passing through the red plastic, giving the faint glow to the area! Cheers, Jan

Hi again - we are still at a loss as to why you get this message. The guess is that your computer is lacking a certificate to make the Secure Socket Layer connection - but these certificates should be downloaded automatically without any user intervention, really. Is there some other way you can try to access the internet? Through a WLAN or a hotspot made on a mobile phone?

Hi mickham, unfortunately - not yet. I also run 4k and I consider this to be the optometrist part of my medical before I fly! No, seriously - it is on the list of stuff to fix. Fortunately one only has to "lean in closely" once or twice during a flight to use it. But yes, it is too small on 4k! Cheers, Jan

Now it is getting weird...we haven´t changed anything with regard to that logic in about 5 years! I will check and see what is going on. Cheers Jan Edit: I checked and it is working ok on my end - are you running a "light enhancement" script of some sort? We had some problems with users that did and they had too bright or too dim cockpit lighting as a result...

Hi, I am not an expert on internet connections - it may be a problem with your internet setup (router, firewall) - our experts live in the US and are still asleep - they should be able to give you better advice in a little while. Cheers, Jan

Just run the installer - it will take care of everything! Cheers, Jan

Hi Antares, yes, you are right - some of the limits on that TMA are not working quite like in the real aircraft. The actual thrust set by the plane is correct, but the limit displayed isn´t. I am actually not sure, though - if you select CLB-2 (for example) manually, will it switch back to CLB at the washout altitude or does the selection "stick" since you made it manually? The TMA is a thing that we pilots don´t really pay much attention to, it "just works", so I what is shown there never really struck me as "odd" - I only started worrying about it when modeling this aircraft. We actually have an open ticket for looking at the logic, including the ability to override the automatic switching and selecting a rating manually on the CDU. Cheers and thanks for helping to point out inconsistencies! Jan

We deliberately allow loading of the plane beyond certified weights - the real one COULD be loaded above those weights as well (it is just not allowed). It would be like limiting the wind in X-Plane that you can set to the maximum certified limit...but part of flying in a simulator is to explore the "what if" scenarios ;-) Cheers, Jan

Works for me - sometimes it´s value is off the scale (it starts at 60C), could that be the case?

Yep, I can confirm that as well...that one used to work as well. Both of these buttons depend on a timer function that has given us some trouble recently. This also relates to the "GPU connects to only one bus" bug. We are continuing to investigate the problem together with Ben Russel, it is a deeper computational problem. I believe that going back to the "stable" Gizmo release may fix those (at the expense of the less smooth experience when flying). Cheers, Jan

Hmm, I never noticed that - it has been a long time since that was coded - I have to check some of my videos of the actual aircraft. Just shooting from the hip I would say that it should correspond to the thrust reduction altitude... Thanks for the report, Jan

You are right! And we fixed that...I wonder what happened . Thanks for the report! Jan