Hello, i am facing an issue, not sure if it is related to corona and/or 3dsmax :
If you use th “lock viewport” function on 3dsmax using a first “viewport set” (let’s say the default quad), and then you swicth to a different “viewport set” (2 viewports for example), as long as the lock is on, only the main machine will compute, the slaves dont, without any error messages.
As soon as you untick the lock, they’ll compute again.
I understand that locking a viewport from a different set could lead to some difficulties (viewport ID ?), but as the main machine deal with it without worries, could it be by chance corrected for the slaves also in a future release ?
I’m pretty sure this is a 3ds Max problem, not specific to Corona. It also explains why for some users the solution to DR issues was unlocking the viewport > making sure the correct viewport is selected > locking the viewport again.
Perhaps we could prevent that, or at least show an error message. We will look into it.
