Poser blocking Standalone (network)

[Zay]

I've found out that having Poser opened before starting Octane Standalone will somehow block Octane Standalone to search for the client on my network. It never pops up on the list - until I close Poser. Anyone knows what is going on and how to fix that?
I have tried to block Poser through the firewall but it didn't help. Poser has to be closed before Octane Standalone can find the client.

[Zay]

It seems the plugin for Poser and the Standalone are colliding (running a copy of the settings from the standalone). This is very bad. The plugin shouldn't interfere with the standalone settings. If I want it off in the plugin it should stay off and not also turn it off in the standalone.

[face_off]

I will forward this issue to Marcus to see if this is the correct functionality or not. In my testing, it seemed the first thing that grabbed the network render node blocked the rest.

Paul

[Zay]

Any word on this? At the moment I have uninstalled the plug-in to get network rendering working properly.

[face_off]

Zay, I have still not heard back from Otoy on this. My render slave is currently converted to Linux and that will not run a slave at the moment, so I cannot personally test it.

If you run Poser, don't open the plugin, run Standalone, then Standalone should be able to grab the slave.

If you run Poser, open the plugin, enable a slave, then Standalone will not be able to attach to that slave until you un-enable that slave in the Poser plugin.

Paul

[Zay]

If you run Poser, don't open the plugin, run Standalone, then Standalone should be able to grab the slave.

I don't open the plugin in Poser. But it will still block the slave search in Standalone. As soon Poser starts it will open a TCP/IP port to listen for a slave even if the plugin is closed. And that will block Standalones attempt to search for the slave. So it doesn't matter if the plugin is open or not. You have to uninstall the plugin for it to work.

[abstrax]

If you run Poser, don't open the plugin, run Standalone, then Standalone should be able to grab the slave.

I don't open the plugin in Poser. But it will still block the slave search in Standalone. As soon Poser starts it will open a TCP/IP port to listen for a slave even if the plugin is closed. And that will block Standalones attempt to search for the slave. So it doesn't matter if the plugin is open or not. You have to uninstall the plugin for it to work.

This is currently a limitation: To work around it, you have to disable network rendering in the Poser plugin, before you launch the Standalone. We plan to solve the problem soon by having each master automatically search for free ports.

[face_off]

Thanks Marcus. Do you mean disable via the Network Rendering dialog "Enable Network Rendering" checkbox?

Paul

[abstrax]

Thanks Marcus. Do you mean disable via the Network Rendering dialog "Enable Network Rendering" checkbox?

Paul

Yes.

[Zay]

We plan to solve the problem soon by having each master automatically search for free ports.

Looking very much forward to that