daemotron

No, only cargo doors will open. Pax doors will come in a future version...

Holy ***, this is going to be really awesome. I'm already addicted

Definitely looking forward to it. Concerning the G1000: at least terrain overlays will come with 11.20 for the map display... But I also like that iPad solution. In that aircraft category, it's not so uncommon to have this kind of retrofit solution...

PAX doors are not yet implemented. For the other problem (camera shake), can you please give some more details? Do you have any other camera or headshake plugin installed? What means "it doesn't work" - will the radio button not engage/disengage, or do you still experience camera shake although the button is disabled? Can you please attach relevant log files (log.txt and GizmoLog.txt)?

Ah, you got the version with alpha floor protection *scnr* No, seriously I can think of two possible causes for this: When pulling the thrust levers to idle, you potentially missed to catch the ghost levers after having disengaged A/T - this would result in the thrust staying where the ghost levers were last before disengaging autothrust Your thrust lever axis could be inversed or incorrectly calibrated.

I'm not sure if this really matters on Windows, but my folder is called "coroutes", not "Coroutes" - and I have no issue loading them in the B733. Concerning SimBrief, make sure you remove any runway and procedure names from the route, as they would lead to another error (invalid format).

OK, that's the problem - the .fpl format doesn't permit to specify runways and procedures. The correct format would be: UMMS GOVIK M863 RUDKA T174 WAR N871 KUKOP N869 OKG UN869 DKB Z818 GEBNO EDDS Runways and procedures have to be selected each time using the DEP/ARR page of the FMS. Furthermore, DCT may only be used between fixes or navaids, but not between a fix and an airport.

@NewSimUser Can you please post the content of that coroute file (i. e. UMMSEDDS.fpl from the coroutes folder)?

