Alpha Floor

I don't know if this has been reported (haven't seen it), but something I experience often is that VNAV will not engage on departure because the altitude restrictions of the SID are not correct, or just blank with dashes. I don't know if the issue here lies with the AIRAC database, or the IXEG VNAV logic. To fix it I go through LEGS and hit the DELETE key, then right LSK on the "offending" restrictions. Once all are clear, the FMC populates the passing altitudes or flight levels and I can finally engage VNAV.

Offtopic, but oddly enough for some reason there is a huge difference with the JustFlight Piper Turbo Arrow here. It happens when after flying the IXEG 733, I load the PA28R and upon rotation I find out the aircraft is basically uncontrollable because I forgot to uncheck the experimental flight model...

Exactly right, that's what I meant!

What I do is create my own views based on the native X-Plane commands, that way I don't have to re-do the views after updating.

Ah yes! I tried it out when taxiing back to the holding point, and indeed, it kept going off. I just decided to ignore the horn the second time and carry on. If this happened in real life, Jan, a TOWS horn that goes off for no apparent reason. After aborting a take-off and troubleshooting, what would you do? I guess you'd contact your companies maintenance and let them know? Maybe they would ask you to pull and push the corresponding CB to reset the system? Eventually you would just take-off and ignore the horn or would the flight be cancelled? This was out of base on a return flight. I guess the decision to cancel the flight is also dependent on whether you're in or out of the company base.

Hey Jan, thanks for your quick comment! I think it must be something with the Gizmo plugin, I will reboot it between flights as you said! For information: I have the speedbrake assigned to a rotating knob in my Saitek X-52 Pro. The knob was rotated all the way up but as you said, some noise in the signal may be sending a slight non-zero value... And kind thanks for the compliment. If unsure, better to reject the take-off at a low speed than continue with the uncertainty of what is going on... only to find out on rotation...

Gentlemen, Another issue caught today while live streaming. This time it caused me a rejected take-off. TOWS kept going off. The usual suspects are: - Flaps set for take-off - Stab trim in green band - Speedbrakes fully down - Parking brake released But it still kept going off. Anything I am missing here? https://youtu.be/MNCTzcAPfQI?t=14503 Jump to 4:01:43 I had a normal take-off earlier at 1:05:00 with no alarms, for the record.

Hello, Any chance 8.33 radio spacing will be included anytime soon? Really starting to miss it when flying on IVAO as on my last couple of flights it seems like every single frequency is on 8.33 and I can't select them through the radio panel in the aircraft and have to use the x-Ivap software.

That's a good solution. Just let the users decide whether they want the feature or not.

I used it for a bit until I realised that it's best to be consistent with the view system one uses. It's either the custom aircraft views or the native X-Plane views, but no mixing! This is because I have my hat switch set to "glance left/right" on the side buttons, but to "Captain" and "IFR" views on the up/down buttons. I had to remap de Captain and IFR views to native X-Plane views for the transition between the glances and the views to work properly. Lengthy explanation but my conclusion is: get rid of it.

It appears someone had this already and the workaround is to add one pixel to the screen resolution? Is this still the "fix"? http://forums.x-pilot.com/forums/topic/13653-ixeg-menu-not-hiding/?do=findComment&comment=127678 Edit: This didn't do it for me. Setting X-Plane to run in WINDOWED MODE does work, the menus work again. But I don't want to use XP in windowed mode for obvious reasons...

Hello, As of yesterday the IXEG 733 was working fine. Today I connected a new monitor to X-Plane and all works well so far. The only issue I have found is the IXEG 737 Main Menu will NOT show when moving the mouse to the left. Issue 1 - MAIN MENU NOT SHOWING If it matters, my setup is the following: Lenovo laptop on the left, its screen being the "main" screen on Windows Display settings. Second monitor to the right of the laptop; this is the monitor where I run X-Plane 11 in full screen mode. I can slide the mouse to the left from the X-Plane window over to the desktop on the Laptop screen. However the IXEG Main Menu does not popup. Issue 2 - MAIN MENU NOT HIDING I tried to reorder the position of the screens on Windows Display. If I move the second monitor (which is physically right of the laptop), to the left (opposite of where it should be), then the issue reverses. The Main Menu shows but it WILL NOT hide. Also to move the mouse from one screen to another the motion is opposite which is extremely confusing/inconvenient. Any help/ideas? Thanks! Jaime

As we all know and Jan very well explains in the video tutorials, the A/T can be disengaged using two methods: 1) Pushing the "A/T disengage" button located on the side of the throttle levers twice (second time to cancel the alarm). This disengages the A/T and also disarms it. 2) Deselect the active thrust mode, for example, by pushing the SPD button on the MCP if it's lit up. This will "uncouple" the A/T but leave it armed. Technically it is still "engaged" in ARM mode. Some airlines prefer method 2 as the idea is that it leaves the A/T armed in case of a go-around. Other airlines however don't encourage it or outright prohibit this method. It's interesting how different operators view things in different ways. I have looked into Boeing's FCTM to see what they say, and it seems that they don't recommend method 2 either because, quote, "the autothrottle ARM mode is normally not recommended because its function can be confusing". It's interesting that Boeing themselves admit that their own system is confusing, and also that they don't really give an elaborate reasoning as to why it is so confusing. Now, here are some important points of the A/T ARM mode: 1) It provides minimum speed protection in the event the airplane slows to minimum maneuver speed. 2) Gust protection is NOT provided. 3) If the A/T is left in ARM mode during a descent to an MCP altitude (for example, the MDA of a non-precision approach), the system will wake up and engage in SPD mode to level off at the MCP altitude. This can be unintended behaviour if we are flying manually and have gained visual contact with the terrain. Of course one would argue "well why did you not set the MCP altitude to the MAA (missed approach altitude) in the first place?", which is a fair question that can be discussed separately. This is something to bear in mind though. So in my view, I personally prefer to fly either fully manually (both A/P and A/T completely disengaged) or fully automatically (both A/P and A/T engaged and active, not just armed). In case of a go-around if I hit TO/GA the go-around mode will activate in the FMA but I will have to manually advance the thrust levers to set go-around thrust. Fine by me. Your opinions, gentlemen? (and ladies if any, let's be inclusive...)

