If I buy, can I edit the plugin?

[PeterStorm]

Hello!

I was just wondering, if I buy the plugin, if I can edit the datarefs to fit my needs? Also is it using XUIPC?

[mvr1918]

OC4BA_XP do not use XUIPC. It is a C++ driver using its own code logic for handling the airplanes Datarefs and Commands.

Not sure what you mean with "edit the datarefs to fit my needs"?

You can edit input/output/display connection number to fit your specific OC built hardware.

What airplane are you going to use it with?

An update of OC4BA_XP will be release later today or tomorrow.

It will support:
MCP, EFIS1, EFIS2, COM1,COM2,NAV1,NAV2 and ATC for the Laminar B738 / Zibo version.

[PeterStorm]

I explained myself rather poorly.

I mean, could I for example start working on getting the OpenCockpit stuff working on the FF 757? Like would it find the data refs on that plane, and would I then be able to map functions?

And when you say NAV2, you mean a second module or the second frequency on the NAV module?

Thank you for your answer and your work

[mvr1918]

FF757 is not supported now.

If you provide a list of FF757 datarefs for MCP, EFIS1, EFIS2, COM1, COM2, NAV1, NAV2, ATC
I can have look. But, no promise.

With NAV1 I mean the hardware unit.

[PeterStorm]

FF757 is not supported now.

If you provide a list of FF757 datarefs for MCP, EFIS1, EFIS2, COM1, COM2, NAV1, NAV2, ATC
I can have look. But, no promise.

With NAV1 I mean the hardware unit.

Ok, I guess that’s the question. Is there an interface so I can start doing the work myself, or can you only load preset profiles in your program? Like Spad.next you can make your own profiles and upload them, but they unfortunately do not support OpenCockpit stuff yet.