Tom Stian

Ok. I could disarm the A/T, but I remember from one (or more) of your videoes that you recommended leaving it in armed. Since you then have the speed protection. I havent tested it, but will speed engage with autopilot off also ?

Just another pilot error then Thanks

Hello When flying with A/T armed only and doing an ILS approach, then the "MCP speed" will activate on GS capture as you can see in my video below

Is the "TAT TEST" switch modeled on this aircraft ? Some info from http://www.b737.org.uk/iceandrain.htm Alpha vanes added Now only one temp probe (many 1/200's had two) TAT TEST button (ie aspirated probe). NB if there is no TAT TEST button you have an unaspirated probe.

SkyMaxPro with the cloud lighting reflection is also not detecting the outboard or inboard landing lights. Iooks like the dataref is used on the runway turnoff lights. Have you tried that ?

If the crash happens when you are entering "Takeoff"-page. The workaround is to the enter a departing runway before you are doing that. Either just the runway or the runway and the SID.

Its a known issue

And check your controller settings maybe.

Hello POL5R (rwy23R) at EGCC have some wierd drawing. Route: EGCC POL1R POL UP17 TIPTA UM82 NIVUN M82 UNBUD UNBU2V ENHD Navigraph Cycle 1605 Should look more like this

I can use APP, but I have to push it twice if I allready have VOR LOC enganged and localizer is not captured. You must capture localizer before G/S. What I normaly do at the approach is to engage VOR LOC, and when I see the localizer is active/moving I press APP, but then it will disengage both VOR LOC and APP if the localizer isent properly captured.

Hello.. Since I dont know if it is a smal bug or my lack of knowledge Ill try here first. When I have engaged VOR LOC for ILS approach. And push APP before localizer is captured, it will not engage APP mode. But disenge VOR LOC and not engage APP mode. Ill have to press APP twice to engage it. Is that normal ? you can see it here.

Yeah. That is the workaround until next hotfix.

No worries. I know you guys will fix it. So its ok But that quickfix fixed the auto brake disarm light when using manual brakes(button) on landing. So thats good.

Hello again. I select auto brake to RTO. All is ok. But when taxing and using brakes (mapped to a button on my joystick) the auto brake is disarming. Every time im using the brakes that happends now with 1.0.4.

If they say that we should keep the default folder for this aircraft, then I will follow that. It may work perfectly if you move it, but it can have something to do with future updates maybe.. Ill stick with what they recommend for sure

Hello Random failures is not simulated by IXEG. So it must have been builtin failures by x-plane that are enabled.

As far as I know you can see if the transpoder is active when the display show ATC 1 or ATC 2, depending what you selected. Screenshot when airborn.

Is see many FSX/P3D users have bought x-plane only because of this aircraft. That is a good decision.

Hi guys Still enjoying this aircraft alot. But trying to report when I see something. The TAT indicator is not showing "0" (zero degree). its going from 2,1,blank,-1,-2 etc, You can also see this in my video. Its from 1.0.0, but it is the same issue at 1.0.3.

You need to use navdata that are designed for the IXEG 733. You can't use navdata from any other addons/products. So you have to get your subscription at Navigraph or Aerosoft. (it is possible to buy only one cycle if you prefer that) https://www.navigraph.com/Subscription.aspx http://en.shop.aerosoft.com/eshop.php?action=article_list&s_volltext=navdatapr About the VNAV issue. I dont think that is because of the stock navdata.

Hello This is just a minor thing. Not even a bug really. But will show you anyway The wind indicator on ND is "flickering" (is that a word?) when the wind speed is very low, just on the limit for being showed or not.

Hello Was planning to fly LSZH to LFLB and got a Gizmo softcrash when I was trying to select runway (ILSZ18) at LFLB. Was not able to export a debug log. Route: VEBIT T50 ROTOS UZ669 VADAR Y58 SALEV SID: VEBI3W STAR: SALE7V Navigraph Cycle 1605 GizmoLog.txt

The reason for IXEG to not prioritize this is that the real b737-300 do not have much wingflex. The wings are pretty stiff. ^^

Since you are tired I did a quick test for you If you select 2000ft on the MCP you will not get that alltitude warning. I guess you get that when your altimeter is at or less then 900ft from the altitude on the MCP. Jan have to answer if this is correct behavior on ground. And if the other problems you got by this is a bug :=)

I see that, but it could be valuable information for IXEG if thats working. Have a good weekend