Litjan

The view selection window was removed as it is redundant. You can set up and save views very conveniently with the X-Plane view menu.

Oh!

I personally would not mix SAM and X-Plane 12 anymore than I would mix matter and anti-matter, but everyone can do what they like within the confines of their own dwelling, I guess

To me it looks like the turn radius is calculated wrong - either you are not flying it at the speed that the FMS "thinks" you should fly it, or there is some data missing for the FMS to calculate it correctly (weight, altitude,...) If you use the FMS correctly, the turn radius will be calculated correctly and the plane will fly it accurately. Have you watched the tutorial videos for this aircraft?

Thanks for your help, @Pils

Yes, these should be good enough - the difference between a -500 at 45 tons and a -300 at 45 tons should be negligible. The -400 comes with stronger engines, so the landing distance on contaminated runways (where reverse thrust is taken into account) would be different. I am unable to share my original data for legal reasons, unfortunately.

Hi! You can use the included charts I added in the EFB function with the avitab...or if you don´t want to use the avitab, just look at the .pdf files. The trim you notice is the so-called speed-trim system, it is active with flaps not up and high power settings and is indeed an automated speed stability system. Did you look at my recent videos? I show how to use the avitab in the first one here (fast forward to 17 minutes): https://www.youtube.com/watch?v=ehOXR__e9rU&t=33s Cheers, Jan

Yes, that is on the wanted feature list. It IS kinda flimsy in real life, too, but we will provide a command for that.

https://www.x-aviation.com/catalog/contact_us.php

Tom and I discussed making load and trim a bit more realistic by adding "random" factors like this, but ultimately I convinced him to make the weight be accurate at all time. Two reasons for this: 1.) Normally the variance in weight will sort of "average out". Some people and their handluggage are more heavy, others are more light than the average weight. The actual weight could be off by maybe up to 1000kgs, something the pilot will not notice. 2.) Some people want to TEST the airplane against published data, and not being able to set up weight and balance precisely is a necessity when doing so (because you WILL notice the weight being off by 1000kgs if you do precise measuring). Adding an option to randomize weights will only confuse people, options always carry the risk of confusing people, no matter how crystal clear the option may appear to you and me (as we saw with the option to switch between KGs and LBs)... If you want to "realistically randomize" your weight, get someone living in your house to move the sliders by a small amount when you are not looking and then have them close the window and there you go

Ok, thanks for taking the time to test this, Stephan. Curious... One last idea: Is there a button or lever on your hardware maybe assigned to nav radio tuning?

Thanks for the nice words, Stephan. One has to say in general that Laminar does work fairly well and close with developers. They have a Slack channel for devs and will answer questions and requests there frequently and timely. In some cases the problems that add-ons (and even default X-Plane) encounter are so hard to figure out and affect so few people that it simply is not economically viable to pour a lot of effort into solving the problem. Often it turns out that it is actually the "fault" of the hardware manufacturer of some component, the user misconfigured their operating system or some other freak coincidence and Laminar and everyone in this business to make money have to decide if they want to assign a specialist for possibly weeks of man-hours to try and recreate, get to the bottom of and finally fix a problem that more often than not turns out to be not Laminar´s fault. Laminar´s support is already overwhelmed by requests from users that have a hard time finding the power switch on their computers (for some reason flight simulation is an area that suits geriatric users especially), and everyone has the attitude of "hey, I spent 59 dollars on this, now help me put this here compute together, install Windows, X-Plane, all of my add-ons, and teach me how to fly an A330, too!" In this special case Laminar (rightfully) shrugs their shoulders and says "well, we do not support OpenAL, so this looks like an OpenAL problem so we are out of it". If EVERY user of our 737 had this problem we would probably have a case where we could go and say "hey listen, we have thousands of users that can´t fly this add-on and will hate X-Plane for it, we need some help in figuring out why OpenAL crashes your code". But with only 2 or 3 out of thousands of users, it is more than likely that this is caused by some weird combination of hardware and software that is very infrequent. As cruel as that may sound - unfortunately you and the other guys suffering from this sound problem are too few to really set a big effort in motion to fix this, especially since the obvious way out of this is to convert to FMOD... I personally believe that if you had a computer with different sound hardware, things would work just fine - maybe you can try to install the IXEG on a laptop (you have 3 licenses to install on different machines) and see? Viele Grüße, Jan

