lanmancz

I set the cabin altitude according to the little ruler under the panel (which is there probably for this reason ;-)) - ie. for FL300 the CAB ALT will be 5100. You set the destination elevation into the LAND ALT. CAB ALT is the cabin pressure setting during cruise. btw I think the CAB ALT setting is relevant only in manual mode. I'm not sure about this but I think that in AUTO mode the cabin pressure setting in controlled automatically according to the current altitude.

Hello, do you please think it's worth setting a higher flight model calculation in xplane that the default 2 per frame ? I'm currently running with 3 per frame with about 40 FPS and all is fine. I was just interrested in how much do you run the 737 in xplane with and if you think it's worth it to have it higher or if the plane is "optimized" for the default so I might as well better spend the cpu cycles on eye candy. How much flight models per frame would you recommend for the 737 please ?

Would it please be possible to make these optional if you decide to implement it ? I don't mind at all that some parts don't cast shadows (in fact I didnt even notice:-)) but what I ABSOLUTELY LOVE about the 737 (among other things) is the amazingly smooth FPS I get with this aircraft. I would even go as far to say it's the best performance of any payware aircraft I own (and I own plenty), let alone a complex one like 737. This model has absolutely beatiful FPS and for me high FPS always trumps graphical eyecandy.

My autodetect puts it in "X-Plane 10\Aircraft\X-Aviation\IXEG 737 Classic". Works fine.

Hello, the XPUIPC fix does not solve the problem completely. It seems a bit better but the climb and alt hold is still quite wobbly as the autopilot is unable to maintain steady speed and climb rate. It still tends to climb much too steep, lose too much speed, go into level or even descent, pickup way too much speed and go into another steep climb wobble. Alt hold is a similar story, constantly wobbling up and down around the selected flight level. If I remove the XPUIPC from plugins and start without it it's fine. edit: Also I noticed that the FMC can sometimes create quite weird routes. For example the LSZH BLM2Z arrival to ILS28 with GIPOL28 transition generates a route with 2 very sharp points that "reverse" backwards instead of turning smoothly into the transition from GIPOL. I always have to skip the ZH203 waypoint and go direct to ZH204 from GIPOL as the FMC is unable to make a smooth transition there. I use the default AIRAC as Navigraph causes the Gizmo errors. This problem I mentioned is with default AIRAC (1509). edit2: And also this happened when I just now tried to select different arrival procedure: Gah! And the error completely messed up LNAV and autopilot both of which now refuse to engage.