Thank you. I tested both suggestions using the standalone Reality Composer Pro 3 Beta 4 build 1A181 (80.0.1.500.1) on macOS 26.6 (25G72). --no-plugins Reality Composer Pro prints: error: Unknown parameter --no-plugins! It then opens only an empty “Untitled” recovery document. The project is not loaded, and the rejected flag means plugins were not actually disabled. --load-project I supplied a valid absolute path to Package.realitycomposerpro. Reality Composer Pro terminated with signal 6 and reproduced the original NSGenericException: “The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window.” The relevant stack still passes through: NSApplication runModalForWindow: libtm-plugin_support.dylib: prepareToLoad librcp.dylib: private__restore_or_open_project librcp.dylib: tick_application Therefore, neither workaround currently opens the project. Is --no-plugins available only in a newer internal build, or is there a different supported spelling for Beta 4? I will also add these results to FB24460905.