Litjan

Poweer is right. Aileron trim is RARELY used on the 737 - as it limits your available aileron travel (which you may need in strong crosswinds). So if the plane constantly banks, you need to find out why (and rectify that). Small banking tendencies can be countered with the rudder (even though that results in a bit of uncoordination). The correct trim procedure, however, is like this: Fly straight and level, make sure N1´s and wingtank fuel levels are the same. Maintain wings level with aileron, stop any turning tendency (yaw) with rudder-trim. Then use aileron trim if needed. For more than one unit (see top of yoke), make a maintenance entry. Jan

If you guys can give me a step-by-step guide (or even better a movie!) on how to recreate those problems I will do so and create an entry into our bug-log to get that fixed! Cheers, Jan

Ok, I have added an entry into our dev-log to take a look at it. No promises, but at least it won´t be forgotten this way. Cheers, Jan

Hi, we tried to keep the radar and terrain display accurate in colour and capability. The radar is masked by terrain, can be reflected by terrain, and can be subject to "overscanning" (icy tops) and underscanning. Update frequency is similiar to the real one, but we don´t model attenuation. The terrain return is a poll of X-Plane´s dsf elevation map, colour coded as shown above. Cheers, Jan

Not sure if this was done deliberately or with regard to some footage I provided. Could be a hommage to the "vintage" area that this great plane was built in . I don´t think it has any consequences, but I will add it to our bug-base just the same to take a look. Cheers, Jan

Hi Ian, thanks for the feedback! I will see what we can do about the clickspots. The yoke movement times have been subject to much debate - the real yoke can´t be moved nearly as fast as the joystick can, it simply takes time to move the flightcontrols, even for the hydraulics, and the yoke is always "in sync" with the flight control surfaces. This is great for the pilot, as it reduces "overcontrolling", unlike on the Airbus´ joystick (I deliberately avoid the word "flightstick", here), where you have no idea how far the ailerons really are when flying in gusty conditions. Really annoying and dangerous. I feel that the yoke response time in our model is pretty much accurate - I have done lots of "flight-control-checks" in the real one (every flight), where you move the yoke through the full travel, and it definitely takes a second or more to move it from one full stop to the other. It also needs to be said that X-Plane´s turbulence model is way too excessive and I NEVER fly with real weather on for this reason. The speed and frequency of wind speed and direction shift is just plain unreal and way overdone, and I have been working on a profound portfolio of videos and documentation of real-world cockpit footage to present my case to Austin. He likes "fun and exciting", so its always a battle to "tone something down". We will see. Cheers, Jan

Hi everyone, I am back from vacation and will go through all of the reports that came in over the last two weeks (I did manage to answer a few on my smartphone) in the next few days, catalogue and reply as warranted. There will be a next patch, of course, and fortunately it does not seem like we have any "must fix immediately" candidates in there. Our number one priority is the "gizmo soft crash", of course - we still have a few of those lingering, but I don´t have any good and solid reports, unfortunately. If you want your gizmo-crash to be fixed for sure, please include surefire steps (a video works best!) on how to reproduce it. The usual "there I was, flying the XYZ STAR into ABC airport..." unfortunately rarely helps, as even minute differences in performing the flight may or may not produce different results. Thanks for everyone´s patience, Jan

Dang, I am convinced now! And I also see that we must reasses our bugfixing and feature priority. As of right now, FMS, VNAV and cabin 3d are on hold until we get this most pressing omission squared away... Tom, please delete that VNAV overhaul and get cranking on the winglets! . Honestly... real classics don't have winglets.... Cheers, Jan

That is the recommended (and most realistic) way. Jan

That is no surprise, nozhong was done on VNAV. Jan

Hi, your request is noted and I will add it to our list for the next update! Thanks for your hard work on this plugin! Cheers, Jan

On vacation right now, but try this: Set a scattered layer and warch it from a valley airport in a default aircraft... I could see the clouds THROUGH the mountaintops on my machine. Jan

30C is the minimum TASS iirc.

Feels like it, sometimes . "Dont fly angry!"

Thanks! Jan

This is due to you levelling off in descent while in VNAV PTH. The VNAV descent is not fully working correctly yet... so if you see this revert to MCP SPD or some other mode except for VNAV. Jan

Who else likes the great movie "groundhog day"?

Dont set Navaids for possible engine failure, its bad luck . Seriously, normal procedures ask for setting navaids for departure and subsequent navaids, you would only set the ILS if you really needed it (LFML for example). In the real world the GS would not show on "other" side of ILS, but you can just cancel the warning by pushing on the light. Jan

You are right, the correct sequence of pages to show when INIT REF is pressed has been on my list for a good year, but its hard to get devtime for that . Still many more pressing issues to fix first. Thanks for the report, Jan

Fahrenheit is a derelict measurement of temperature used by backward people, only. Get with the program, its kilograms, meters, seconds and errr Kelvin, erm, Celsius... . seriously, I dont think they use Fahrenheit in serious aviation even in the U.S... Jan

Also check if you have gusty crosswinds set. Jan

Not yet. You can visualize those points by using the FIX page. Cheers, Jan

Hmm, I will take a look at this when I get home from vacation in two weeks! Thanks for the report, Jan

You can see these clouds through the terrain (mountain tops), too. So I think its a Laminar bug. Jan

We are still investigating this, but there may have been a last second **** up on our side just before 1.2 went out . We had them working at one point in time just before the update and its not quite clear if we missed a setting or if Laminar changed something. At any rate, we definitely plan to bring reflections back. Jan