3D GCode Viewer integrated with DWC
-
@Exerqtor I have a release that is now updated to 2.0.4
https://github.com/Sindarius/DuetWebControl/releases -
Yeah i got the notification from Github earlier!
Just installed it, and it works but the extruder colors don't apply to the renders for some reason. There static gray (just tried with single extruder slices so far) no matter what i change the colors to.
-
@Exerqtor This could be one of two things.
-
After you change the extruder colors are you hitting the "Reload Scene" button?
-
In the menu under stats if it switches from Mesh Rendering to Line Rendering the model is probably too large so it switches to line render mode which does not show the colors very well. This is something I plan to revisit to see if I can make the line colors a little more pronounced.
Edit
There is a 3rd possibility that I need to double check. It's possible that there is no T# call anywhere in the gcode for single extruder prints which may be throwing off what extruder it should be using.
Edit 2
It was the 3rd possibility. If there is no tool selected or M567 it will default to Extruder 0 in the next build. -
-
Yeah i've tried to "Reload Scene" a couple times, also closing the 3D viewer and opening it again.
It's on Mesh Rendering to with T# defined in the gcode several places.
-
@Exerqtor What slicer did you use and can you get me the gcode so I can dig into it?
-
It's sliced with S3D 4.1.2, sure here you go:
https://mega.nz/#!cR1jXLRA!9eZoYY-lZ7a8RdKR87jEwkwRBLeF4Bmy5oPojnggE1gI've tried several gcodes and the same happens in all of them.
-
@Exerqtor Thanks, I'll take a look at it!
-
@Sindarius
It looks awesome! I think you can dev a column for preview Gcode picture/icon is more better. It just like the repetier server. -
@Exerqtor I found what was causing the issue with this gcode. Looks like I forgot to scrub out the comment which was throwing off the parsing. I'll get a fix for that here in a few minutes.
-
-
@Sindarius Just loaded it up and what I see looks sort of OK think you also need to check the Config.g to decide on the type of printer it automatically seems to default to a Rectangular bed with the origin at 0 0.
I the case of a delta the origin is still 0,0 but is in the centre of a circular bed.
I you check the config.g for a M665/M666 lines and set it to circular centre origin it would be pretty damned good?
-
@Dougal1957 Delta support is on my down the road list at the moment. I would need to see if there is a way through the rest services to read M665/M666.
I don't own a Delta but an early compromise would be to let you select the bed shape (circle/square) and let you adjust the radius of the bed for now. I am currently storing settings client side for the viewer and not on the duet/pi itself.
-
@Sindarius said in 3D GCode Viewer integrated with DWC:
@Dougal1957 Delta support is on my down the road list at the moment. I would need to see if there is a way through the rest services to read M665/M666.
I don't own a Delta but an early compromise would be to let you select the bed shape (circle/square) and let you adjust the radius of the bed for now. I am currently storing settings client side for the viewer and not on the duet/pi itself.
That would be a fair compromise along with being able to set the origin although you could default it to be 0,0 in the centre of the bed. That would work but allowing the Origin to be set manually would be a good idea anyway as I do know some like to have it in the centre even on rectangular beds.
another suggestion would be to show non print moves in a different colour as well (those without any E movement).
Doug
-
@Dougal1957 I had non-print moves in there at one point and even with toggling just found them to be noise, which also reduces the amount of polygons that can be rendered for the models. Since I am not doing a line by line scrub bar I don't know that travel moves make much sense to visualize the model's end product.
-
@Sindarius said in 3D GCode Viewer integrated with DWC:
@Dougal1957 I had non-print moves in there at one point and even with toggling just found them to be noise, which also reduces the amount of polygons that can be rendered for the models. Since I am not doing a line by line scrub bar I don't know that travel moves make much sense to visualize the model's end product.
OK I can live with that it was just a suggestion and if you have tried it and it don't really work then that's fine.
Doug
-
Did some mobile tweaks in a new release that is now availabe on github.
https://www.youtube.com/watch?v=XxkoAm-oLH0&feature=youtu.be
I plan to address the ui scaling in a future release.
-
Is it possible to change this to a Tool to live view the current Layer in the sliced view?
What i mean with this is shows the Print in Orange with 100 Opacity for example and the rest upcomming in Orange 50% Opacity with a few Things like Printtime and Layer Number etc.Is this possible?
-
It’s possible but my priority with this tool has mainly been to view the colors that are assigned by tool / m567 mixing as a preview. A few folks have asked for a live view. My early go will probably just adjust the z slider automatically on the side.
-
@Sindarius
is it possible to have this also in DWC 3.1.1 for the Duet 3? -
@Sindarius any possibility to update to 3.1.1
