This all started in an attempt to take the Denoiser out for a spin. I see AMD listed first, I beeline for it disregarding anything else since there’s a Radeon Pro 5600M on board. It took a few seconds longer than expected for something to happen when typing the PackageManager command, but the new-to-me dialog came up and I selected AMD. As Scott’s announcement post instructed, I restarted RhinoWIP only to get a “Rhino has unexpectedly quit” warning.
At the next opportunity, I loaded my SubD model and hit the Render button. The render screen showed no sign of the Denoiser option to check-mark. Killed the render operation and typed the PackageManager command. 15 seconds of waiting and nothing shows up. Found “Package Manager” listed under the Tools menu. Nothing comes of that either. Reboot? Yeah, that’s always the answer. I may have gotten another “Rhino has unexpectedly quit” either here or at the start of the next launch. Next launch, I definitely got the type of error that reports back to McNeel.
By the time I get back into Rhino, I load a fresh template, make a SubD sphere, start a Render and verify there’s still no Denoiser. Package Manager still not invokable through command line or menu listing.
Preference > Plug-ins shows:
Deactivating AMD Denoiser from the Plug-Ins list still doesn’t bring Package Manager back. The polite suggestion to use the Intel Denoiser for Macs should’ve probably been injected into the AMD listing.
Is nuking RhinoWIP the only way to restore PackageManager?
Attempted to paste diagnostic stuff from one of the error screens, but at 16,000 characters, it exceeds some kind of forum limit. They’ve been initially sent via the reporting process.