OSC output act weird on arena reload re-scaling targeted comp

[Hakol.Sound]

We have a main machine that sends column triggers (only column triggers) to another Resolume machine, means all OSC output commands are disabled rather than column triggeres.
That works great and indeed every column trigger on the first machine fires the correlated column on the other.
UNTIL, you need to restart Arena on the main machine:
When main Arena restarts it sends some hidden OSC command (that no one asked it to) that changes the composition dimension and clips scale.
The only way to eliminate this behavior is to *manually* disable OSC in on the other machine until main Arena re-loads, forcing the second machine to 'not listen' while first one loading.

We had this issue before with a Mac Studio as the first machine and Windows based on the other, after some back and forth with the support we got to an understanding it is an issue with texture size mismatch between both machines.

Replacing main machine was the thing to do, or so we though.
Now both are windows based, both with same display adaptor (RTX 6000 ada) but the not wanted scaling is still here.

Any one experienced similar issues?
It would have been nice to be able to toggle OSC in/out via REST API/ midi or even a keystroke shortcut. GUI is just not fast enough for live show.

[Zoltán]

viewtopic.php?t=29796

[Hakol.Sound]

Thanks but this has nothing to do with backup what so ever.