Closed funinthefalls closed 8 years ago
I get the same
Funny thing is it works at http://hakanbastedt.github.io/ without any issues.
Sorry, the word 'fix' in the commit name autoclosed the issue.
I manually pasted over the two files from https://github.com/HakanBastedt/HakanBastedt.github.io/
Check if it resolved your issues? (Seeing as you say it works without issue on http://hakanbastedt.github.io/ it should)
@HakanBastedt ^ (;
Though looking at the generated diff off the two pastes, I dont see anything off. (I only added some unfinished G7 code lol)
Whatever you did, it fixed the problem.
I take it that it works now?
Having problems once generating the gcode again, system hangs for up to 3-5 minutes, process a little more, hangs for a few minutes, process a little more and so on. Was working after Peter made a fix earlier, looks like the Y resolution increase has done something to it.
Strange, just tested here on openhardwarecoza.github.io and it worked nicely for me. Is it a particularly large image or so? Is it better when you start with a new freshly started browser? I do 2000x2000 without problem, and I am sure I can do much larger than that.
The Y resolution should not influence this, the same amount of G-code is generated now as before, there is just a small difference in Y value.
It is now working for me. Not sure what the issue was, but this can be closed now.
Since the last merge, files that generated the raster and preview and gcode in less than a minute are now taking much longer (5 -10 minutes to complete the process, or even causes a hang sometimes). The raster seems to generate just as quick, but creating the gcode and displaying the preview seems to be where the bottleneck is. Not sure what has happened, but it definitely feels broken.