Litjan

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

Thanks for the feedback! I will check the APU sound! The flap lever in the real 737 can be moved smoothly to any position and the flaps will follow suit. So you could set it to "flaps 5.7832" if you wanted to. There is a metal rail underneath with indentions, and if you slide it over this rail (it is springloaded to down) it will "snap" into these detents. It is perfectly possible to set it outside those detents, though. Often a lazy captain would just move the flap lever a tiny fraction aft so that the electric trim runs in the fast setting when getting the plane ready for the night (4 units down stab setting). So I am hesitant to make the detents any bigger (or rather have Tom do it, I have no idea how to), especially since you can easily map a key or button to "flaps up one notch", "flaps down one notch" or even map a button to any specific flap setting you want. Cheers, Jan

Hi Andreas, I am happy with the way it is - in fact I feel that it often is a bit too reluctant to move. But I have only flown the plane for 10 years, so what do I know Cheers, Jan

It is only on our aircraft - we are still working on making the VNAV work better with multiple altitude restrictions. Jan

Yes, thanks for sharing - I will see if I can find out what happens there... Jan

Hi Martheson, thank you very much for the work you did for the previous version! I know it has been a godsend for the VR users of our aircraft - in absence of us providing the necessary files ourselves. I will certainly look for your input and assistance down the road when tweaking the VRconfig.txt for this aircraft, and hopefully we can implement this in the very near future for everyone out of the box. Thanks again to you and Joe (and whoever helped make the previous version VR compatible), Jan

Scroll wheel is fixed for next patch - what about the speed brake? It comes up for me when I pull the lever "up", just like in the real plane? It also extends when I trigger the command "Speedbrake extend one" and it retracts when I trigger "Speedbrake retract one". Is this different for you? Cheers, Jan PS: Sorry for my ridiculous quality control and lame excuse on that!

Hi again, a (very) brief google search netted this: http://www.b737.org.uk/flightcontrols.htm Searching with google again, netted this: https://www.youtube.com/watch?v=AXr0PExNqBA Posted November 2014, I will help you with the math: ca. 5.5 years ago The purpose of this system is much the same as the new MCAS system - it was required for certification, because at high thrust levels you could get into the situation where the plane would slow down - but the nose won´t drop (fast enough), as the lessening elevator forces are not able to compensate the (more or less static) pitch up moment from thrust in underwing mounted engines. So they put in a system that "amplified" the natural pitch stability that you would want in any aircraft (plane gets faster -> nose goes up, plane gets slower -> nose goes down). You are not alone - it confused the heck out of many real pilots (that did not read and understand the book word for word). In the real plane you trim almost all the time - so the effect of this system would only really show when someone has poor piloting technique (prolonged flight with constant yoke input needed). Cheers, Jan

I think this would be a question you need to put to Laminar Research (X-Plane), not here. It looks like your new nav database is getting read by our FMS, but not by Laminar? Cheers, Jan

The question is rather - why did XPUIPC stop working with our plane? We didn´t change anything. Every cheap joystick can interact with our throttles, XPUIPC can´t (anymore). Cheers, Jan

Mmerelles is helping us put this into the plane for everyone. Right now we are clarifying with Laminar Research why the cockpit.obj file we exported from Blender chokes up the VRconfig.txt - there is one extra word in there ("none") that we need to support our new way to define our manipulators, but Laminar´s VR code does not handle it well (as you all found out). So while it is absolutely fine to enjoy what mmerelles is coming up with right now, we will try to solidify this with his help and then include it for everyone by default. Cheers, Jan

Found the bug and fixed it. Thanks again for reporting, Jan