Litjan

Thats the spirit! Have fun, Jan

Hi Martin, we do not "force" failures on people with renewed licenses - not even if they don´t have a licence at all, the plane will simply not run . And your report about this is the first one we get, so I am inclined to think it is a problem unique to your computer or setup. If all else fails, delete your preference files, maybe there are some corrupted key bindings that trigger failures or so... You can see the status of the icing (and anti-ice) on the "data out" display, search for the correct data to output with the keyword "ice". Happy landings, Jan

I just doublechecked and anti-ice is still working. There is ice accumulation on a "AOA 2" - but this is not used on our aircraft, so it should be inconsequential. Cheers, Jan

Hi Laem, I have not really tried them recently - but the anti-ice used to work and I am not aware of any changes to the icing code or datarefs. But I will check it out just to make sure. You have to use wing-anti-ice and engine-anti-ice in icing conditions. The nose gear being "stuck" could be due to having X-Plane default failures enabled. Cheers, Jan

Your impression is right - the pilot will not feel different CG´s as long as they are within the allowed envelope. Cheers, Jan

Normally (on a real plane) it would - since the bags and pax stay in position and the fuel "shifts" its position. However, we treat the CG as shown in the "ground services" menu as the CG that is currently valid. This is the way that the real pilots would interact with the CG. They don´t see it shifting during loading/fueling - they just get a "final" CG when the loadsheet arrives. Happy landings, Jan

Hi Mareckis, the trim is only influenced by the CG (center of gravity) - not by the zero fuel weight. You can set the center of gravity in the "ground handling" IXEG pop-out menu, or alternatively in the X-Plane weight and balance GUI. The recommended trim setting as read in the FMS will only change if you input the correct CG there - it defaults to 20% MAC (mean aerodynamic chord, a measure for it´s longitudinal position). You can also read the recommended trim setting in the ground handling menu, next to the CG value. Cheers, Jan PS: In the real plane (and also to some extent in X-Plane) the CG will shift during the flight - when people walk back and forth, and also as fuel gets burned, as the location of the fuel tanks does not coincide perfectly with the CG. The effect is pretty mild, though, and the pilot will typically not notice it.

Hi Sylvain, I read you question, but I have no idea how to extract the flightplan from our plane. There are no datarefs or any easy way, and the same holds true for the EADI and ND. I know that Tom is interested in cockpit-building himself, so there is a good chance that this capability will be expanded in the future. Cheers, Jan

Matthias is right - there is a bit of a conflict with X-Plane´s native settings (start with engines running) that can be selected in X-Plane´s GUI and the IXEG provided settings, which can be selected in the left-side pop-out menu. The recommended way is to have your X-Plane setting set to "start with engines running" - and then select your desired startup state in the IXEG pop-out PREFLIGHT menu. Cheers, Jan

You are right - the real plane will use an algorithm to reduce the bank angle at cruise speeds - we have not implemented that yet. Cheers, Jan

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