SENDER: Nom :DefaultDomain
Aucune stratégie de contexte.
MESSAGE: Un composant externe a levé une exception.
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
@frederic.conrotte, this is fixed in the code already, it will be in the next 6.2 release candidate (and obviously final 6.2). You can for now load-protect the RhinoCycles plug-in while in the fail safe mode. Just don’t forget to re-enable it when you’ve got the next 6.2 release candidate (YT item RH-44147)
Also, please check your drivers. My guess is that you have at least a (built-in) Intel GPU that has a (very) old driver. If Rhino doesn’t see it, i.e. it sees for your possible Nvidia or AMD GPU, then check in the device manager if you have an Intel GPU - check its driver date. The crash I investigated showed a driver from 2012… You could try updating that also and see if the crash goes away.
Thanks for testing, this makes it even more important to submit the patch to the Blender Cycles developers
Probably begin March, but you can already subscribe to the service release candidate stream through Help > Check Updates... - the next release candidate that will contain the fix, and will probably available through the automatic update system. Probably sometime next week.