mmerelles

you have to map the button or key of your liking to 'ixeg/733/autopilot/TOGA' there is a documentarion folder included with the aircraft, document '2-interface guide.pdf' on page 14 contains the list of all custom commands you may map. To map a custom command on xplane, you go to joystick & assignment then buttons or key tab then you select your desired button or key then you clic on the top right corner (custom commands checkbox) then you navigate the three to ixeg/733/autopilot/TOGA to map

nice to hear you got your hardware level of fun and immersion increases substantially manipulating external hardware

I did run RWC + SKMP without any ATIS issue. Then i decided to install NOAA to test venturasky script, i immediately noticed a weird behavior. Now ATIS reads current aircraft position winds and altimeter, not station reporting data. i.e. you are 14500ft descending towards the destination airport and destination airport ATIS reads current aircraft position winds instead of destination airport winds. I haven't done any research yet to understand this. Do not know if this is a setting under NOAA i have to modify, or a bug...

go to location->local map and check "disable tail wind ils" checkbox. In those cases that the runway shares the same ILS frequency at both ends, xplane will disable the ILS side having tailwind weather conditions. You are supposed to land headwind. If you share me what airport/runway you were experiencing the issue, i can double check if that airport/runway falls under that category or you are experiencing another issue operating the aircraft systems.

yes that would be great! a few tips: A. Some approaches are LOCalizer based (no full ILS G/S is available) In this case you set your freq. and course. You are flying over a LOC heading interception course, you hit LOC and the aircraft will turn towards the runway tracking LOCalizer. once intercepted. You are responsible to comply the vertical glide path / requirements B. Full ILS approach you set your freq. and course you are flying over a LOC interception heading and you hit LOC mode, the aircraft will turn towards the runway when localizer is intercepted. LOC mode is active. you should also be flying over an interception G/S altitude as per the procedure (you intercept G/S from below), so when your G/S comes alive (monitor FPD) you then hit APP mode, the aircraft will switch from LOC to APP mode and will start tracking both LOC + G/S path on interception. note: During approach A or B if you notice the aircraft tries to fly exactly opposite direction of the runway, this means the runway you are trying to land falls under shared frequency case, you need to disable tailwind ILS on xplane local map. some airports share the same ILS freq. at both ends, on real life only one side is operative at a time and the other side remains off. But on xplane both sides may be ON and the aircraft may pickup incorrect side trying to fly opposite direction, thus xplane includes disable tailwind ils feature.

can you attach a few screen captures to see what the displays, systems are showing while you are trying to engage APP mode? maybe a video?

as per your problem description this is not related to 10.51. seems you are running a mac, you upgraded to sierra os which breaks gizmo. you need to install latest gizmo version.

and also please attach a screen capture to see what the systems and displays are showing.

KSNA is quite a popular airport, any airac cycle date shouldn't be a problem anyways. I do use it all the time at pilotedge -Starting the aircraft "engines running" mode at ksna, do you have the same problem? (go to left menu, preflight and select ready to fly) can you enter KSNA at RTE now? -Can you please attach your xplane log.txt file found under your xplane root folder?

mmmm this is weird. Are you sure you have installed 1612 for the ixeg bird? this aircraft reads the nav database from its own folder structure and should be updated there. If you go to the fmc IDENT page? what airac cycle says there? What airport are you trying to load as departure? i can test it for you as well. I do have latest cycle as well

The documentation was made when Sierra didn't exist. El Capitan was latest OS from Apple at that time The developers are now focused on the upcoming upgrade with new features, improvements and in preparation for XP11

Most likely you are running SIERRA OS which is not compatible to GIZMO plugin version provided with the aircraft. install latest gizmo update and you will be on the air

I think they are working on a major new version of the saab that will be paid, most likely a discount for current customers

do you have xplane failures enabled? go to aircraft -> failures -> check there and you have a reset all failures button.

