-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cura 5.0 MeshTool Oversize the Part but not immediatly #26
Comments
This is pretty much what the "Unit for files that don't specify a unit" does. It looks like the model you opened actually has its coordinates specified in mm, but you told the plugin to interpret them as inches so it scales the model op by a factor of 25.4 (from inches to mm) after loading it. The pause is a bit strange; is the model very detailed? |
The issue his not on what meshtool do with the model ( even if it's strange that this setting have been change as I never modify the default parameter of your plugin ) It's really on the laps time between the time I load the part and the size modification ( In the previous release the representation of the model in his original size was not visible) It's not a complex part , it's the test part used by Ultimaker in their Cura 5.0 Video : |
Using the barbarian plugin on the same part, is not very long. So I don't think it's a issue with the model complexity Wq2zzBgpkz.mp4. |
The barbarian plugin does something different; it sets the scale in Cura. MeshTools actually changes the coordinates in the model, rebuilding the model. That way you end up with a model that is at 100% with MeshTools, which IMO is a better UX. |
Is the pause between loading and scaling still this long with the final release of Cura 5.0? |
Hello,
With the Cura 5.0 meshtool oversize the part but not "immediatly" as we can have with cura 4.13. So could be hard to understand what is the origine of this issue.
BcA9iTyXGM.mp4
The settings "Unit for files that don't spcify a unit" was in this case set to inch and not to the default Milimeter. But I cannot be sure of an issue with the release or a PEBKAC.
The text was updated successfully, but these errors were encountered: