GCODELoader contains wrong travel visualization
See original GitHub issueWhen using the GCODELoader, the travel moves of the gcode are not shown correctly. When opening the same GCODE in another program like Repetier or Cura, the travel moves are shown differently than when using the GCODELoader of ThreeJS.
Live example It can also be seen in the example on the ThreeJS website, for example if you zoom in on the travel moves between the 3 skirt lines. The travel moves are always shown a line too late.
To fix
To fix this issue, change line 155 from line.extruding = delta( state.e, line.e ) > 0;
to state.extruding = delta( state.e, line.e ) > 0;
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Simulation of Arduino Based CNC -- Arduino+ GRBL+ Proteus 8
Simulation of Arduino based CNC by Proteus 8 and GRBL firmware. In this instructable I want to show how to Simulate Arduino, stepper...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks!
I’ll apply the fix directly.