6 Commits

Author SHA1 Message Date
Ghostkeeper
8b10bef0a6
Actually compress the 3MF archive
Yeah, I only compressed one of the files in it previously.
2020-06-26 19:00:15 +02:00
Ghostkeeper
51d0545201
Actually compress the 3MF file
It was a zip archive but just using the archive 'compression' method, not LZMA or Zip or anything.
2020-06-26 18:58:37 +02:00
Ghostkeeper
922986a3f9
Apply transformation inside 3MF file
It turns out that we have another bug in Uranium: Transformations from 3MF files are not applied to the platform mesh. This makes sense because UM.Scene.Platform takes the mesh data (without transformations) from the node that it read and squashes that into the SceneNode for the platform. This SceneNode already has a transformation for the platform offset. The 3MF node also has a transformation from the 3MF's convention to have the origin in the front left. The 3MF reader then squishes the transformation from the node into that.
To fix this we'd need to either:
* separate the transformation of the 3MF file from the transformation from the 3MF convention to have the origin in the front left, so that we can pick and choose, or
* remove the transformation from the 3MF convention and apply it only on loading normal printed meshes, and then modify all of the 3MF platform files.

Both require significant effort. So instead I applied the transformation directly to the vertex data.
To do that I imported the file into Blender using my own Blender plug-in, exported to STL and imported that STL again to apply the transformations, and then exported the file from Blender again.
In Blender I also combined a lot of flat faces together, which reduced the file type losslessly.

Contributes to issue CURA-7534.
2020-06-26 17:56:52 +02:00
BeamUp 3D
88c0746fa8
Update beamup_l.3mf
Rotated
2020-06-26 15:46:35 +03:00
BeamUp 3D
2f48b93bb3
Delete beamup_l.3mf 2020-06-26 15:45:46 +03:00
BeamUp 3D
b7eb3f4f75
Add beamup_l.3mf 2020-06-19 11:35:26 +03:00