mgeiss

Thanks, good to hear, credit card is ready!

Just wanted to ask if you guys plan to support XP11 after XP12 gets out of early access or will further updates of the 650 be XP12 only from that point on? In my experience, XP versions are a moving target until pretty much the last revisions, so I usually avoid updating till X.40 or so

Yeah, I'm seeing the same on my end. The X-Pilot.com and X-Aviation.com sites are running fine with my usual internet speed, but the installer's download rates are well below 10 KB/s since a few weeks.

On many Boeings you can hear a click-like sound when the lock for the landing gear lever disengages. It prevents the lever from being moved to the "UP" position before getting airborne. I don't know if it's the same for the classic, but it's quite possible. Need to watch some cockpit videos...

I don't know why it doesn't work for you, the script is running fine on my end. However, it doesn't trigger the lever animation, so here's the complete version which set's the mixture and also moves the lever in the virtual cockpit. Of course you need to change the button numbers to match your hardware: -- Engine 1 cutoff switch create_switch(15, "sim/flightmodel/engine/ENGN_mixt", 0, 1, 0) create_switch(15, "ixeg/733/fuel/fuel_start_lever1_act", 0, 1, 0) -- Engine 2 cutoff switch create_switch(17, "sim/flightmodel/engine/ENGN_mixt", 1, 1, 0) create_switch(17, "ixeg/733/fuel/fuel_start_lever2_act", 0, 1, 0) Maybe it's a copy&paste problem with the forum code function, so I have also attached my script (again, using my button numers that you need to change). cutoff.lua

It's just the single number so 10 in your example.

You don't need the ICAO to make a FWL-script aircraft dependent, as you can use the .acf name instead: Just use if AIRCRAFT_FILENAME == "name_of_acf.acf" Instead of if PLANE_ICAO == "ABCD" This also helps when you want to restrict a script to one addon if you have more than one variant of a plane which share a common ICAO code (e.g. several C172 addons).

Should work, but I can't test atm, not at my sim machine. You just need to replace XYZ and ABC with the button numbers of your cutoff switches, which can be determined by running the "Show joystick button numbers"-script from FlyWithLua's menu. -- Engine 1 cutoff switch create_switch(XYZ, "sim/flightmodel/engine/ENGN_mixt", 0, 1, 0) -- Engine 2 cutoff switch create_switch(ABC, "sim/flightmodel/engine/ENGN_mixt", 1, 1, 0) The logic behind that command is (button number, DataRef name, array index, value when button is released, value when button is pressed)

I'm supprised there is no word about it here yet. Or the search function didn't find it. Anyway... https://www.thresholdx.net/news/hscl65

If you use the X-Plane command "toggle thrust reversers", you can do just that. With your throttles at idle, you push that button and the plane goes into idle reverse. Your hardware thrust lever now acts as a reverese thrust control i.e. adding reverse thrust as you move the lever forward.

Thank you, this dispels my concerns!

Congrats to the team for this outstanding addon! Will definitely get it if my system can handle it. It seems to have many features which need a lot of CPU power, so I'm wondering if this will run fine (i.e. 30+fps) on a quad core? I'm using a 4790K @4,4GHz and my X-Plane settings are generally in the medium to high range, nothing maxed out. Reflections are turned down to minimum.

It's been a while, but i think... 1.) Enter a new destination on the route page 2.) Just select the new runway and STAR on the DEP/ARR page. It should replace the old one(s) more or less seamlessly. But check the legs page afterwords nonetheless 3.) Go to the legs page, downselect the waypoint to which you want a direct to by pressing the LSK next to it, upselect it to the current "to" waypoint by pressing the LSK next to it (overwriting the current "to" waypoint")

Good question, maybe some of the real world saab drivers can shed some light on this. I just start and stop in a parking spot where no pushback is necessary, that's how I usually find the turboprops sitting at airports. Passengers are brought to the plane via bus or just walk there (depending on the country and size of the airport).

Maybe opening a support ticket will get ignored work. https://support.projectfly.co.uk/tickets/create

We discussed that issue in the topic below. It seems to only occur with newer versions of XPUIPC.

Not on SIDs or STARs, but you'll find them on most approaches in the US. The stepdown- or PT/hold-altitudes will more often than not include altitudes bewteen whole thousands.

This has nothing to do with VFR. There are more than enough altitude restrictions for departures/approaches which command leveling off at some "odd" altitudes like e.g. 5600ft. Or say you are flying in russia, there you would even need to select altitudes in 10 feet increments in order to exactly follow the charts. I don't use the mouse wheel option but highly prefer click & drag, which is also faster in most cases.

You could try to change the plane's ICAO code in the .acf file, could be that Smartcars is looking for that rather than the folder name. 1.) make a copy of the IXEG's .acf file and rename it e.g. by changing the file extension to .bak 2.) open the .acf file in a text editor and search for the line that begins with P acf/_ICAO 3.) change the ICAO code to B737 4.) save the file

Iain already gave an elaborate answer, but here is a tl;dr of how I do descents depending on the situation: LVL CHG when I just can get down to the next altitude without needing to obey any restrictions on the way. E.g. when ATC says "descent and maintain XYZ". V/S when I want to reach the next altitude at a given point. E.g. when approaching an altitude restricion on a STAR or when ATC says "cross ABCDE at and maintain XYZ". V/S can also come in handy when there is a speed restriction coming along the way. E.g. you are going to descent through 10000ft and you want to keep descending at a reasonable rate while also needing bleed off speed, you could dial in -1000 ft/min and 250knots. When the plane has slowed down to 250, you could then switch over to LVL CHG to expedite the descent.

Hallo Jan, danke für die Klarstellung!

Fuel still get's drawn from the tanks with the pumps off. IIRC you can even start the engines (and fly) with all fuel pumps off, as fuel is feeded to them by gravity. The fuel pumps are needed to ensure positive pressure under all flight conditions.

You need to activate nose wheel steering by using the corresponding pushbutton on the tiller.

Seems that the problem is only present with the latest (or later) version(s) of XPUIPC. Here a user was able to resolve it by reverting to the initial 2.0.0.0 release: http://forums.x-pilot.com/forums/topic/14345-assigned-throttle-axes-dont-work/ Although the author's site seems to be down or under construction, there's an archived version available: https://web.archive.org/web/20171109165154/http://www.tosi-online.de/XPUIPC/XPUIPC.html

Keep in mind that X-Plane 11 allows for aircraft-specific input profiles. It could be that you have accidentally assigned a profile to the IXEG which has no (or an incorrect) mapping of the throttle axis. Can you check if there are any profiles other than the default and if one of them is assigned to the IXEG? However, deleting the prefs should have taken care of this. But who knows...