No MCP hardware & EXEC light not working

[ApacheHunter]

Both the manual and readme of v2 clearly state: "When flying in your home cockpit and you don't have any hardware for the OVH panel, you MUST push the MCP C/O button to initiate
your modules windows." But what if I don't have an OVH panel and an MCP? I only have an FMC v3.

Also, the EXEC, DSPY, FAIL, MSG and OFST lights of my FMC v3 don't work with OC4BA v2, whereas they did work with the free version of the software.

Can you please help me?


EDIT
And another small thing: when I push the CLR button the whole scratchpad gets cleared, instead of only one letter. Is this normal? The earlier versions of OC4BA also had this behaviour. I'm just asking; it's not a real nuisance.

[mvr1918]

As you don't have the MCP , you can't initiate the OCP4NGX with the CO button.

Here is what you do inntil a new update for userr without MCP:

Start sioc.exe from sioc folder
Go to edit script in the sioc window
Find the script line with variable 2800 in the beginning of the script ( this is the variable that gets a 1 when MCP CO button is pressed)
Double click that line and insert initial value to 1
Save
Close sioc.exe

I will make an updated script when back In office tomorrow.

The CLR issue will also be looks into and corrected If not OK








Rgs Roar

[mvr1918]

Hi,

See Download page for updated script to be used when MCP is not in Cockpit

An update for a minor CLR issue will be corrected later

[ApacheHunter]

Excuse me for my late reply.

Thanks a lot for trying to help me, but unfortunately the new special script renders my whole FMC v3 unit unusable. I'm now using the original script with the modification you provided, which works perfectly.