mmerelles

Given your latest posts, "I think" we have a miss understanding what -compatibility- means. compatibility = it has been tested and certified by the developers for loading properly, it doesn't crash, all systems are fully working, it can be used on the sim with no trouble. full xp11 bird = it has been reworked as much as required for the aircraft perform spot on to the manufacturer performance charts on all aspects, it will also take advantage of all latest sim tech like PBR rendering Going back to your FF / IXEG notes, both are under -compatibility- status, both have released updates to assure they are compatible to xp11, BUT both are still working on full xp11 bird updates. Go & try to compare climb ratios, or speed brake performance, etc. etc. etc. xp10 vs xp11 and you will be quite surprised about the findings. Go and re-read 767 xp11 policy carefully from FF which was released under XP10 as IXEG737 and as SAAB340 to compare apples to apples. Whats the deal about SAAB 1.4 and 1.5?? as you said, they look the same... yes! 1.4 is fully tested by the developers on xp10 and it introduces fixes for all known issues for their large user base still here (they didn't perform any testing on xp11 at all, if you use it on xp11 is entirely at your own risk) 1.5 is the same than 1.4 yes, but fully tested by them on xp11 and applied any fixes required to make it load, not to crash, systems working, etc. Yes it could happen nothing is required, or minimal, and in the end it looks the same than 1.4 for xp11. 2.0 is when they will develop and release a full xp11 bird. they will recalibrate the entire model to guarantee it performs by the charts, they will take advantage of latest rendering stuff.

Consider they have to take care of a broad audience, preferences, simmer priorities. There are a lot of people that do not care on realistic aircraft performance by the charts and just wanna have fun, some people can not read/care about performance charts, neither are pilots on real life to feel the difference on an aircraft performing right or not. If you look around the forums a bit, you will notice there is a large user base that switched to XP11 from the early public beta1 trying to load, putting patches via planemaker, sharing workaround on the forums to make the xp10 birds load and just have fun. i do not see anything wrong from them delivering a compatibility patch for those, so all systems are functional. This is what most developer are/have been doing by the way to attend than demand on the first run. Release a compatibility patch, not fully redone birds in the meantime. Having said that, there are other people (like myself) were having an aircraft that perform by the chart is all what counts. For those of us, we are awaiting full XP11 birds from all developers we like. Delivering/retuning an XP11 aircraft by the charts requires a lot of work, because the ground model changed, drag model changed, engine model changed, flight dynamic changed and also the cosmetic thing due to the new PBR rendering engine. If you follow laminar's developer page you will also notice Laminar is still tweaking XP11 model release after release, they are not done yet. This makes developers lives even more complicated to be spot on over a moving target. They are not saying you have to pay and wait 1-2 years! The way i do understand this: 1. If you are still having XP10 as your primary sim (large user base), this is the newest 1.4 update that fixes/improves several known issues for the best experience. 2. If you are an xp11 early adopter that wanna use the bird on xp11 no matter what, a basic compatibility fix is coming (lot of simmers are on this category as well) 3. if you are awaiting for this aircraft being full xp11 performing by the charts and having latest tech on rendering you are set for 2.0. (given the implications i wouldn't expect this to be fee, maybe a discount for existing customers, but this is just my pure assumption not any statement). You can jump onboard at the timing you feel confortable to given the facts if you are not customer already. just my 2 cents

