mmerelles

we trust you but to help, we need more information! how someone else will be able to reproduce your issue if you do not provide anything? please share your fmc programming, departure airport, procedures , runway, route, altitude, navdatabase version. All details you can share to reproduce your problem. or you can make a video where you experience the problem. we need something!

Hi @ErmakDimon a few comments: 1. as you already experienced never ever use ap_toggle xplane default feature because this aircraft is a complex boeing with very complex a/p modes primary, secondary and intrincated systems as per the real thing. if you want to map a joystick button or key of your liking to disengage a/p on final approach, ixeg provides a custom command you have to map to your key or button "ixeg/733/autopilot/AP_disengage" Once mapped you have to press it twice, first press to disengage and a warning sound will kick in, second press to acknowledge and cancel the warning. Just like the real thing. 2. i do not know exactly how far "ap_servos_toggle" will mess the ixeg 733 systems, so best course of action if this happens again should be -reset everything- and -re engage-: -Clic the disengage a/p bar located below the a/p puttons -Disable both FD switches left & right -Re-engage FDs left & right -Clic CMDA to engage A/P left -Clic LNAV and VNAV to re-engage In the mean time you have to fly manually. Also note when this happens the aircraft may become unstable, you are too high and too fast, desktop yoke hardware will result being very sensitive to operate the aircraft. And while you try to re-engage A/P it may keep disconnecting back because is receiving signals from the yoke overriding A/P. So, also set the CWS nullzone slider bar on the aircraft preferences (left side menu) full to the right, this will prevent A/P disconnecting and going into CWS mode while you try to engage LNAV or VNAV but still controlling the aircraft. hope this helps

if you are experiencing continuos hard crashes, most common root cause i have seen is: -VRAM exhausted. Overloaded rendering/addon settings. Sometimes performance goes hard down badly, sometimes it makes the sim hard crash. -Plugin conflict. -1050beta is still on its baby steps and having several crashes if you are running it.

very nice videos! i am looking for selling one of my full rig imacs and getting a powerfull pc based on gtx 1080, it is shame i can not crank anything up on my imac for autogen, clouds, etc. and they cost twice

I wouldn't call zero plugins you are running silverlining for skymaxxpro and real weather connector, anyway i wouldn't think that is the problem at all. Lot of people use them, i use them myself with no issue. by looking at your log file, i see you are running AI aircraft 2 of them besides you. This has been a problem in the past specially when AI tries to load the 737 twice. Just for the purpose of testing i would recommend you go to Aircraft -> Aircraft & Situations -> Other Aircraft tab and set it to 1 (just you). Check if problem is solved. Also double check on joystick & assignments your shift xxx assignments are still in place, sometimes the pref file get messed during betas forth & back. Does them work properly to other aircraft normal and replay flight?

seems like a camera plugin conflict? do you use any plugin to control de camera? attach your xplane log.txt please!

I am assuming you are on the ixeg733 or what aircraft? you will not hear anything by default on the comm frequencies (clearance, ground, tower) unless you are making active use of ATC feature or an online network. but you should hear ATIS automatic weather information reading by tuning the proper frequency (and being in range!!!) please follow the following steps to confirm: 1. sit your aircraft at KSNA (John Wayne) 2. select ready to fly mode on the IXEG preferences so you do not have to mess with electricity issues if you are unsure. 3. tune KSNA ATIS weather frecueny: 126.00 and switch it to active (user your comm radio1 left side of the pedestal, comm radio 2 audio right side is off by default you need to know how to enable it) you show start hearing the audio.... note: -double check audio is properly set on setings->audio -audio uses operating system synth speach, it should be available hope this helps

where do you get this? copy/paste from boeing: Landing Gear warning Config - Visual Indications (737-300) The landing gear indication lights are activated by signals from each gear, the LANDING GEAR lever, and the forward thrust lever position as follows: Green light illuminated – landing gear is down and locked. Red light illuminated – • landing gear position is in disagreement with LANDING GEAR control lever position (in transit or unsafe) • landing gear is unlocked • landing gear is not down and locked, and either or both forward thrust levers are retarded to the idle range. All lights extinguished – landing gear is up and locked with the LANDING GEAR control lever UP or OFF.

