I totally agree with the need for a VP forum category, +1 ! It’s nice to see your reply @echo_four as I have seen a number of questions asked throughout the forum that have gone unanswered in this newish VP use case category, and my guess is not having a place for people to come means they have to guess at where best to post those questions, so perhaps they are getting missed since the right patrons and devs aren’t keeping an eye on all the places in the forums.
per your question @trabtown my assumption is since OSC is not a “standard” HID input sort of protocol, (its simply UDP network messages), it isn’t really included in the input sync features of nDisplay.
I’ve done a lot of work with OSC in other applications for large scale multi-output sort of things (mostly using TouchDesigner) and have had to get commands to multiple nodes all the time. I usually set my system up to have a master know that when it is in master mode it will relay commands ( either via more OSC or internally more robust protocols) and then the slaves, when in slave mode will adjust their listening to listen for commands from the master instead of an external controller. I think a similar thing could be done with nDisplay.
Alternatively you could look into the multi-cast options for Lemur and try to pick everything up on a multi-cast setup, though this could be error prone depending on your network.
Probably the most robust is to use the built in nDisplay sync components, which I am not super familiar with yet. I’ve only tried using them to keep actor and SM comp transforms in sync, but I believe I read in the documentation that you can keep other parameters in sync between nodes for the actors you want to synchronize.
Cheers
P