3D GCode Viewer integrated with DWC
-
@Sindarius In my case it were Three.js geometries that were transformed by Vue so I moved them out of the data scope, which did the job for me. Check out the heightmap and temp chart components for further details.
@smoki3 Yes, the current visualizer in 3.2-pre-b1 doesn't have a pretty front-end yet. At the moment it can be used only to watch live prints.
-
I have a fork of the previous visualizer code that incorporates STL viewing, slicing, and a slick slicer settings / model control component (right now based on Slic3r). Let me know if you’re interested in the code. It’s based on AngularJS and relies on a NodeJS component to integrate with the user’s local slic3r settings and execute the slicer.
The goal is to eventually move it server side (cloud) for saving settings and slicing. Also possible to slice on the PI 4 - early benchmarks showed it performed at ~50% of a top end desktop, which means it can likely outperform a slice from the cloud with network transfer in most conditions.
-
Been a while since I provided an update. I have been working toward getting my viewer converted to a plugin in 3.2. Here's a little sneak peek of where it is at today.
-
Woow looking Forward to it
-
For anyone who is building and running the latest beta 3.2 you can install and test the plugin. Enjoy!
https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.5.0
-
Yeah! Super nice work!
Best
-
Hey, this requires DWC 3.2-beta3 but there is no beta3 on github? Only beta2.
Compiling the source code of DWC results in "Plugin requires incompatible DWC version (need 3.2.0-beta3, got 3.2.0-beta3pre)" -
@copystring You may want to wait for RRF 3.2 beta3 to be released if you don't want to compile it yourself. Sounds like you've got DWC compiled, but not the firmware itself.
-
Works for me when using the latest code off GitHub to compile my own
-
Just finished implementing object cancelling in the 3d viewer.
https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.6.0
-
What What What! Thats a game changer!
-
@PCR I am cleaning up some of the view so it looks a little cleaner.
I am still working through some transparency order issues. (Always a PITA)
-
awesome work.
-
Great work! I just installed and am excited to give it a try this weekend. One bit of initial feedback - it would feel much more intuitive if there was an option to flip the camera control around and the center scroll wheel's zoom..
-
@oozeBot Noted. Appreciate the feedback. I'll have to look into making that an option. I think some of it comes from how you play video games. I tend to use inverted mouse when I play games so it has been more natural to me, I can see that being a problem for others.
I am resolving some alpha blending issues and trying out some different textures.
I expect to probably have another version out this evening.
-
This is truly wonderful!
I love seeing the cancelled object.
-
A genuine question.
What is considered the real world use for this?
-
@CaLviNx
when one print fails over you can still finish the print on the other objects.
-
@Veti said in 3D GCode Viewer integrated with DWC:
@CaLviNx
when one print fails over you can still finish the print on the other objects.
How does it do that then ? if what you are saying is true then how does the printer know one object has failed and stops extruding for that object but continues to extrude for the others?
And that still doesn't explain the real world application use of this when you can see 99% of this from the slicer
-
@CaLviNx said in 3D GCode Viewer integrated with DWC:
How does it do that then ? if what you are saying is true then how does the printer know one object has failed and stops extruding for that object but continues to extrude for the others?
this has been a feature in octoprint for some time.
https://plugins.octoprint.org/plugins/cancelobject/each object layer has a prefix comment. if the object is to be cancelled the pointer jumps to the next prefix object for the g code printing. leaving out the g code of that object.
