CLI version looks for include file on a wrong path on Win 10

  • Hello, I'm testing my unflatting script on a Win 10 machine and it seems that there's a bug on this platform that tries to open an included file from the main script path, but it cannot work as this path contains the main script file name. It works fine on Ubuntu, so it can be something tricky to resolve.


    To make it work for the moment I replaced the includes with their content on the main script, I can easily add this to my nodejs script that create a .jscad from the .obj file containing the 3d model to unflatten. Sadly, I will only be able to use this win 10 machine for a few days.