First off I gotta say that this is a great little tool. The tracer mode makes it so much easier to find Lvars and controls specific to each A/C, loving the tail-like console log too...With the VRI MCP-Combo it's a no brainer, getting rid of the SerialFP2 is great. No more keymaps, conflicts with other apps and their key assigments...Artem and Günter, I'm very sorry that I didn't give it the time it deserved during the Beta process Got a question please. Can we expect to have the MCP knobs & switches available in Mode 2 anytime soon?And can I suggest a "Global Mode switch 1-2-3"? something that wil control the entire panel's mode, not just the EFIS, MCP or User part No big deal really, since there's an easy way around it adding something like this to the common.lua:

function GLOBAL_MODE_one ()    ipc.set("EFISmode", 1)    ipc.set("MCPmode", 1)    ipc.set("USERmode", 1)    ipc.set("GLOBALmode", 1)        local ident = "glo1"     if type (USER3["IDENT"]) == "string" and string.len(USER3["IDENT"]) > 0    then ident = string.sub(USER3["IDENT"], 1, 4)  end        DspShow("GLO1", ident, true, true)end function GLOBAL_MODE_two ()    ipc.set("EFISmode", 2)    ipc.set("MCPmode", 2)    ipc.set("USERmode", 2)    ipc.set("GLOBALmode", 1)        local ident = "glo2"     if type (USER3["IDENT"]) == "string" and string.len(USER3["IDENT"]) > 0    then ident = string.sub(USER3["IDENT"], 1, 4)  end        DspShow("GLO2", ident, true, true)end

and then I can add a function in an aircraft specific module (actions.lua) that I can assign to a knob:

function NGX_AP_SPD_inc ()    mode = ipc.get("GLOBALmode")    if mode == 1 then        ipc.control(70016, 16384)    else        NGX_AUTOBRAKE_inc()    end end

But it would be cool to have all of the knobs & switches in the panel available to Mode 2 & 3 as well, and configurable via GUI Thanks

Dario, In the earlier builds mode switching was global for the whole unit and MCP block had 3 modes for rotaries too. But later we've decided split mode switching to the separate blocks (EFIS/MCP/USER) to make it more flexible and to get rid of alternative modes for MCP rotarties, because we wanted these rotaries ALWAYS (in any case and any mode) to control the AP system. The other reason for such decision was that we cannot fully control MCP display. And if we assign alternative actions to the MCP rotaries, display is still showing it's non-removable SPD/HDG/ALT and numbers are jumping while you rotate knobs. This looks messy (and potentially confusing for user).

Would you consider giving it as an option Artem?I mean the Mode 2 knob operation

Hm... may be. But not earlier, than I'll start the update process for VRinsight MCP2. I'll be reworking LINDA's interface for that and will consider that option.

Hm... may be. But not earlier, than I'll start the update process for VRinsight MCP2. I'll be reworking LINDA's interface for that and will consider that option.

Fair enough. I think It's a pitty to give up so many knobs for the display especially since many A/C don't have an SDK and it doesn't work properly anyway, but it's your decision, of course One more question please. Is there a way to keep the console from opening automaticaly on startup?

I think It's a pitty to give up so many knobs for the display especially since many A/C don't have an SDK and it doesn't work properly anyway, but it's your decision, of course

Now I agree with that. The decisision wasn't the best.

One more question please. Is there a way to keep the console from opening automaticaly on startup?

Console opens automatically only if some error is detected (do you see any red lines there?). Otherwise it will not jump on to you. :-)

Console opens automatically only if some error is detected (do you see any red lines there?). Otherwise it will not jump on to you. :-)

Oh, alright, I thought I could just ignore the errors setting the console's verbose mode to Standard instead of Debug or something, heheYes, I had two errors when trying to stablish a serial connection COM4 - virtual ports (at least I think so)

[E] VRI port 2 "com4" failed to open[E] VRI port 3 "com4" failed to open

Turns out that my FSUIPC4.ini contained too many entries here:

[VRInsight]1=com42=com43=com4

last two attempts failed cause COM4 was open already? Anyway, it's fixed now. Thanks for your help :)

May I suggest two completely expendable things, but that would be nice to have if they are easy to implement? 1.- An option to start minimized to tray2.- An option to close automaticaly when FSX is terminated

1.- An option to start minimized to tray

already implemented: have a look at LINDA setup page: "Minimize to tray"

An option to close automaticaly when FSX is terminated

you can change the FSUIPC.ini section [Programs] to the following:

Run1=CLOSE,F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LINDA.exe

(do not copy that; its a different installation path. But you could easily insert the CLOSE command) Maybe Artem could implement this also one day ...

already implemented: have a look at LINDA setup page: "Minimize to tray" you can change the FSUIPC.ini section [Programs] to the following:

Run1=CLOSE,F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LINDA.exe

(do not copy that; its a different installation path. But you could easily insert the CLOSE command) Maybe Artem could implement this also one day ...

That's perfect. Thanks Güenter

Güenter

that's nearly perfect ;-) Regards, Günter

that's nearly perfect ;-) Regards, Günter

Sorry Günter :(

Thanks guys for bringing back the Mode 2 thingy. Very much appreciated :)