Hello,
We are wondering if there is a better way to approach a problem we are experiencing when trying to view the monitor on our artist workstations.
We’ve installed the client without the “Launcher as Service” and “Slave on startup” options to avoid the GPU hardware limitation as described in the user manual. Our current setup, has a dedicated render user that logs in on startup, launches the Slave application via a shortcut in the startup directory, then locks itself. The problem occurs when another artist logs in and attempts to start the monitor: it does not appear (although we can see it in the task manager). We found we have to terminate the launcher process under the render user first to get the monitor to appear with another user. I understand the launcher gives us the ability to manage the machine remotely, and is why I’m concerned with terminating it, or having it running under a non-dedicated user account. Hopefully this makes sense.
Is there a better method to configure the workstations to launch the monitor with multiple users without terminating the launcer process or losing the ability to use the GPU? Any advice on approaching this would be greatly appreciated.
Thanks in advance,
-Alex
