3D GCode Viewer integrated with DWC
-
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.
-
yep. its super useful if you printing a lot of small parts and it happens that some does not stick!
There is a thread somewhere here explaining it!
Will post the link later -
@CaLviNx if you are talking about the 3D viewer the original purpose of it was because I use a mixing hotend and I wanted a way to preview how a model would look when i changed the filament on each of the extruders. This viewer approximates what the printed model will look like based on configured colors. Another use is being able to see the model before printing without having to go to a slicer to load it up.
-
Now that is much closer to the word "simulation" than what is now
- WOW! I LIKE IT!I can easily see a big benefit (if this is going to be the new simulation), to also check that you have positioned your file correct on the heatplate, especially when working with additional csys beside the master-machine-csys, BECAUSE -> since it can get from the duet-config.g the maxi building size and can fetch the current "working-csys" (G53-G60 is what this is referring to) no more fuss there!!! You could show even "all" moves (travel-moves etc.) that are in the file to make sure everything is within bounds.
Can you tell me if that is implemented already and or if you think you would also have a use-case for this and could implement it?
Because that is something for big printers/cnc/lasers that almost no slicer can do (if you do not want to spent "real" money for it and not just a few bucks), to have a simulation with G54 in relation to your workingarea where you have positioned your local csys and where exactly it will be printed then!
(
some people might wonder about the use-case but 2 years ago when working in an art-school, we had courses where we had to position diffrent files on one plate and usually you do this with "sub"-csys like G54, G55, etc. and nobody in a semi-professional environment for basic/-beginner courses will have a slicer or laser-software or cam/cnc-software where they can simulate the whole machine with sub-coordinate systems. The safest thing is to do the work 1 time for/on the actual machine, so to avoid to have to put it into each software every year when a new version is implemented...
)
-
@LB I can’t say that I have implemented anything for it. I would need to see a sample and look into the use case. This viewer does not simulate exactly what the duet would do it processes the gcode and renders it for the commands I have implemented.
-
@TLAS said in 3D GCode Viewer integrated with DWC:
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.
Great feature!
Hope others have the same usecase:
Would appreciate to have the option to run it "locally"(no cloud), since we use duet-boards here at my work (because of me we converted the anycubic i3 mega when the mainboard died instead of throwing it away and buing a new one) and I do not think that by any means my boss likes the idea of our company-files being sliced/simulated in some sort of cloud somewhere... I think most company-printers with a duet or printers in public spaces (because of local data-protection-laws) would appreciate local viewing/slicing!Great work anyway - unbelievable to see how much is going on