These simulators are pretty amazing stuff they feel so real. I payed USD 800 for 1hs which includes 30 minutes briefing. 01:30 total. The 737800NG is one of the the most expensive they have, they sayd it is based on latest AIR technology for motion which is smoother. Cost 17 us million They have 6 certified full motion sims -737-300CL (i wasn't aware before reaching their facilities, otherwise i will have tried this one for sure) -737-800NG -757-200 -787-800 dreamliner -MD82 -MD88 They do train/certify pilots from all around the globe and use the sims free time to schedule common people.

A per your log you are running lot f plugins. I would bet your issue is xenviro + ixeg. this combination causes crashes to a lot of people. For the purpose of testing, move xenviro out of your plugins folder and do some testing. You can put it back after testing.

Been on the Panam academy for a 737 training session. Landing the 737800NG, weather set to 200 ft overcast and the instructor put a surprise. An aircraft pulling into the runway and required to jump over and land. A LOT OF FUN. Those simulators feels like the real thing. AMAZING No A/P, A/T used, full manual approach down to the runway ILS 04R JFK Hope you like it.

The IXEG bird runs ontop of gizmo plugin which is basically a scripting engine. When you perform a change on the fmc inflight, the fmc runs some scripts to keep recalculating the values until you hit EXEC (commit the changes). Windows defender tries to analyze that realtime getting 100% of the CPU for it and the simulation goes hell (the cpu is locked to defender, the gpu has nothing to do because the cpu is overloaded, you get a freeze or a 1/2 fps at best) So don't be paranoid and put the exclusion, that feature is on windows defender for a reason as Cameron said. You are not excluding the unknown.

this is weird, it worked to everyone else to my understanding. 1. have you followed this guide to make sure? 2. maybe a plugin conflict? have you tried removing all them except gizmo just for testing? attaching your xplane log.txt file found on the xplane root folder could be usefull 3. Have your confirmed the minimal electricity for starting the apu is set? fuel available? do you have installed any saitek switch panel or similar? did you kept holding the start switch for a few secs before release? 4. can you attach some video or screen captures?

hopefully not, looks amazing

do you use external hardware joystick/yoke? seems your hardware is sending noise signals from the potentiometers overriding AP. If you look at your PFD annunciators the aircraft is probably entering CWS P yellowed mode Go to ixeg left side menu, move your CWS nullzone slider all the way to the right, this will prevent AP disconnecting when your hardware sends noise spikes

The T/C is an estimation based on no winds, standard temperatures. Under these scenarios you will reach T/C quite sooner than anticipated: -Having colder temperatures than standard (more climb ratio) -Having head wind component (moving upwards not forward as much as expected relative to the ground/distance) As per your screen capture it seems you have been experiencing quite strong head wind components. Look at your GS is quite low actually. When having head wind airspeed will look the same, but the aircraft is actually not moving forward that much in relation to distance traveled TC/ground. The aircraft is basically climbing but not moving forward that much as expected during planning.

Press RTE and re-enter origin airport this will clear anything you may have entered/selected for the route note: works for any boeing fmc

go to Flight -> Edit failures, on the bottom of the screen there is a checkbox enabled by default that says 'set global mean time between failures'. Untick this checkbox to disable random failures

the log file you shared is from plane-maker not from xplane 1. run xplane 2. try to use the 737 on the simulator 3. close xplane 4. attach the log.txt file here

seems like your aircraft is not correctly installed and or your licence activated. can you please attach your xplane log.txt file found on your xplane root folder. do not copy/paste, attach via choose files here while you edit your post

If you use external hardware for the landing gear such us saitek switch, the rattling is normal when go back that much on the replay to the point your hardware landing gear position was set to down after landing but when on replay the aircraft gear is still up I.e. try loading xplane/aircraft having your landing gear lever to up already and you will have the same rattling because the aircraft will be gear down on the ground. This is Xplane fighting your hardware over the landing gear dataref

1. load xplane and try to use the ixeg aircraft. it will not work as per your description. Close xplane 2. here when you replay there is an option on the bottom part of the text field that says "choose files" (this is to attach files), navigate your hard disk folders to the destination were you have xplane installed, select the file "log.txt" to attach. Having the log file we can see why the aircraft is not working

gizmo plugin included with the aircraft is not working, this could be due to: -You antivirus blocked and/or quarantined gizmo executables -Your aircraft installation is incorrect -there is some issue with your aircraft activation key. Can you please attach (do not copy/paste, attach) your log.txt file found on you xplane root folder after you tried to use the aircraft?

The same reason most PC, laptops, TVs, etc are not touchscreen but full of dirt and finger prints on the screens. Because you manipulate them, because you put your fingers on them when discussing something with someone else, because those instruments live on the real world. I remember pretty well when sat on a cockpit for the few hours learning to fly, it was very noticeable for me how different a real aircraft is from a simulator. On the real aircraft you have lot of dirt, uncalibrated instruments, scratched glasses, y i can go forever... The confort of a simulator were everything is always the same is present just at home.

very nice

VNAV will not work without a valid vertical profile. it is always quite important you review the entire legs page during preflight to make sure you have everything right. Sometimes complex SIDs including multiple/combined altitude constrains, or even bugs on the navigraph database, may lead to a waypoint having 0 as the altitude constrain on the flight plan. This is not valid for VNAV to work, you edit those manually on the legs page and problem solved. note: looking at the charts is also useful to anticipate potential problems, anytime you see on a SID or STAR a waypoint that has a double altitude constrain i.e. WAYPOINT cross "7000A & 9000B" the FMC will likely put on the legs page 9000A which is incorrect. So you edit those as well for a proper vertical calculation. This will be improved when VNAV is revised. hope this helps

Austin, as per your screen capture it seems the engine adjustments required on planemaker were not made. The aircraft idle is too low N1 % is 11 should be around 21 can you open planemaker again and confirm: -you did not configure another field? -were both values set hi & lo? -make sure you save the changes via planemaker menu before you exit. hope this helps

pareciera que el avión por algún motivo no quedó correctamente instalado. Por favor adjunta los siguientes archivos de log, después de intentar usar el avión log.txt gizmolog.txt estos archivos los encuentras en el directorio raíz de xplane. Para adjuntarlos le das clic en "choose files" cuando estas editando el post

can you make a screen capture of your entire forward panel (or several screen captures of partial areas) to see what the system status are by the moment you try to engage AP? is very difficult to diagnose what problem you are having without any detail other than AP does not engage. I have a clue what could be wrong but need to see you screen captures

When you make any FMC change inflight, the simulation makes calculations realtime until you hit EXEC, but problem is your windows defender starts inspecting the script running killing the CPU, all the simm goes to 1fps at best being unusable. Please go to your windows defender configuration and set a -folder- (not file) exception for the entire /X-plane/ root folder. This will cure the problem entirely. If you use another security platform different than windows defender, set the exception there.

@JGregory hows the saab update coming? any screen capture to share on the progress? I like this aircraft so much. I just bought a new powerfull pc for migrating to xp11 (intel 7700k + 1080ti) to replace my imacs, awaiting the arrival within the next 15 days.