mmerelles

i am interested on this as well. I do have a goflight tqm6adv and do not use the flap lever because xplane does not support flap levers natively and sometimes they do not even fully close inflight and you rip them. but having a lua script to define ranges will surely make them work. can you provide us a script example to tune from as a starting point? thanks!

i move them to min and leave them there, this is a workaround i found to get consistent thrust in beta mode after reverse. In the real thing it doesn't matter. You can taxi having them in max or min because you are in beta mode. turboprops per their engine nature have several seconds lag to respond to throttle adjustment changes (5-6 secs aprox). this make them very inconvenient for taxing and general ground operations. in response, engineers creates beta mode, the throttle range goes from GROUND IDLE to MAX GROUND IDLE (just before you enter FLIGHT IDLE) under beta mode, the engines are held constant by around 1100 rpm by electronics (do not remember the exact value) and moving the throttles within the beta range you are actually only controlling the blade pitch 0 to +10 degree. Being in GND IDLE you have a 0 degree blade pitch no air gets pushed, moving it forward you add blade pitch and air gets pushed. Blade pitch changes are almost instant and rpms are held constant by the electronics watching fuel flow. Thus you get a predictable thrust for ground operations. note: Condition levers MIN to MAX position allow you to set your desired engine RPM for torque vs speed at different passes of flight while the throttles are in the flight range (FLIGHT IDLE and forward)

it happened to me as well. i reported it a long time ago (almost a year) but i was said the aircraft operates just right. This is not correct, i have been many times on a 340 cockpit, a family member is a 340 captain. My workaround is to move the CLs to MIN during braking/reverse, it makes the aircraft get thrust in beta mode after landing. Otherwise the aircraft seems to get stuck on the runway. This problem only happens after reverse/landing. No issues during initial roll when leaving the gate in beta mode.

In my opinion the VNAV is the soul of the fmc, it has so many calculations, variants, considerations. No aircraft available on xplane as of today has a working, solid predictable and realistic VNAV featured FMC. All them fall short on predictions, last minute flight plan changes, etc. I am not blaming developers, we are talking here about an extremely complex piece of software that takes boeing lot of people full time to improve and develop for decades and they never stop.

this is a configuration file for plugin xjoymap which allows to bind your condition levers to your hardware levers without using the saab custom menu every time you load the aircraft. 0.50 means moving the lever down (closed) it will no go further than 50% of its travel which is MIN position 0.90 means moving it forward (open) it will no go further than 90% of its travel which is MAX position not to overshoot. i do use this plugin but i set them to 0 and 1 respectively to have the full CLs travel as being on the real thing. edit: forgot to mention in this file they are mapping one external hardware lever to both CLs, so you move them simultaneously, no individual control per CL. Anyway, your CLs should work properly without xjoymap, i put this plugin later on down the road when i got tired of assigning them each time i loaded the aircraft. Not because i had any range travel issue

i would recommend "simbrief" -its is free -you can select the aircraft, model, passengers cargo and it will make all calculations based on that -you can provide alternate airport, reserves, etc. or leave them auto for suggestion -you can select the AIRAC cycle you have running and provided route will be supported. -you can save flight for further edit/use -it provides weather, notams, etc.

Yes you can reinstall the 777, just delete the entire 777 folder. Download the aircraft again (or decompress 777 .zip file if you still have it) and put it on the aircrafts folder again. On first launch you will be required to re-enter the activation key. Can not imagine how reinstalling xplane or the 777 will fix something. If you have a plugin or a configuration issue it will pop-up again sooner or later. i would better recommend you share more details about your problems to understand and fix them.

you are doing a superb job with this simulation! excellent!

glad to hear you got it up on the skies nicely unable vref speeds background: yes, i forgot to mention my fault. because this aircraft was meant for very loooong trips and heavy loads (pax, fuel, cargo) the engines are extremely powerful. When you configure the bird for a very short trip you need to derate (remove thrust) the engines considerably so the FMC can computate a safe takeoff. To derate your engines you have pre-programmd profiles under the takeoff fmc page. derate as much as required. This will limit engine thrust during takeoff. You can also derate the engines by cheating the FMC introducing an extremely hot temp above current conditions.