Is there a list of what will be changed with v1.3 so far? I'm particularly interested in FMC functions (HOLD, custom waypoints etc.) and VNAV logic.

Jan that's a very interesting point. I had a little "accident" regarding an armed A/T in manual flight and will open another thread to discuss it. But I think this is pretty much down to airline SOP as I've been told by other 737 pilots that it's their SOP to "disarm" (not just "deselect") the A/T when in manual flight.

Guten Morgen Jan, Thanks for the tip. I went in Planemaker and increased all RGB values of the external lights from "1, 1, 1" to "8, 8, 8". Now this looks more like it in my opinion: I see your point about people thinking lights should be brighter than they really are. But I've done a few hours of night flying in a Cessna 172, practicing landings WITH and WITHOUT the landing light on, and the difference is abismal. That landing light is very strong! In real life our eyes also adapt much better to night vision than what a simulation through a monitor can replicate. Therefore I'd rather be on the "too bright" side on X-Plane so that I can actually see something. Danke sehr! Jaime

Probably not a bug but didn't know where to ask this. The external lights (landing, taxi, runway turnoff) do not illuminate nearly as much as I would expect them to. The real aircraft lights are very strong but here they are very weak while standing on the ground. During night landing they don't illuminate the runway until you're on it pretty much. Below I have all inboard and outboard landing lights on (taxi and rwy t/o off): How can I change the intensity or beam size of the external lights? Is this an X-Plane 11 thing? I do believe external lights in X-Plane 10 was great.

Just thought you guys might enjoy watching this. I particularly laughed out loud when the guy was surprised that the throttles were moving by themselves!

Hello Tom, If you mind the question, why not have ALL and EVERY IXEG command as a custom command under "IXEG" in the keyboard selection? At the moment it is a mixture of native X-Plane commands and custom IXEG commands. For example the TOGA button is the native X-Plane command. That way you would make your commands "independent" from X-Plane in case they change them with an update or something weird like that. Just an honest question, not a programmer and I'm sure you have good reasons for the way it is.

Hello Tom, excellent work on this! Is it possible to modify the script on my side to have the bugs like this, if so, could you tell me how? Bug 1 - V1 Bug 2 - VR MCP bug - V2 Bug 3 - V2 + 15 Bug 4 and 5 free to use, because I like to set these to Flaps Up and Flaps 5 maneouvring speeds respectively

Amen to that; for now at least, let's see where I can find a paying flying job after Covid, I think I'd even accept an Airbus xD

Hello Jan, I am also paying close attention to the sequence with the sound muted. I can assure you I didn't touch the controls as it is a stick standing on the desk (not a yoke in front of me which I could have pushed with my body). 1:40:14 - TOD reached and speed bug jumps to "infinity" at the same time as VNAV PATH goes to ALT HOLD. Engines start to spool up. 1:40:41 - Aircraft starts to descend with VS going down to 500 fpm. This is where I notice something is not right. 1:40:43 - The first time I hit ALT HLD, speed window opens to M .40, SPD engages in the MCP and MCP SPD announced on FMA. The ALT HLD deselect light does not light up on the MCP though. 1:40:44 - The second time I hit ALT HLD, pitch channel is disengaged, ALT HOLD disappears from FMA and CWS P appears under CMD. This is what one expects to happen when you hit the button with ALT HLD engaged except the deselect light should have been on (light showing the mode can be deselected). 1:40:46 - I hit V/S and from here on behaviour is normal. I'm intrigued now as to what the cause of this could be! Prost!

Thanks for the quick respond Jan! I think I didn't give the AP enough time to develop that descent, stopped it pretty quickly. That initial V/S drop to about -500 fpm was only temporary, would it have been cancelled out if I had let it do its thing? The FMA was still in "ALT HLD" mode so why does it go down?

Hello, I noticed this issue yesterday and I am pretty sure it must be a bug, please correct me if wrong. I am flying with AP engaged, VNAV/LNAV and FL300. The aircraft reaches the TOD but altitude is not changed from FL300. FMC is asking to change it (normal behaviour). But once the aircraft hits the TOD the speed bug goes back to 0 (or infinite, don't know exactly), and the aircraft starts to descend. This caught me by surprise, tried to stop it by pushing ALT HOLD which didn't work. Had to revert to V/S and command a climb. This video shows this behaviour between 1:40:14 and 1:41:15 (please disregard the audio). Aircraft starts to descend at 1:40:40. https://youtu.be/sXsVnTKGW-g?t=6014

The 737-300 is very good for flying "conventional IFR", with sole reference to terrestrial radio aids, more so than other more modern aircraft which will not intercept and track a VOR radial directly. It has two EHSIs, two RMIs and two DMEs. You can navigate without using the FMC at all (although I still use it for the performance calculations when flying "pure" IFR, not the lateral navigation). Tip: You can use the FIX page of the FMC to "draw" radials and arcs. It's very useful when flying procedures if you want to use the MAP mode without a magenta line; particularly the arc function to fly those dreaded DME arcs. Also very useful for drawing holds where you can setup the inbound radial for reference and the abeam to start the timer.