Hi Jolmos! Oil press & temp is coming from xplane not ixeg, according to IXEG they will engage LR when possible for supporting them on modeling properly a jet engine that works and produce better output at different altitudes, temperatures and thrust settings. I have exchanged a few topics with LiJan about this already, coding this from themselves may take lot of effort and should come from the simulator. This is a non critical topic at this time because it does not affect the accuracy of what the aircraft produces and they are focusing first on the fmc, bug fixes and new features for upcoming release. Regards asymmetrical readings on the engines this is on purpose, not 2 engines are the same on real life. This is just fine. hope this helps

@Frank This happened always to me from the very first version of skymaxxpro, i do run xplane on 2 imacs for achieving 130 FOV and i would say the clouds are not in sync 80% of the time. It is actually rare when they are in sync properly. I am running now latest SKMP + RWC on both machines, tried all possible settings combinations, nothing seems to work to have consistent sync. 80% of the time they do not sync and the experience is pretty weird having overcast one side vs scattered, nothing vs broken, different altitude formation on both sides, raining one side but not the other, etc. The interesting thing is, when i do disable SMP via plugin manager on both machines, default xplane clouds are always perfectly in sync. But i do not like them and they reduce my sim performance. I already put about this issue here, asked the same thing to beta team if someone is testing this scenario when new versions were announced, but no luck. I am a bit frustrated on this topic honestly, i was waiting for V4 to come alive to start my own thread about this and being more active myselft (my fault) on properly opening a ticked for support. If you want any testing, evidence, video, screen capture based on SMP3 i can certainly assist on this troubleshooting for V3 or using this info yourself for V4. I am highly interested on this topic as well. Off course this is not a problem for multimonitor setup, problem is multimachine setup. EDIT: i forgot to mention if matters, the "static" high altitude cirrus layer seems always in sync. Haven't seen any problem to that.

attach your xplane log.txt please

you are still loading them Ground Handling Plugin by JARDesign v.220116 for X-Plane 10 Loaded: C:\Users/Rusny/Desktop/X-Plane 10/Resources/plugins/GndHandling/win.xpl (jardesign.crew.ground.handling).

This error kicks in typically when there is a pilot fmc's programming mistake: -A route discontinuity -Non entered cruise altitude -Non entered weight values on PERF page All common mistakes above impedes VNAV to calculate a vertical profile properly which leads to the simulation to crash. Surely the developers may iron out user mistakes not to see the windows popup, but at the end of the day is quite important you program the fmc right otherwise you will not be able to navigate properly using VNAV. Pay attention to have the fmc fully programmed, check on your LEGS page via PAGE NEXT all waypoint have speeding / altitude populated automatically by the fmc, no waypoint discontinuities, this will be a good indication you did all steps required for programming. Otherwise please attach FMC screen captures i can help what is wrong on your programming.

you are welcome

1. go to your xplane10/resources/plugins folder and remove the folder /Gizmo64.plugin/ (this is the old version) 2. download the new plugin to a temp folder, unzip, and move downloaded /Gizmo64.plugin/ to xplane10/resources/plugins/ load xplane and test, if you still have issues re-attach your log to see it

yes, as per your log file you are running sierra which breaks 737 gizmo. install latest gizmo version and you should be fine.

are you running windows or mac? your problem description looks like you are running mac over sierra os which is not compatible and gizmo plugin required by the aircraft to work is not running. if you attach your xplane "log.txt" file found on your xplane root folder will be much easier to offer you some support than just guessing.

yes i have seen on the charts it has one runway 09 / 27 this falls under the bug. as per the charts you should have RNAV09 and RNAV27, try selecting one of those procedures for arrival instead of just the runway.

There is a known bug that selecting a 2 letter runway arrival causes gizmo to crash. I.e. Selecting runway 22, 05, etc. If you select +2 letters such as 05R, 22L or ILS05 there is no issue. This is fixed for upcoming release. I am not 100% sure this is what you are experiencing, your description is a bit generic to me. Otherwise please attach some screen captures to see your issue.