It appears that the Cura storage registry may have changed again. That should be an easy fix for the Autodesk folks to make. In short, Fusion360 needs to change its Cura integration code toġ.) Obtain the location of Cura from the registry key used by current versions ( instead of Cura STL model file)Ģ.) Append " -single-instance" to the value retrieved from the registry when invoking Cura. If it is before the "%1" flag, Fusion360 will fail to launch Cura. Cloud-based products like Fusion 360 remove many barriers to connecting and collaborating with remote team members. As workforces become more remote in a post-pandemic world, working together and designing products as a team becomes much more challenging. ![]() If it is after the "%1" value, Fusion360 will ignore it and call Cura without the flag. Fusion 360 Multi-User Assembly Design Collaboration. Attempting to add the flag to the registry does not help. īy default, this key does not have the -single-instance flag. You can see this in their installer script at. That's not where Cura 3.1 stores its registry information. ![]() HKEY_CLASSES_ROOT\Cura STL model file\shell\open\command From earlier update to Cura when auto load stopped working here is what was found:įusion360 attempts to find Cura by looking in the registry at In short, Fusion360 needs to change its Cura integration code to 1.) Obtain the location of Cura from the registry key used by current versions ( instead of Cura STL model file) 2.) Append ' -single-instance' to the value retrieved from the registry when invoking Cura.
0 Comments
Leave a Reply. |