Good news:
A had another user report this exact issue...and after some further debugging with them I believe I've tracked down the root cause and it'll be fixed in the next build (v1.024). It only happens during network rendering using v1.012 and above, and only when using Max 2019 or below, which is why it was tough to track down and why nobody else reported it.
A had another user report this exact issue...and after some further debugging with them I believe I've tracked down the root cause and it'll be fixed in the next build (v1.024). It only happens during network rendering using v1.012 and above, and only when using Max 2019 or below, which is why it was tough to track down and why nobody else reported it.