re-use macro files

[crashdog]

Hello,

I was just wondering if it's possible to send some one a macro file to be reused that I made.

If that other person has the same aircraft model and same fsuipc version should that work ?

I had experianced earlier that when I installed a patch to my aircraft model that the macro file had to be made completely from scratch again.

Is that because the vendor has changes the panels and the addresses are then different or does fsuipc in general not know how to "link" to the updated aircraft ? I guess that since the .gau file is mentioned in a macro file that fsuipc will just check for the gauge file to exist or is there any versioning involved ?

Kind Regards,

Gery

[guenseli]

I was just wondering if it's possible to send some one a macro file to be reused that I made.

If that other person has the same aircraft model and same fsuipc version should that work ?

should be no problem. Same or better said latest version of FSUIPC is recommended!

I had experianced earlier that when I installed a patch to my aircraft model that the macro file had to be made completely from scratch again.

Yes, some developers change their codes with updates, e.g. F1 Cessna Mustang.

Don't ask me why this happens, other could do updates without changing the codes.

Its not a missing link, the numbers change.

If you create a mouse macro, then you will notice a numver in the upcoming FSUIPC message window, like "X1c740*Xa1cc".

There will change mostly two numbers ( I think it has sth to do with hexdecimal system)

The only solution is to redo all the work again...

regards,

guenter

[Pete Dowson]

I was just wondering if it's possible to send some one a macro file to be reused that I made.

If that other person has the same aircraft model and same fsuipc version should that work ?

The version of FSUIPC should not matter, except that I only support the current versions.

The version of the aircraft model can be critical however. The mouse macros work by making calls directly into the code in the Gauges of the aircraft. If that code is changed, the places in the code will almost inevitably change. They may even change just by recompiling with an updated compiler, because of optimisations.

If the macro code lines, the first hex number is the offset to the entry point in the Gauge, and the second hex number is a check on neighbouring bytes, to make sure it has not changed. If FSUIPC detects the change it does not dare jump to that place because to do so could crash FS.

Regards

Pete