I have had a number of occurances with slicing in Cura, saving to file, and then loading the gcode into Luban to transfer to the printer and then the model not loading. And I think I may have figured it out.
Luban doesn’t like certain characters in the file names.
For example - the files attached are the same model, sliced in Cura with the exact same setting. They were just saved with different names from the same slicer output.
The “5.1 Right #” will not show the model in my Luban (3.13.1) after opening the file.
The “5.1 Right” is missing the “#” and will load just fine.
There seem to be a few characters that do this, but I haven’t gotten an exhaustive list yet. FYI - the file with the # will work in cura when opening the Gcode.
A good general precaution when you’re porting files back and forth between operating systems is to use a very restricted set of characters when naming them: unaccented Latin-alphabet letters (A-Za-z), numbers (0-9), period (.) and underscore (_). Those are all safe on any modern operating system and require no special handling, escapes, or Unicode/codepage support. Anything else will break something, somewhere.
You mean I shouldn’t do ť̷̝̪̣͈̠͑͐̌͒́̋̐̃͑͝ḧ̵̡́e̵̻͓̾̾̀̋̓̚_̴̨̞͔̠̙̦̘̬̅̒͐̅̈́͌̔̑̏̑͜ͅṛ̸̛̥̞̜̺̙̟̙̠̃̐͐̀͂̈́̏̐̒͌͂̚͝í̸̱̠̦̪̜̤̠̻̝̺͚̘̦̠̈͠ṇ̴͈̪̝̙̒̈́́̄́̆͋̋̉̔̍̚͘ģ̶̛̜̮̦́̈́͗̕.gcode
Out of curiosity I tried to see if I could quickly find an Electron JS quirk or something that would explain that bug - couldn’t find anything. ‘#’ isn’t even that crazy of a character, wonder which other ones are bad.
Might have something to do with # being the URL fragment separator (in which case I’d expect it to also have problems with other characters with special functions in URLs, such as @ : ? % and & ), considering that Electron has browser in its DNA.