Yes, absolutely. Torque indicated is actually a force measured at the propeller shaft, and it's mainly driven by the resistance the propeller experiences when its blades are moving through the surrounding air. With constant barometric pressure, this resistance is a function of the speed of the blades (which could be expressed in RPM) and their pitch angle. So while on ground, the same combination of pitch and power setting will always result in the same torque. Now let's take off and start climbing - you keep power and pitch commanded the same way all the time, but what changes is the barometric pressure of the surrounding air: it gets "thinner", creating less drag on the propeller blades and thus resulting in a lower indicated torque (and also in a lower propulsion power of the engine, as the mass of the airflow becomes smaller). To counter this effect, you actually can adjust your power settings during climb (in some aircrafts you actually have to do this, but stay within the engine's operating limits!). This is btw. also the reason why it's so important to disengage the CTOT system after take off: CTOT (constant torque on take-off) is a system that will adjust the commanded power to keep the preselected torque. If you keep it engaged during climb, it will command more and more power to compensate for the altitude-driven torque drop, until the engine catches fire or fails otherwise.

Hehe, that's the bane of realism in flight simulation... there's a reason why IRL a Saab would be operated by a flight crew of two

@teban13 Have a look at the IXEG1 youtube channel: https://www.youtube.com/user/IXEG1/videos The videos you're looking for are called "KPHX-KLAX Departure Part 1" and "KPHX-KLAX Departure Part 2" (the hydraulics failure is demonstrated in part 2).

Looks neat!

This sounds like a Gizmo soft crash. If that happens again, please take a screenshot of the popup (shift + space usually will do) attach the files GizmoLog.txt and Log.txt to your forum post Open a dedicated forum post in the 737 support sub-forum (http://forums.x-pilot.com/forums/forum/200-gizmo-soft-crashes/)

Absolutely phantastic!

Actually in X-Plane this effect may come from your loading order of scenery and libraries in the scenery_packs.ini file. The SeasonsXP library will only replace vegetation coming from the standard library, so all airports using standard library trees will benefit from the replacements. Custom vegetation will not be altered, so they will be displayed in their original shape. However, there are some caveats - for instance you cannot use another library replacing standard trees (or other standard objects) in parallel with TerraMaxx. A good example for this would be the HD Forests library by MisterX6 - if you put them above SeasonsXP in the load order, you'll always see green HD forests. If you put them below, you will see the TerraMaxx trees, but you then could actually remove the HD Forests library as those trees will never show up.

Just on my first flight with TerraMaxx, flying in deep winter along the Canadian Rockies. This really adds a lot to the immersion, love it so far! Now I'm looking forward to learning how to make my custom airport sceneries compatible...

Chiming in on the same issue - CTD when xEnviro downloads METAR. Some observations from my side: The crash happend for me after ~1hour of flight on ground, after having followed the parking checklist, after depressurizing the cabin and the moment I pushed open the front door (it was unlocked before). On preflight I had the front door opened already without any issue. I use xEnviro alongside with the IXEG B733 (latest version), so far no CTD experienced - either I was lucky, or the CTD is not directly resulting from a Gizmo vs. xEnviro conflict, but instead is only triggered when Gizmo is used in a specific way (only speculating here, not knowing the differences in how both developers use Gizmo). crash_logs_and_dump.zip

Just fyi, xEnviro 1.07 (currently released version) has a known issue with transparency, not only with the 733, but with other models as well (particularly noticeable with aircrafts having prop discs). This issue is marked to be fixed with 1.08, whenever that will be released... (and introduces new issues )

You seem to have a problem with iBlueYonder_libs - can you check the contents of that directory? It should contain an objects subfolder, and a library.txt. Apparently it's listed in your scenery.ini, but the content seems to be inaccessible (maybe also blocked by permissions or an antivirus thingy?). Also you seem to miss a bunch of default textures; you can use the XP installer to add those missing files (simply by running the XP updater).

Seems we have a new player on the market when it comes to XP scenery: https://orbxdirect.com/product/kcgx/xp11

@Dhruv I think what Jan wanted to say that in the days back when he flew the B733, VNAV wasn't used a lot. As of today, there are also in Europe more and more airports trying to develop continuous idle descent profiles (I know at least we (Airbus) worked with EBBR on that). However that's far more complex than most people imagine; as you already touched the point let alone the different aircraft types & capabilities, but of course also the fact that there are some airports in Europe you hardly ever get into without holding (LFPG, EDDM in winter, ...) - there a type-specific VNAV profile would be wasted...

@marpilot I don't think that's even possible. AFAIK, Gizmo itself is installed as a global plugin, so you can only have one version of the Gizmo "engine". The aircraft models themselves only have the scripts that are run by Gizmo.

@crisk73 maybe you could check the file "Aircraft\X-Aviation\IXEG 737 Classic\fmc_data\SidStar\KIAD.xml" - it describes the waypoints of the procedure and is read by the FMS. In the Navigraph file, the STAR you selected is defined like this: <Star Name="HYPER7.19C" Runways="19C"> <Star_Waypoint ID="1"> <Name>DELRO</Name> <Type>Normal</Type> <Latitude>39.965475</Latitude> <Longitude>-76.625344</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="2"> <Name>LIRCH</Name> <Type>Normal</Type> <Latitude>39.826767</Latitude> <Longitude>-76.922231</Longitude> <Speed>0</Speed> <Altitude>14000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="3"> <Name>BINNS</Name> <Type>Normal</Type> <Latitude>39.785061</Latitude> <Longitude>-77.010994</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="4"> <Name>HYPER</Name> <Type>Normal</Type> <Latitude>39.683933</Latitude> <Longitude>-77.225094</Longitude> <Speed>250</Speed> <Altitude>10000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="5"> <Name>COVUR</Name> <Type>Normal</Type> <Latitude>39.359072</Latitude> <Longitude>-77.453469</Longitude> <Speed>0</Speed> <Altitude>7000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="6"> <Name>DIMKE</Name> <Type>Normal</Type> <Latitude>39.309106</Latitude> <Longitude>-77.454383</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> <Star_Waypoint ID="7"> <Name>HOOSR</Name> <Type>Normal</Type> <Latitude>39.226192</Latitude> <Longitude>-77.455597</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </Star_Waypoint> (skipping the transition part here). Can you check whether in the NavDataPro variant, the waypoints are defined in the same manner? Could also just be a semantic issue (tag not properly closed or similar), but I don't have the NDP files for comparison...

Airport code has already been created, so it should come with XP11.20. However, there's currently a general issue with those Canadian airports having a number in their ICAO code - Laminar has borked their meta data. As an example, let's take CAD4 (Trail). It exists in XP, but as "AD4", not "CAD4" (this was changed from XP10 to XP11; in XP10 all those airports had their 4 digit ICAO code as ID, not the 3 digit local code). The AIRAC data however identify this airport with its proper ICAO designator, "CAD4". This now has several side effects: In the default GPS / FMS, you can select the airport only by its short ID ("AD4") In the default GPS / FMS, you cannot select procedures, as they are linked to "CAD4", not "AD4" (CIFS or whichever AIRAC format you use, it doesn't matter) In the IXEG 733 FMS, you cannot select the airport at all, neither with its ICAO nor short designator I already contacted Julian concerning this issue. He changed the meta data for CAD4 to now have an FAA identifier of CAD4. Apparently this should fix the default GPS / FMS discrepancies, but I'm not sure about the IXEG FMS. If Tom or Jan could confirm how the meta data have to look like (i. e. what you're validating against internally), we could crowd-source the work and file change requests for all those Canadian airports concerned (they're quite numerous, though not all are fit to fly in with a 733 ).

Push that to the bottom of the priority list, it's really only minor: (1) ALT selector knob: the "SEL" texture sometimes "jumps" by 180° (2) The Heading selector's rim texture seems to be moving in the "wrong" direction (the white triangle is turning in the correct sense) No influence on functionality, it's just the texture animation (and you will only notice it when looking directly at the knobs - from an angle it's hard to notice). Log files attached, though I doubt they will be of much use GizmoLog.txt Log.txt