mmerelles

can you attach your log.txt file again now? please do not copy/paste you have an attach file option by clicking "choose files" or draggig the file to the post while editing

you should have a "reshade-shaders" folder under xplane root folder or under xplane/resources/plugins/ find the folder "reshade-shaders" and remove it entirely out of xplane.

as per your log your problem seems reshade to me. Please remove it entirely from your system for testing purposes.

maybe you aircraft is not activated after all. You should attach your xplane "log.txt" file found on your xplane root folder after trying to load the aircraft and close xplane. also a screen capture of your entire overhead panel and the front panel may be helpful just in case something is miss configured. EDIT: also consider disabling a plugin does not mean it doesn't load. You need to remove the reshade plugin from the plugins folder and restar xplane to be sure this plugin is not the problem

yes, you are completely correct. I ve forgotten ixeg modeled an option on the preferences menu to enable ice/rain effect.

The speed brake has no settings like a switch or a knob, it is a handle lever that works vía xplane speed brake axis dataref To control the speed brakes lever, you may: A. you can map xplane speed brake axis to a hardware handle lever you have (same as you map a throttle lever) B. you can map 2 buttons or keys to xplane 'sim/flight_controls/speedbrakes extend one' & 'speedbrakes retract one' (each clic will cycle them up or down a bit) C. you can make a lua script or similar to manipulate xplane dataref speed brakes axis writting values 0.xxxx to 1.0 (sim/cockpit2/controls/speedbrake_ratio) Or did you mean wheel brakes knob settings? (RTO, OFF, 1, 2, 3, MAX) dataref 'ixeg/733/hydraulics/hyd_auto_brake_act' RTO = -1 OFF = 0 1,2,3 setting = 1,2,3 respectively MAX = 4 hope this helps

on real life pilots are always sacanning visually for icing formation on the wings when conditions exists. on the sim there is no visual clue, but ANTICIPATION is key. Anytime you are flying <10C TAT and humidity exist (clouds, rain, snow, etc.) turn on anti-ice systems until icing conditions no longer exist. Icing is extremely dangerous on real life as well because aircraft looses aerodynamics and gains weight, you are basically a piano falling from the sky. Anticipation is always key.

i do use some of the misterx scenery, KLAX, KSFO not a single crash here. Maybe you will be required to take some time to re-install them one by one to see which one has the issue.

This aircraft is compatible to both windows and mac platforms. You just use the installer based on your platform. You can delete osx-installer.app if you are windows based. If you just purchased and installed the aircraft you should have the latest version already 1.0.7. To confirm open xplane and load the ixeg 737, you can check the version you are running on the left side popup menu of the aircraft.

this crash is about: -no vram -damaged scenery package (most likely) I would recommend you remove temporarily the entire sub-folders below: 1. Custom Scenery/SimHeaven_VFR-Landmarks_World/ 2. Custom Scenery/SimHeaven_VFR-Aerials_World/ try again the same flight and confirm no more crashes please. note: i can assure you this crash is not originated on the ixeg bird.

I think your example does not apply here. IXEG team made it pretty clear, PUBLIC and straight forward the product status for the release for everyone make their on decision whether to buy it or not. You do not see this transparent communication quite often.

yes, but you need to install first a free plugin named xjoymap found on the xplane org forum. Once you have the plugin installed and working: 1. Go to the saab 340 root folder of the variant you use. i.e. passenger variant 2. Create a text file “xjoymap.ini” (this will be the config file for the assignment) 3. Paste the configuration below. Your “xjoymap.ini” file should look like: [saab CL both] axis=31 dataref=LES/saab/CL/manip_common(float) drl=1 drh=0 note: 31 = is the axis ID of your hardware lever on xplane. To know the ID number of your lever axis you want to use. Go to the saab axis menu. as usual for axis assignment and move your lever to assign it for left or right CL just for the purpose to know the lever id on xplane I think the developers said they have managed how to assign the CLs easier for the upcoming version. As of know, just follow the steps above is quite easy and works great.

can you attach your log.txt & the gizmo log please after the crash? both are found under the xplane root folder. it doesn't look any normal, maybe we can help

This will not work ever because this is to map a custom command. Custom commands are actions they do not accept any parameter. This works because you are actually declaring as a dataref and sending a +1 value to whatever the memory position is holding.

Guys all those you were discussing above such us 'ixeg/733/radios/radios_com1_left_mhz' are datarefs not custom commands. Your software interface (flywithlua, Ardsim or whatever you use) are required to write a +1 to increase to mimic rotating right and -1 to go backwards rotate left.

does this means they may also extend chart coverage? I have the 12 month subscription and find it very useful for flying usa and europe but argentina has no charts not even for major airports i also like to fly NZAA to NZQN (Queenstown) no charts either as of now.

do you have a specific repeatable case you can share the details to reproduce? Part of 1.1 target is to squeeze out as many bugs as possible that leads to gizmo softcrash. I presume the developers will be very happy to see an issue that is repeatable to understand what is going on and fix it or simply to double check is already fixed.

xplane 10 steam does not entitle you for xplane 11 key. Only xlpane 10 digital from laminar purchased starting xp11 announcement works for xp11 as well. Steam does not apply. you can use xp11 in -demo- mode. which means you are restricted to ksea area and for 15 minutes each time you load it.

yes, upcoming 1.1 release will include TCAS and distance to next waypoint working on the ND.

please attach your xplane 'log.txt' file found on your xplane root folder to see what is going on.

I assume you are under windows platform. You need to go to windows defender configuration and set an entire folder exception for /x-plane/ root folder (note it is an entire folder not file exception). Problem is when you modify something inflight, the fmc keeps recalculating the values until you EXEC (commit) and windows defender kills the CPU. If you installed a third party AV instead of defender, then set the exception there. I have no idea. I do not use XP11 yet.

Glad to have helped.

Cool let us now how it goes. note: I forgot to mention xplane 11 beta seems to have a parsing issue were items (custom commands within the trees) may be displayed unnamed at first. If that happens to you map any item under the appropriate tree 'ixeg/733/autopilot/', then apply and close. The next time you open to re-map they should be named properly for selection.

1. you select the button you want to map and press EDIT (button 11 in my example) 2. On the right side, navigate to the +ixeg tree: ixeg/733/autopilot/AP_disengage (for A/P disc feature) ixeg/733/autopilot/at_disengage (for A/T disc feature) Screen captures attached for your reference. Note: this is my xp11 beta install on the laptop (not at home now) and my ixeg bird is installed on my home simulator. So you will not see the ixeg tree listed on the screen capture attached for your reference but this is to give you an idea were to find it. It should be the same root tree level than +ATC +ANNUNCIATORS etc.

A/P disc & A/T disc for a boeing requies very specific modeling to work as it happens on the real aircraft using xplane default commands will not work because this is generic. you need to map the correspondig ap_disc and the corresponsig at_disc from the ixeg/ custom command tree