Next video is up - turnaround ground operation at Portland.

And I do appreciate your patience in dealing with this problem and your help in finding the cause - even though we were ultimately unable to fix it for you. I did like to start the engine with my window open once in a while in summer, but pretty much had to close the window as the engine sped up to idle because it would get too loud in the cockpit to communicate efficiently ;-) Cheers, Jan

Thanks for the logs!

Well, Laminar is wrong, because the add-on developers themselves have no clue why your X-Plane crashes at 20.2% N1 . There are a myriad of possible reasons in operating systems and hardware, we used the OpenAL engine for our sounds to our best ability but I think there is nothing we can do right now to fix this for you...except ask you to keep your window closed during engine start and maybe wait for us to move to FMOD sounds, it is planned for the future!

Thank you for the logs - despite what Tom said about possibly secretly "fixing" the frequency problem, what speaks against that narrative is that I have NEVER experienced our frequency to be out of bounds or not set to what it used to be set to previously... Looking at your log.txt I see that you load SEVERAL aircraft (A300, MD82, C172, 737-800, SR22,...)but never the IXEG? Here is a snippet from your log: 0:01:10.035 I/FCG: Starting new flight in Aircraft/iniSimulations/iniSimulations A300-600R(F) v2 - Passenger/A300_P_V2.acf at Piste 05 0:01:10.035 D/STM: Transitioning from state state_QuickFlightWizard to state_NormalLoading 0:06:47.236 I/FCG: Starting new flight in Aircraft/Laminar Research/McDonnell Douglas MD-82/MD80.acf at Piste 05 0:06:47.236 D/STM: Transitioning from state state_Normal to state_NormalLoading 0:07:34.371 I/FCG: Starting new flight in Aircraft/Laminar Research/Boeing 737-800/b738.acf at Piste 05 0:07:34.371 D/STM: Transitioning from state state_Normal to state_NormalLoading ...and so on... It would be interesting to see a log.txt where you actually USE the ixeg (and no other aircraft at all). Do this, please: Start Xplane, use the IXEG and set both NAV receivers to 115,00. Then shut down X-Plane. Now load X-Plane again, using the IXEG and see what the NAV receivers are set to?

That is a crazy coincidence! It could be something related to sounds, but we are running our OpenAL sounds, so I can not imagine how that can crash X-Plane?

That is TWO OF US! Don´t ask how many times this happened to me when testing and then I wonder "WTF is wrong now??"

Interesting, thanks for the videos! I have no idea what would initialize these frequencies in a different way. We COULD possibly code a way to store the last frequencies or at least default to valid ones, but as you said it is not a huge problem. I would like to understand why this works differently on different computers, first. If you guys want to, you could post log.txt files from your sessions so I can take a look if there is maybe something you have in common?

Scavenge pump http://www.b737.org.uk/fuel.htm (Scroll down to about midway, the scavenge pump system is explained there) It is possible in the real aircraft, but due to technical limitations it is not possible in our IXEG aircraft. We would like to fix that in the future. To solve the problem you are reporting I would recommend to either fly from the FO´s side (and put the weather radar display on the CPT´s side) or you can DIM the weather radar returns (the brightness knob for the EHSI is actually TWO knobs, one is for wxr/terrain) so that they don´t blot out the navigational info. Cheers, Jan

I would check the fuel level...

I just tested on my machine and between reloads of X-Plane the frequency of NAV1 stays the same and NAV2 decrements by one "click" for both the megahertz and 25 khz knob. The nav radios show default X-Plane nav frequency datarefs, so if you see something else you may want to check other aircraft you fly in between or third-party plugins (flywithlua, etc.) that may fiddle with this. Also make sure that you always select the "engine running" option in the X-Plane flight setup GUI, even if you then use the "cold and dark" initialization in the IXEG menu. The communication VHF radios stay at the same frequency for me.

Ok, I will doublecheck those reports today. In reality the nav frequencies stay at the last frequency, as they are mechanically moved, and they should not be outside the valid band in any case.

I can not reproduce that - on my end the frequency is still the last one I set it to when i shut down X-Plane from the previous session.