mmerelles

Steve If you are flying VNAV / LNAV engaged and you change vertical mode by pressing V/S or FLCH for descending, LNAV should remain engaged and the the aircraft should remain following the magenta. If the aircraft stopped following the magenta while you engaged another vertical mode, something else happened unnoticed. If you see this behaviour again please capture and attach here a few screen captures of your forward cockpit to see what FMA a/p modes are telling, what the displays are telling, what the fmc is showing for diagnosing.

you should share the info if you want help. You use external hardware, without any log or info i would bet they are interfering with the electricity somehow. For the required AC for the displays or dimmers. Without any sharing from your side i would recommend you disconnect all your external hardware from the computer and plugins and confirm the aircraft is back fully operative and continue from there.

please attach your xplane log.txt and a few screen captures of the overhead and forward panel

the home page link works just fine to me. Anyway, the full link for direct download is http://ruscenery.x-air.ru/files/RuScenery.zip hope this helps

when you fully retract your flaps to 0 via key command and they jump back to something this tipically means: 1. Your axis lever and/or potentiometer is having dust and it can not reach minimum travel readings. 2. Your potentiometer is bad, it never reads 0 it is always sending signal as being certain % of the travel 3. You have an uncalibrated axis/driver issue? If you have a proper calibrated axis lever and a properly working potentiometer you should be able to have full travel under xplane calibration menu. EDIT: The axis flap detent script: If you have a fully working axis lever ranging from 0 to 100%. The script creates virtual detents as per the aircraft model so when you move your flap lever you have ranges % of detents not to be required to keep fine tuning the axis travel to get desired flap setting.

check you did not enable "cinema verite' by accident under xplane views menu.

try this for your flap axis lever, ixeg compatible http://forums.x-plane.org/index.php?/files/file/30886-flap-axis-detent/

go to www.x-aviation.com, then login, then go to ´my account´ and re-download the installer. It will install latest version 1.0.7

Cruise optimal & maximum altitude should change as flight progresses and the aircraft comes lighter. It always worked and working for me. XP10.51 IXEG 1.0.7 maybe XP11 thing?

how to read altitudes on the legs page: XXXXXA (the aircraft must cross the waypoint at XXXXX or ABOVE that altitude XXXXXB (the aircraft must cross the waypoint at XXXXX or BELOW that altitude XXXXX (standard size not bold) estimated altitude computed by VNAV given your flight parameters XXXXX in bold (user entered manually or procedure mandatory entered means the aircraft MUST cross at that altitude, not any higher not any lower. hope this helps

Given your explanation maybe their internal tools detected your key was shared/distributed which violates the license terms and constitutes serious stuff. Nobody here on the forums can know/help on that, this is just a mere assumption on my side and could be wrong. If you got nothing to hide, nothing to worry then, it will be addressed.

did you send an email to 'support@x-aviation.com'? you should receive an automatic reply back including your ticket # which confirms you entered the queue and it should take 3 business days max for a reply. do not resend the email or you will be queued again and start over.

yes and all custom commands and datarefs available are documented under the aircraft documentation folder, file '2-interface guide.pdf'

all required datarefs and custom commands are documented on the aircraft documentation folder under the file '2-interface guide.pdf'. It is very helpful also to install xplane plugin dataref editor (free) to monitor, edit the different datarefs values for throubleshooting, testing purposes. Will help you to speed up the process. hope this helps

Airfmc is ixeg 733 compatible as stated on their web page. There are also a number of people posting time to time on this forum group running it.

i do not know the formula you are trying to get, but any correction formula that does not include aircraft air speed will be incorrect. The amount of correction to stay on track requires wind intensity and wind direction BUT ALSO the aircraft airspeed. The slower the aircraft is flying the more correction that will be required not to deviate from desired trajectory.

did you try removing flywithlua RTH (real terra haze)? in your video i see it active and this is the type of things coming from rth. go to xplane 10/resources/plugins/flywithlua/scripts/ and remove all scripts held here to a temp directory for testing purposes.

xplane does not support flap detents for jets, it does not support nullzone for flaps axis either so far to counteract desktop grade hardware noisy potentiometers. Your tq6 flap axis is sending noise signals all the time so the flaps does not fully retract and if it does they may deploy from nowhere. When flaps are deployed A/T reduces maximum speed not to rip them. Best stable solution so far on xplabe is to use buttons instead of keys for flap axis until xplane offers better support for detents, nullzone, etc. You can also try a free lua plugin http://forums.x-plane.org/index.php?/files/file/30886-flap-axis-detent/

you need to use the aircraft custom commands and datarefs provided by the developers. The list of custom commands and the list of datarefs is over the aircraft root documentation folder. '2-interface guide.pdf' To make the strobe light work via external hardware set a 1 to ON or a 0 to OFF to the aircraft dataref 'ixeg/733/lighting/strobe_lt_act'

All the inflrmation is on the aircraft doc folder, there is a pdf having the list of datarers and custom commands i do use external hardware myself. Some people doesnt even read the documentation, just complain first

please attach your xplane log.txt file found on your xplane root folder. it seems to me your aircraft is not properly installed and gizmo plugin is not running. Or you may be running sierra os if mac. but just speculating potential problems, we need to see your log file for an educated response. note: your attitude is not right my friend. just demising others job and you do not provide any information to get support is a bit absurd, it could be also your fault. Sounds to me you have a bad day.

That is pretty old stuff. there is no issue as far as i know. i do use the 737 daily.

attach a screen capture of your cockpit to see what the display screen says. as per your description, sounds to me if use a joystick/yoke and the potentiometers are sending noise, go to the igex menu and set the cws slider all the way to the right.

did them not say the VA interface was just right and tested as is? hahaha, liars! we saw their programming was wrong on the vainterface.exe binary. anyway, this is great news to know they fixed the issue based on your perseverance guys. Enjoy your hardware

do not remember, but just move the mouse all the way to the left side of the screen until the end, a ixeg popup will arise, go to preferences and set there. 50 tons in metric is +100k pounds. so this is a difference when entering valid data to the fmc. If you are metric and try to enter a large pounds load it will not accept it. if metric/pounds issue still does not fix your problem please attach some screen captures to see what is going on