mmerelles

are the packs set to auto? maybe you forgot them to OFF during engine startup? unfortunately your screen capture is very restrictive and i can not see the packs. please make a full overhead panel capture next time, also forward panel screen capture to see everything and give you better support

You can activate specific failures manually via ixeg failures left side menu and also via xplane flight->edit failures menu Or, if you are interested on having random failures for non standard procedures training you may consider this script by Tom REFERENCES BELOW:

Sounds like you are not having enough torque for takeoff. are you sure the condition levers are set to MAX and not beyond MAX which is T/M? When you move the condition levers forward, pay attention MAX position is not at the end of the lever range, this is T/M, MAX position is just before that, there is a detent there for the MAX position

Never seen this on my aircraft neither on the forums. Maybe a plugin conflict you installed? attach your xplane log.txt file found on your xplane root folder after this happens.

i do assume you are xplane 11? this is a well known problem recognized by laminar already and expected to be fixed for 11.10, happens to any aircraft.

Try going to the aircraft menu on xplane, then clic customize for the ixeg bird, then on the top right corner clic "regenerate icons".... it will take a couple of minutes and should work

IXEG uses standard xplane commands for speed brakes. You need to map 2 buttons or keys of your liking to: -sim/flight controls/speed brake extend one -sim/flight controls/speed brake retract one Depending you press extend one or retract one it will cycle between OFF / ARM / LOW / MED / FULL speed brakes.

Several actually... 0:25:31.508 I/DSF: Warning for missing scenery file: +23-089 0:25:31.548 I/DSF: Warning for missing scenery file: +23-086 0:25:31.548 I/DSF: Warning for missing scenery file: +23-088 0:25:31.582 I/DSF: Warning for missing scenery file: +23-087 0:33:42.894 I/DSF: Warning for missing scenery file: +24-089 0:33:42.964 I/DSF: Warning for missing scenery file: +24-088 0:33:42.964 I/DSF: Warning for missing scenery file: +24-086 0:33:42.989 I/DSF: Warning for missing scenery file: +24-087

No need to disable, go to windows defender configuration in windows and there is an option to set a folder exemption. Put one for the entire /xplane 11/ folder. note: windows will reenable defender at all the time during updates. This is not only about navdata. Please make a video at your earliest convenience to share so we can double check what the systems & displays are telling, what that airport ils issue would be. etc. We are blind at this time, we do not even know what airport ils procedure you are making reference to. what the fmc says if you go to ident page?

1. Your windows defender is the issue. Go to windows defender configuration and set a "folder" exemption for the entire xplane root folder. Not file, but folder exemption. windows defender tryies to analuze the fmc scripts when you make changes inflight, kills the pc cpu and the simulation is over. 2. Yes, this is a known problem on current vnav implementation go to legs page and edit the altitude manually enter XXXXX and press corresponding right soft key. This will be addressed when the vnav update is ready. 3. Most common issue is navdata and scenery does not match. This is not the aircraft.

I did not test this aircraft on xp11, can not comment on that. Regards the brunner yoke -Duplicate the ixeg profile if you like it on the CLS2SIM and rename to SAAB340 -Go to Autopilot tab, make sure 'Don't set pos in AP mode' is checked for all axis. Otherwise the aircraft will move the yoke, the yoke will move back the aircraft controls in a non ending loop. Hope this helps.

Most payware aircraft uses its own custom commands and datarefts to mimic its counterparts real life operation as much as possible. I would suggest you use a per aircraft profiles basis configuration. To achieve this you can use a free app like x-assign or use a lua script that handles all your aircraft profiles. The idea is, when you select a different aircraft in xplane all your joystick/buttons, keys gets reconfigured automatically for that aircraft. i.e. you can use the same joystick button for a/p disc to any aircraft.

IXEG simulated some marks on the whinshield, they look really nice. No windshield is crystal clear and free of marks on the real thing. I presume you are having an issue with your graphics card drivers or rendering settings on xplane. Or maybe any lua script that messes xplane arts or so?

if you use the disengage bar it will kill the FDs among other things. Do not use it. you have to use the a/p disc button located on the aircraft yoke. map to custom command 'ixeg/733/autopilot/AP_disengage'. it requires 2 clic as per the real thing. First clic disconnect a/p and you get an aural warning to be sure this is not an accidental disconnect, second clic cancels the warning. EDIT: i just realized you were also asking how to mimimic pressing the A/T DISC buttons on the throttles for a/t disconnection on final approach. you have to map any key/button of your liking to 'ixeg/733/autopilot/at_disengage' note: all custom commands available you can map are on the aircraft included documentation '2-interface guide.pdf'

your install is a mess. 1. Delete the following files F:\Programs/X-Plane 11/Resources/plugins/mac.xpl (file) F:\Programs/X-Plane 11/Resources/plugins/win.xpl (file) F:\Programs/X-Plane 11/Resources/plugins/64/ (entire folder) F:\Programs/X-Plane 11/Resources/plugins/Gizmo64.plugin/ (entire folder) F:\Programs/X-Plane 11/Aircraft/Extra Aircraft/X-Aviation/ (entire folder) now run the ixeg installer and please select properly your xplane folder. It is under F:\Programs/X-Plane 11/ if you do a better job this time, the aircraft will be installed automatically within: F:\Programs/X-Plane 11/Aircraft/X-Aviation/IXEG 737 Classic/ the gizmo plugin will be installed automatically to: F:\Programs/X-Plane 11/resources/plugins/Gizmo64.plugin/ Please do not start moving things manually.

most common cause of this behaviour, you did not select your xplane root folder properly during installation. please attach your xplane 'log.txt' file found on your xplane root folder after you try to use the aircraft and then close xplane. The log should tell what is going wrong. note: attach the log, do not attempt to copy/paste. Use 'choose files' hyperlink when replying to attach a file

it has been said there was a mistake when packaging 1.2 and they didn't went through but coming back next update.

your problem is windows defender killing the cpu when you make any change on the fmc. Go to windows defender and set a 'folder' exemption for the entire /xplane/ (use folder not file exemption) problem solved!

attach your log.txt file found on your xplane root folder after a crash. in my experience, if the log has absolutely no trace of the crash coming then your video card is getting out of vram. To confirm: 1. try one flight you typically crash but lowering down as much as possible for testing those vram heavy consumers like textures, clouds, orthos, etc. 2. try implementing any free application for monitoring your gpu vram usage real time. Do not use xplane monitor, this only shows textures nothing else, this is not total vram usage at all edit: about the xenviro thing, if you monitor your vram usage having it installed vs not, this app is a heavy user. They said to be working hard on vram management/optimization for upcoming update.

the official list of custom commands & dataref is included with the aircraft in the documentation folder, file "2-interface guide.pdf"

Boston runway 04R/22L share the same ILS frequency at both ends 110.30. On real life this would not be a problem because only one side of the runway will be operative at a given time as per weather conditions (head winds) while the other side ILS system will remain shutdown. On xplane both ends will be avialable at the same time which may be an issue: -You need to configure "disable ILS tailwind" on xplane local map (xplane will disable ILS tail wind runway for shares freq. cases to mimc real life) -If you have this already enabled, maybe you were trying to land tail wind and that side was off Please attach some screen captures when this happen to know what the system, displays says

can you attach your xplane log.txt file found on your xplane root folder after you tried to use the aircraft? please do not copy/paste, attach using the hyperlink below on the post edit "choose files..."

very cool, now you need to order a second piece to complete the cockpit for the fo side.