mmerelles

This is great news Keith!

The flashlight is an xplane feature that works to any aircraft. you activate it on the view menu, toggle flashlight note: your simulator must be on HDR rendering mode or it wont be available hope this helps

I have seen this behavior too. To me this is due to the VNAV fine tuning still required and the developers being working on. If you want to make sure you are on this category and not a special case not considered, you should provide more detail for them being able to reproduce it. -Entire flight plan (departure airport, runway, sid, route, star, approach, runway, airport) -Airac cycle you use -Performance data entered on the FMC, cruise alt, ci, etc. EDIT: forgot to mention, if you are running 1.0.7 the FMC leaves a file on the aircraft root folder that contains all necessary information for the developers. Attach it!

Real Terra Haze is still available (but not supported by the developer as long as i understand). There are some modifications you need to perform on the script to make it compatible to 10.50. There are youtube videos, lot of tutorial how to make those simple changes. http://forums.x-plane.org/index.php?/files/file/33659-real-terra-haze-for-flywithlua-rth/ There is also another new project you may be interested in which seems very promising and even more advanced than RTH. You can follow it here. http://www.avsim.com/topic/494912-ventura-sky-beta-3-is-here-for-everyone-to-try/ hope this helps

can you please attach (not copy/paste) your log.txt file found on your xplane root folder to see if something comes up there?

most common software people use to make a livery is Photoshop (paid) or GIMP (free). There are several youtube tutorial videos, search there something like "how to paint a livery gimp" or "how to paint a livery photoshop". It takes lot of time, patience, experimentation and persistence to understand and learn to make, specially if you are unfamiliar to image editing tools.

Again, this is not a dataref. A dataref is a memory position, a variable, were you can read and/or write values. A custom command is an order, a command. When you trigger it, it does something pre-programmed. You can not read or write anything. If you map a custom command as if you were treating a dataref it wont work!!!

I am not saying ixeg/733/FMC/cdu1_del (delete) i am saying ixeg/733/FMC/cdu1_clr (clear) I just went to joystick & assignment for testing purposes, assigned a key to ixeg/733/FMC/cdu1_clr and it works flawlessly, each key push clears a character on the scratchpad. Remember also this is a custom command NOT a dataref as you call it above which makes a difference. Datarefs (memory positions) are a whole different thing

I did not test because i have no remote cdu hardware. But got these from the included documentation: ixeg/733/FMC/cdu1_clr ixeg/733/FMC/cdu2_clr have you tried them? not working?

hope this helps for you to start moving.

I noticed this too. But, no smoke during landings or not smoking during replays? i did not attempt any auto land yet to compare if smoke is missing always or just replays.

@Cjones97 1. this is because just right side of the CTOT switches you have knob DIAL for selecting the mount of thrust and seems you have it a bit low, Increase it. 95% should be fine for most standard takeoffs. or 2. The Condition Levers are overshooting the MAX position, do not move them to full forward. There is a MAX detent previous to full forward. Is hard to tell whether is problem 1 or 2 as per the camera angle, most likely problem 2

you should attach your log.txt (not copy/paste, attach)

All users i have seen that experienced massive FPS performance loss from nowhere on the past few days, removed windows update KB3176938 and fixed their problem. This windows update is certainly causing problems to a lot of people. Once removed performance is rock solid back. I can not tell whether this Microsoft update is buggy or it makes a laminar issue come alive. But reality is you remove it, and problem is fixed.

I am not expert here just trying to help. Document provided withing /xplane 10/instructions/sending data to xplane.rtf provides the information how to set a dataref / how to read back. To my understanding sending/reading via UDP is not related to the IXEG or any particular bird. This is how you interact with xplane and xplane should allow you to manipulate set/read any dataref or other plane commands/features.

1.0.7 is latest version available. you are just fine.

