Ghostkeeper

I don't know. Could you show me Cura's log file?

@mwu1020 there is a similar report for MacOS here, with a lot of discussion: https://github.com/Ghostkeeper/X3GWriter/issues/30 The problem with MacOS seems to be that the GPX binary I'm using is linked...

Strange, it looks normal from the log file that Danmchales posted. Writing the file took 0.26s, the GPX command gives no output in its error streams. All seems correct to...

I'm working on a new release of the X3GWriter with updated GPX version and rebuilt binary, as an attempt to fix this. I have a preview here, which you can...

You could try installing the Printer Settings plug-in and fiddling with the machine settings that become available then, such as the Steps Per MM (Z) setting.

Yeah, I've seen it. There are still older ones I'd like to handle first.

The merge conflict is resolved on the https://github.com/Ultimaker/pynest2d/tree/StefanBruens-cmake_use_imported_target branch.

This seems to fail to build, on Windows only. We're getting this result: ``` -- Found PythonInterp: X:/env/CURA-8240_pynest2d_transitive_dependencies/inst/bin/python.exe (found suitable version "3.8.8", minimum required is "3.5") -- Found PythonLibs: X:/env/CURA-8240_pynest2d_transitive_dependencies/inst/libs/python38.lib...

Well, that's just replacing the find procedure with a manual hard-coded path in the cura-build-environment source. I don't think that's something we want to merge then, since it wouldn't be...

> It does not hardcode the path to libnest2d, it provides the path of your build/install prefix. Obviously you have that already set somewhere, otherwise it would not be able...