i tried ro recreate your flight and had the same weird behavior. The aircraft does not try to join and follow the magenta to the right when engaging LNAV. Because you did not select any arrival star neither runway (which was a problem on the past), i tried recreating the flight again but selecting BAVES1 arrival and runway 27. i selected the arrival procedure with no issue, as soon as i selected runway 27 and i had a gizmo soft crash! I cleared everything and managed to complete the fmc programing including the arrival and runway. Departed again and had the same weird LNAV behavior, i manually pressed LSk3 and then LSK1 skipping the initial LSK1 conditional and LSK2 (int) orders from the legs page and now LNAV was able to turn right and join the magenta properly. A bit later i realized VNAV was unable to engage, i had to remove the miss approach procedure from the legs page leaving RW27 as the last step on the plan for the fmc to allow me engaging vnav and resume the flight. conclusion: there is a big mess here trying to recreate this flight, full of problems. I wonder whether this is related to navigraph database (running 1607rev2 here) or part of the fmc fine tuning still in progress. the developers should try to recreate this flight and shed some light here.

mmm this is weird. can you share more details? i would be happy to reproduce it and provide more evidence to the developers. It is necessary you share the detailed flight plan you loaded on the fmc, departure runway, sid, route, arrival star, runway. What altitude, ci, you configured? What navdata version you have installed? it could be also an error on the navdatabase. Just saying it doesn't work will not help the developers reproduce and fix it if anything to blame ixeg for.

The zip file is to update while the hotfix online system is down! Go ahead and update via the zip installer provided

yes override your existing "B733_prefs.txt" file on your IXEG 737 root folder with this one (save a backup of the original file just in case you want to rollback) Load xplane and use numpadkeys 0-9 to select the different views and experiment what this guy is providing you for camera pre-sets. Off couse by overriding your existing file you will loose -your- #0-9 camera view presets, you are replacing the entire file. But once you determine the wings view you like you can re-program the other slots back as per your liking note: You may also try to copy/replace wing view parameters into your existing pref file but this will be much harder.

ohh i see now why he see 5000, nice touch

run the installer provided here and it will update you straight to 1.0.7

transition altitude (TA) is 18000 by default! do you mean to change it from 18000 to 5000 instead? it is on the PERF PAGE 1. Press MENU 2. Press LSK1 (FMC) 3. Press LSK6 (INDEX) 4. Press LSK3 (PERF) 5. type 5000 on the sractchpad and press RSK6 to replace This is the step by step, there are several pages on the fmc where you can press INDEX soft key then PERF and get into the PERF page LSK# (Left Soft Key on the screen 1 to 6) RSK# ( Right Soft Key on the screen 1 to 6) hope this helps

known by the developers already. there are several posts about texture issues already. example

yes, as long as both are only for you, not sharing your license to a friend or family member to use it twice by different people.

yes we know, but he did edit his original post and removed his crash report. We were discussing about real terra haze not working (RTH lua script)

lua uses -privte- xplane art controls which changed for 10.50 thus being incompatible at the moment. the lua developer has to contact laminar for a workaround.

FlyWithLua Error: The DataRef "sim/private/controls/skyc/sky_imm_end" does not exist. this line means to me you installed xplane 10.50beta isn't it? which is not supported by lua by the way

just the latest. when you copy/paste the code be sure you are not inserting a blank space at the end, this is quite common during paste, remove the blank space before proceeding.

yes and no! climb & maintain XXX states to initiate an unrestricted climb to XXX (any altitude restriction from your present altitude up to XXX gets delered) which doesn't mean you can violate speed restrictions that may exist on the procedure! if there is no speed restriction you can climb FLCH at no problem, but VNAV will still take care of speed restrictions for you. You may still climb FLCH but you must also keep accommodating speed restriction on the MCP SPD dial if any!

you go to the fmc climb page and delete the altitude restriction there. press DELETE and press the corresponding soft key on the fmc screen edit: it is also quite important you reset the mcp alt to authorized altitude, otherwise mcp alt acts as a fence and the aircraft won't climb beyond that.