Litjan

Hmm, I can´t see the video... Yes, the initial "dive" for the path is a known problem. The real plane starts a bit more smooth - our plane is like "falling off a cliff" as the path suddently drops down and it tries to catch up. However - if you use FL CHG in the real aircraft while still targeting a MACH number (high altitude) it will also descend with V/S of 4-5000 fpm sometimes. The oscillation could be due to a bug with our VNAV descent calculation - if VNAV does not perform as wanted, use FL CHG or V/S instead for now. Cheers, Jan

Hi Jürgen, we have had reports of systems getting saturated with "sound calls"... I remember that when we implemented the GPWS sounds and people said that they sometimes couldn´t hear the altitude callouts. We increased the maximum number of "sounds" to play at the same time back then. Maybe something to keep an ear open for ;-) Viele Grüße, Jan

I will have one of my pretty young lady copilots do the voiceover for you guys...

Wasn´t there some sort of script for this already around? Someone?

Just wanted to let you know that this is fixed for the next update. Cheers, Jan

Hi again, I doublechecked the generator oil drive temperature thingy - turns out that Tom already has a pretty good model in place (taking generator load into account). I have increased the temperature a bit - the lower range of the scale was 40C and sometimes the temperature was close to that. And people also confuse the "rise" scale (on top) with the "temperature in" scale. There is a tiny button on top of the avitab - it is just a slim laptop or tablet computer, so it has a power button on top which should turn it on and off. It defaults to on (except for cold+dark startup option). Cheers, Jan

Here is something to try: Open the IXEG_user_prefs.txt file with a text editor (it is in the aircraft main folder). Change this line: disable_mainmenu_popout = 0 to disable_mainmenu_popout = 1 Now start X-Plane and assign a button or keypress to the command: ixeg/733/toggles main menu ON/OFF Now when you run the 737, you should be able to pop that menu with that button/key. Maybe you need to adjust the position of the window (where it pops up), you should be able to do that with changing the mainMenuX and mainMenuY values in that preference file. Cheers, Jan

Hi Jeff, thanks for reporting back that its fixed for you...I still hope to find out why XPUIPC (newer versions) don´t work with our throttled... Cheers, Jan

You may want to start by watching these tutorial videos: Jan

You may cure this by setting the "ready to fly" state in the PREFLIGHT menu, first Thanks for the logs! Jan

Thanks for the report - I will try to duplicate that! Cheers, Jan PS: To continue your flight in such cases, reboot gizmo, then set up your airplane systems again - at least you can continue the flight then...

Well, buy a real computer!! Seriously, I don´t know why the saving for the views would not work for you. Maybe some sort of writing permission thing?

Hi, do you possibly use any other plugins (x-camera, etc.) that may interfere with it? Honestly - the preset view menu is somewhat obsolete, you will probably get much easier and better results with setting up pre-saved views with the default X-Plane view system (set up view, press CTRL-Numpad key to save it...now press the same Numpad key to recall that view). Cheers, Jan

Hi Kieran, I don´t think that using the BETA Gizmo had anything to do with it. Happy landings! Jan

I second what Tom says - we have made big strides and I don´t see any obstacle to providing a good VR experience with our next update. Jan

I just briefly checked on my end and the APU can be heard. I can hear it start (even while engines are running) and when I turn the engines off, I can hear the APU running. Will keep an ear open for that, though! Cheers, Jan

I guess if the navigation database holds the coordinates of the runway ends readily, I would have no objection to making them accessible to enter in the FIX page.

I think it depends on the nav database read and if the runway ends are available. I don´t remember being able to input the runway ends on the 737, but we usually do nowadays on the A320, like EGAA25. IIRC the FIX INFO can only take up to 5 letters, so EGAA25 wouldn´t be possible... Not sure what database or FMC version the Zibo models, I don´t have it. Cheers, Jan

Yeah, once you know why the plane is fighting you (and more importantly how to stop it) it´s not so bad anymore ;-) Cheers, Jan

Yeah, bogus parts, I tell ya! The Cx100 is clearly wrong on the FF gauges. Thanks for pointing it out! Oh, and when you change to imperial units (like lbs, but who would want that??) the KGPH doesn´t change to LBSPH yet. Cheers, Jan

Yeah...that one has been on our list forever. It´s one of those things where it would be easy to just copy the value over from the left one and no one would ever ask again, but Tom wants to do some sort of model that takes in generator load, airflow, etc...so it has been "under construction" for a few years ;-) Cheers, Jan

Yes - the x100 refers to the needle. So if it points at "5" the EGT is 500C. (I know it doesn´t match the readout exactly, they sold us crappy gauges!) I will check the FF gauges, not at my home computer right now. Cheers, Jan

Hi Kieran, thanks for the nice words and the bug report! We are always very keen on getting data to replicate these code crashes - I will try to input your routing when I get home and hope that I also get the crash - then forward it to Tom. There are often STARs or SIDs that pertain to many runways - but sometimes are even laterally dependent on which runway they serve. So for us it is hard to decide which on the different "versions" to load before the user has specified the runway. We certainly endevour to fix that - by possibly holding all display of routing until a runway has been selected - but often users don´t do that until the flight nears the destination...so they get confused about the STAR not being in the LEGS page (because we don´t know WHICH one to show yet). So indeed - the easiest way to do it (and the way I was taught to do it in the real 737) is to always start with the runway (for both SID and STAR) and then work your way "inward". If you don´t know the runway yet, just put in the most likely and then change it enroute when you get closer. Cheers, Jan Edit: PS if that ever happens enroute you can at least "save" your flight somewhat by rebooting gizmo...you will be in the same spot, but of course you would have to set up your systems again as the reboot resets everything to default values

What Tom said. We try to emulate the way the real radar works. This includes ground returns (of different intensity) and even terrain shadowing. So like in the real plane you can see the reflections of the terrain and - with a little skillful tilt managing - even use the wxr radar to find bigger terrain features like lakes, rivers, shorelines, etc. We also simulate "overscanning" (not seeing reflections from the icy part of the CB). Cheers, Jan