Babbo

Sorry, but I can't get this out of my head, the trouble is massive. To outline, what I cannot understand: if, according to you, AMD is the only and exclusive reason why these GTN don't work in the Islanders, then why do they work very well for all my other aircraft, same GTN-version and same AMD-Adrenalin-driver provided - you don't see a logical contradiction here? Absolutely no offense, but I'd be really interested in what you're reasoning here!

Had a discussion. Reality-XP developers (GTN 750 and 650) argued that there could be connections to an, maybe, not up-to-date SASL-version used within your aircraft. Could that be an idea to pursue?

Your reply unfortunately doesn’t answer my question, at least it is clear and apparently final. A sad story. Thanks, anyway.

Ehm, ... and this means what for the two non-working Islander-cases: what would Torquesim have to do, what can I do to get the GTNs running without flickering, ... "add" a Lua-interpreter? (Implementing Lua-things can't be an AMD-task ...) Also, about rendering ... can one / should one display gauges without or with rendering? Sorry, your answer comes a little bit too aggregated, ... and in no ways I'm an expert!

Thanks, Coop, for your response ... but then, what's the reason that both GTNs do not flicker with other planes?

Dear all, please allow another flickering thread, since the problem is more specific: my whole BN-2B shows rock-stable visuals, only both RealityXP-GTNs (750 and 650) suffer from nervous flickering. Again, it is an AMD-card under Vulkan, but this GTN-flickering does not occur with other planes than BN-2B and btw. BN-2T. Consequently, there must be a link between that problem and the way those GTNs are implemented within the Islanders. For the stats: OS (Win10pro), AMD's Adrenalin driver (and hardware), X-Plane, RealityXPs and of course your Islanders, everything is up to date. Also - not to forget - love your Islanders! Many thanks for any help.

Right, if you mean Prop coarse/fine a bit, this is already mapped by default to F3/4 - and it works nicely. However, it appears that detent-functionality then is ignored.

Thanks a lot for your update! ... and a question: condition levers now can be mapped to keys?

... anyway, I tried it. So we may discuss the following script - for me it's running fine: local CL_time CL_DRef = "LES/saab/CL/manip_common" create_command("FlyWithLua/LES/Saab/CL_increase", "Move condtion lever towards Max", "CL_time = os.clock() + .1\nset(CL_DRef, get(CL_DRef) + .01)\nset(CL_DRef, math.min(get(CL_DRef),1))", "if os.clock() > CL_time then\nset(CL_DRef, (get(CL_DRef) + (os.clock() - CL_time) * .05))\nend\nset(CL_DRef, math.min(get(CL_DRef),1))", "") create_command("FlyWithLua/LES/Saab/CL_decrease", "Move condtion lever towards Min", "CL_time = os.clock() + .1\nset(CL_DRef, get(CL_DRef) - .01)\nset(CL_DRef, math.max(get(CL_DRef),0))", "if os.clock() > CL_time then\nset(CL_DRef, (get(CL_DRef) - (os.clock() - CL_time) * .05))\nend\nset(CL_DRef, math.max(get(CL_DRef),0))", "")

Hello all! Please accept excuses for bumping a frequently stressed theme. I've searched up and down the net, but was not able to find an answer to the following question: how to map a keyboard key to jointly move both condition levers? (I.e. not a quadrant, not a joystick, not the mouse - just the keyboard, precisely, two keys for both directions.) Thanks a lot for any input!

Thank you, I would never have had that idea. - Is there a way to disengage this licensing window (since it isn't needed)?

Firstly, have my greatest thanks for your gift, but secondly, I can't license your product: correct entries (email and pwd) always fail! Could you please offer some help?