this time you was entering a wrong route which leads into a 10000 NM trip and insufficient fuel arises as MGEISS pointed out. No, now you shared your route i see your trip ESSA to EFHK is 221 NM only. See it here https://skyvector.com/?ll=60.097992270051215,21.298645022262377&chart=304&zoom=4&fpl=M082%20ESSA%20NTL%20UXETI%20LAKUT%20EFHK this is an extremely short flight for this bird meant for 4000 NM to 6000 NM trips average. if you load the FMC with a 221 NM trip and you put fuel for a 4000 NM trip the aircraft will be SO HEAVY that it will take your entire trip distance just to reach cruising altitude, so the FMC is unable to compute a valid VANV profile. Putting also a CI (cost index) of 20 which is very restrictive on engine thrust will make things even worst. so, if you are trying to make this flight happen, you should enter 12k kg of fuel aprox and a cruising alt of 270 should work. I am not at the sim know to give you a tested profile.

My fear is if you tried FL280 and the FMC said "unable cruiz alt" this is most likely due to a short flight, but a very fuel loaded (weight) bird, the FMC was complaining unable to make a valid VNAV profile for such a trip. You are also entering a low fuel conservative CI which means restricted thrust (aircraft takes longer to climb) if you share your complete route i can double check instead of guessing and speculating what it could be.

42k kgs of fuel is given for a +4hs of trip, your cruising ALT FL200 doesn't make sense at all. can you share me your entire route? sid, trasition, rouute, star, trasition landing runway? something does not match on your parameters and the FMC is judging it will not make it. all of your waypoints have no vnav information populated (speed/alt), the fmc can not calculate a valid profile a few side tips: -you have to set the HDG knob to runway heading prior to departure -if you do not have fuel on the center tanks do not activate center fuel pumps on the overhead panel, you have an alarm trying to suction fuel from a dry tank (fuel low center) -the speed dial should be set to V2 speed given by the fmc when you set takeoff parameters prior to departure. This is the safe climb out speed in case something goes wrong. -edit: also your doors are not set to auto, you have an alarm too

i forgot to mention if you are in vnav mode lets say cruising at FL340 and the FMC suggest a step climb to FL380 or you want to climb to FL360 or whatever, just rotate the MCP to your desired new target altitude and clic/push the altitude knob as well. This will let the FMC know you do require a new higher cruising altitude and initiate the climb to level off at desired target altitude. This will not work to reduce your cruize level since this was not simulated by the developers.

HDG: push the HDG knob to enter in HDG mode. Rotate the HDG knob left or right to your desired HDG heading, you can set max lean angle on the back part of the knob, default is auto. Once you are on HDG mode, rotating the knob will make the aircraft to turn immediately, you are already in hdg mode. ALTITUDE: you have two options. -VS (vertical speed mode) set your target altitude on the MCP (higher or lower) push VS button on the MCP. The vert speed display will illuminate. Rotate the VS wheel dial up or down to set your desired climb or descend rate. Once the aircraft reaches your MCP alt it will enter in ALT HOLD mode and will maintain such altitude. -FLCH (flight level change) set your target altitude on the MCP press FLCH button if you target altitude configured on the MCP is higher (a climb) A/T will enter in climb thrust mode as configured on the FMC until reaching desired altitude. if your target altitude is lower (a descend) the A/T will enter in IDLE mode and set nose down as required to maintain present air speed. To maintain present speed being at IDLE it will put the nose down as much as necessary. So the rate of descend will vary based on your current speed and altitude. note: VS mode will gurantee a specific rate of climb or descent in ft/sec as configured on the vs display. FLCH mode will keep varying rate as required to maintain IAS during the process. hope this helps

