Cargo forces to close Unity for no reason | Voters

Cargo forces to close Unity for no reason

Mike Wuetherick

Cargo forces you to close all instances of Unity that are open for no reason. The plugin is install on a per-project basis, there is absolutely no need to force the users to close all instances of the editor before installing the plugin. This is very frustrating.

March 18, 2024

Leland Green

I'm not familiar with Unity plugin development or the requirements. If possible, I'd like this feature, too. (I think all Unity users of Cargo would!) 
But since the KitBash3D plugin is essentially integrating with the editor, maybe it requires closing the one you're installing to. If you have other projects open, it seems like installation could avoid closing all instances. Maybe with a "proceed with selected project", if they can't tell which editor is which during the setup. 
Better yet, what if we could install to an empty directory, and then simply copy the resulting files/folders to existing projects??? Would that be "ideal"? I think it should be an option. 
BTW, I've copied the plugin to another project, and it seems to work fine. I closed the editor for the target project first, though. (So it seems we could install to a "central directory" via a "manual installation" option for Unity. Right? (Or has the plugin changed since I did that??)
🖖😎