As per your log you have several problems here: 1. You are running RTH (Real Terra Haze). This script for flywithlua works for xplane 10.45 but is not compatible to xplane 10.50. The developer no longer supports it. Remove all RTHxxxxx.lua scripts from you flywithlua scripts folder to stop xplane crashing. There are some guys who figured out how to modify the scripts to make it work, you can try that. I strongly suggest you to remove RTH scripts first and have xplane stable again before adventuring to modify scripts. 2. KSFO (San Francisco) scenery you installed requires some libraries to be installed as well specified on the instructions. As per your log xplane is showing you a screen pop up to warn you KSFO may not look correct. xplane is complaining that some autogate jet-steel objects are missing. So, you have not installed required libraries or they are installed but outdated. 3. plugin FJCC_x737FMC is having tons of problems. You should remove this plugin until you have a stable xplane working before putting more stuff into the mix of issues you have. Non of your issues are related to the ixeg 733 itself

the one which seems to really matter is KB3176938, so uninstall it and report how it goes.

maybe you are one of a lot of people experienced poor performance from nowhere during the past days, now being known to be caused by a recent windows 10 update? If so, uninstall it and you should be fine. Check here, there are already several other posts all around the same. http://forums.x-plane.org/index.php?/forums/topic/107128-answered-performance-issues-maybe-due-to-1050-rc3-no-windows-update/

ok i see. This is my understanding of the situation. 1. You are in VNAV PATH mode, you are also experiencing tailwind which will push the aircraft forward more than anticipated for the FMC calculated descend, this means the aircraft will be prone to overspeeding during descend. You as the pilot in command should account for this situation and do proper planning. Maybe switching to VS or FLCH. 2. As soon as your video starts you are already on A/T ARM (armed) mode, look at the display were the artificial horizon is, top left corner of the display. It says ARM in white letters. This means the aircraft is overspeeding the target speed (your target speed is 210 knots and you are 233 knots), A/T goes fully retarded and enters ARM mode awaiting for the aircraft to reduce speed for applying throttle back automatically when required to maintain target speed. While the aircraft is in retarded-arm mode it will not apply more thrust by itself, it makes things even worst! Quite smart system. 3. At 00:53 you decide to turn off the rebel A/T entirely by flipping the A/T switch, then you reengage A/T then you re-engage VNAV But if you look closely your displays, you engage everything back A/T + VNAV and A/T goes FMC SPEED MODE, but immediately it senses you are overspeeding the target speed and A/T goes back to ARM mode, video ends. So, you are basically back to the video starting point I am unsure what you are trying to do here, the aircraft is behaving properly. -The aircraft will not command more thrust, you are overspeeding already -You may switch to FLCH or VS and command thrust manually or via SPEED dial. hope this helps

A/P disconnect: The problem using the yoke button is you have to rotate the camera down while you are aligned to the runway for landing and this could be distracting. On real life this is not a problem, because you are feeling the button with your thumb, no need to look at it for pushing it My advice would be you map any button of your yoke (if you own one), or any key on the keyboard of your liking to the A/P disconnect button. So you can mimic you are pressing the yoke button but actually without rotating the camera to clic it with the mouse. If you want to test it, map a button or key to "ixeg/733/autopilot/AP_disengage". Same as on the yoke you need 2 clics to disengage. A/T: I am not sure being understanding your issue. When you are approaching to land, you want to move your hardware lever to regain throttle control but it ignores you? You need to clic A/T DISC first on the throttle levers, then you need to move your hardware lever to sync them with the aircraft lever and the aircraft will go to manual throttle mode. You can also map a key or button for throttle disconnect. You have to map "ixeg/733/autopilot/at_disengage" hope this helps

sounds great! For the saitek radio panel (if you still have it) be sure to install the free xsaitekplugin you do not need any config or fine tuning. Otherwise when turning the dials you may experience some difficult to set desired frequencies easily (by default tends to jump way to fast)

Required datarefs & custom commands are already there and available to anyone. If the virtual avionics CDU is not compatible to the IXEG bird yet it is just about their time frames and priorities not ixeg pending.

i think this is the explanation you are looking for, from the developers

in the settings -> operation & warning menu make sure the number of flight models is 2 or 3. do you start engines running or cold & dark on xplane settings? (try cold & dark so if you have a setting issue the aircraft should not bounce because is off it could be a hardware settings or a plugin conflict if you do not get much help here post on their forum http://forums.x-plane.org/index.php?/forums/forum/104-bell-206-jetranger/&page=1