Litjan

Awesome shots - good enough to print them out as posters or postcards!

If flying RNAV approaches is what you are after, then that is possible with the current implementation already. As a matter of fact, the real 737-300 I flew was not certified to use VNAV during the approach - we flew them in LNAV and V/S. I think the problem was the single FMS/GPS receiver combo. So you can already fly the GNSS or RNP approaches to the LNAV minimum, but not to the Baro VNAV minimum. Cheers, Jan

Hi Erich, I do not think that flying without that scenery should be the final solution - I would just like to find out what is causing the weird returns. Let me know how that goes, Jan

Hi johnc, there is nothing new to report, unfortunately. Work on 1.3 has not begun, we are working on 1.21 (bug fixes and 11.10 compatibility). Jan

Hello Erich, the weather radar is taking it´s cues both from X-Plane´s weather, and from the terrain mesh - this is to simulate ground returns. You can make the radar beam reflect of mountains, and it will even be shadowed by them (not showing returns behind the mountains). You can also make out big enough water surfaces... that being said, it is possible that erroneous terrain data my throw the radar off. But I think this terrain would also show up visually (like a spike) - and I have no clue why it would have the same shape as the arrival transition to the ILS . You could test if it is related to the norway pro mesh by temporarily disabling that mesh (add the _DISABLED to the relevant line in your scenery_packs.ini) Cheers, Jan

Hmm, that is weird - never seen that before. Does it happen if you don´t use WT3? Does it go away after a few seconds? Thanks for the report, Jan

Nothing suspicious in your logs as far as I can see - I hope that Ben has an idea . Thanks for the update, Jan

Ahh, ok You need to type FREEZE into the window so you agree that your OLD computer (before replacing the hardware) is now not used to run the 737 anymore. This is to avoid that people run the 737 on many computers by saying that they built new hardware. You need to de-register the old hardware (which you are not using anymore). Cheers, Jan

Hi adbera, please rephrase your question, I have no idea what you are asking. Thanks, Jan

The trick here is not to ARM the autothrust. You should still press the TOGA button (to get the correct FD-Modes) but advance thrust levers to the required values manually. Jan

Yes, it is. Even without GPS the FMC position is updated with scanning DME stations, so the ANP is usually in the vicinity of 0.2NM or better. RNAV in the terminal area is requiring 1NM or better. Jan

Hi Fabio, thanks for the report - I will contact you when Ben has time to troubleshoot the problem. I will send you a PM with my email! Grazie, Ciao, Jan

Hi Sebastian, yeah, Laminar is aware of the unique airport - it is the first in the list of airports (called 02 Ranch)... so there is some sort of "reset to airfield" getting triggered, and it may be the "reset to last airfield" with a wrong data field in the "last airfield" involved. This is why I asked for the people that have this bug to check their keyboard bindings - unfortunately there is no answer. This could mean that the bug does not occur anymore, not sure. Cheers, Jan

I just doublechecked - the flap sound can be heard inside the cabin when the flaps drive. It could be a bit louder, maybe. 1.) Position yourself in the cockpit 2.) Open the cockpit door 3.) Move until you are about mid-cabin (so you can hear the electrically driven hydraulic pumps through the cabin floor). 4.) Move the flaps (joystick button or default 1/2 keys) Cheers, Jan

Hi everyone, after 11.10 is done, Ben Supnik will work with me and anyone experiencing this problem to resolve it. I will contact you again on this forum (maybe via private message) when we are ready to start testing. In the meantime I need everyone experiencing this bug to check something for me, please. 1.) Go to the X-Plane settings menu, then go to KEYBOARD. 2.) In the field "Search Commands" insert this text: reset flight to 3.) You should see three commands - are any of those bound to a key for you? 4.) If so, please delete the key assignment, and try to invoke the "teleport" bug again. Let me know how it goes, Jan Example of the screen after typing in the "reset flight to" search phrase:

Hi, alright, we are going to check this out - thanks for the report! Jan

Hi there, it seems to be a common problem - and Laminar is looking for a fix... the workaround is to play in windowed mode :-( Cheers, Jan

I reread the initial post - and sorry, you are right, Morten. The flaps can be heard well when inside the passenger compartment - but not from the cockpit or the outside. I think we do not model the sound of the flaps driving when inside the passenger compartment - maybe something to add in a future update! Cheers, Jan

There is no flap sound audible on the real 737 - the hydraulic (and back-up electric) motor that drives the flaps is housed inside the main wheel well, where its sound is totally droned out by the din of the electrically driven hydraulic pumps. In theory you could turn them off and try to drive the flaps with the electric motor (alternate flaps mode) on the ground, but I never tried this (and stood in the gear well), so I can´t say how loud the motor really is. The default 737-800 models flap sound, but that is totally unrealistic. Jan

Thanks for the nice words!

Until we start modeling failures in a future update - it will be!

Hi Gerard, yeah, I can see how that may confuse someone if only casually reading over the text. I hope that you will not be too disappointed with your purchase, though. I am sure that you could plan the flight with PFPX and then punch the routing into the FMS really quick. The 733 is not a long-haul aircraft, so entering lengthy routings is usually not necessary... Let us know if there is anything else we can help you with! Cheers, Jan

Hi Bill, I like to use it in VR myself - but find that I can´t read the instruments and dials with enough precision - there simply is not enough resolution. The feeling of being in the cockpit is awesome, but to really use it professionally (for example the FMC) is not quite possible, in my opinion. Cheers, Jan

Hi guys, lets not fight - thanks for defending us, Syl20, and gonvise, your concerns are duly noted! We are striving to put out 1.21 soon after 11.10 is finalized. Until then we try to get as much content and fixing into it as possible with the time available to the team-members in charge of their components. Cheers, Jan

Hi guys, sparkie66 is right - pulling out this knob makes the orange speed cursor decouple from the value on the MCP and you can set it manually. This is useful in case the MCP fails in the real plane. For what it is worth, I never had to use this feature in 10 years of flying the real aircraft. The autopilot will continue to reference the MCP speed - it has no way of knowing where the "orange bug" is - it has no eyes . Cheers, Jan