This is very exciting news. not sure if anyone in the team can beta test it on PILOTEDGE or similar which tries to mimic how real aircraft are managed. It seems to me other airliners were not tested under dynamic conditions and as soon as you put them to work and make changes/decisions inflight all kind of problem/bugs and limitations arises. They seems only to work under a non-chaning pre-programed standard flight. on a side note: would you be able to send 2 radios simultaneously to the speakers? i.e. having tuned approach freq. on radio1 and atis on radio2 for listening weather reports while keeping track of ATC traffic comms? thanks!!

mmmm what this means.... jejejeje

according to your log file you have installed an HD custom mesh which is incomplete and causing the error /zzz_uhd_global_scenery1/ move this folder out of your custom scenery folder not to load it and try again if it works. EDIT: also note that alpilot ultra hd meshes requires 10.25 and later mandatory!!! requirements here http://www.alpilotx.net/downloads/x-plane-10-uhd-mesh-scenery-v1/

according to your log file you have installed an HD custom mesh which is incomplete and causing the error /zzz_uhd_global_scenery1/ move this folder out of your custom scenery folder not to load it and try again if it works. EDIT: also note that alpilot ultra hd meshes requires 10.25 and later mandatory!!! requirements here http://www.alpilotx.net/downloads/x-plane-10-uhd-mesh-scenery-v1/

OMG this is serious stuff from IXEG :D

in Argentina they do taxi back to gate single engine configuration. My brother in law is a 340 captain. Being myself many times on the cockpit. Most airlines worldwide use dual engine taxi configuration procedure, BUT you may loose an engine inflight and the saab is perfectly capable to land and taxi back to the platform on a single engine configuration. Which is not the case on the sim. Hopefully this is not that hard to get fixed. no speculating here. there you go:

I am also interested on this, while landing on a single engine is imposible to taxi, the aircraft will simply circle around. LES team: are you planing to fix this? or what are your comments about this?

ok i reviewed carefully your steps again and got your point. It is too late now going bed, but i will test it tomorrow morning to see if i can replicate your behavior and report back my findings.

orgasmic!!! :D :D

Hi Martin I am not quite sure i am understanding your problem. I do have a Goflight GF-TQ6-ADV quadrant, not the same model than yours, but i am not experiencing any problem with the saab. I will share you my experience. When you start xplane and you load the saab340 having your goflight hardware throttle levers fully closed/retarded, the saab 340 doesn't know what your actual hardware levers positions are. The saab340 will configure its throttle levers at ground idle as supposed to be encountered upon entering the cockpit in the real thing. BUT your hardware levers are fully retarted/closed, which means they are actually physically on the max reverse position, low end of its travel. You already have a SYNC issue which is ok, the saab has its throttle levers set at ground idle, but your hardware levers is fully retarded in the MIN position 0.0 of its travel, but neither the saab or xplane knows about it until you move them physically for the first time which will send a signal to the simulator about its position for the saab/xplane to pickup. I.E. assuming your hardware levers are in fully closed/retarded position (0.0) when loading xplane/saab340: As soon as you move them tiny bit (any or both levers) xplane/saab knows they are at 0.0, which means low end travel MAX REVERSE position and the saab will jump its throttle levers back to sync them with your hardware actual position. Now they are in sync, you have to move your hardware levers forward by 15% aprox until you reach ground idle and you are all set. is that what you are experiencing?

for climb is best and safer to use IAS mode, you select your desired climb speed rotating the speed bug and the AP will accommodate the VS rate continuously to guarantee your desired IAS speed during the entire climb. The higher you go the lower the VS rate would result to maintain the speed. It is a bad idea to use VS for climbs abobe 10000, because in this mode the aircraft AP will guarantee the ascend rate and the IAS will drop rapidly while climbing, the IAS will also vary a lot based on existing weather conditions (temp/winds/pressure). As consequence climbing in VS will result in constant manual intervention or you risk to stall the aircraft. I would advice to use IAS mode to climb except for initial after takeoff CLIMB mode.