3D GCode Viewer integrated with DWC
-
Awesome! This is getting installed right after the ongoing print is done for sure!
Hope it get's integrated to the master asap!
-
This is awesome
Is this Client or DWC based? -
@AS-3D-Druck this is DWC based. Opens a new browser window to launch the 3D viewer but no special installation beyond the branch I have with it integrated.
-
@Sindarius Ok, what i tryed to say is does it get calculated by a Script on the Client or Duet Side?
-
@AS-3D-Druck it’s javascript based so it is client side. The viewer downloads the file and renders it.
-
@Sindarius Cool so it can be used even during a print Job right?
(without negative effecting the print Job) -
@AS-3D-Druck I use it while printing all the time. Only one Duet based printer at the moment
the file download doesn’t impact the print from what I have seen. -
Have you tried it with DWC 2.0.4 btw? I see that it's still realeased based on 2.0.0 ?
-
@Exerqtor I’ll look into updating the baseline with the latest. My changes on the DWC itself are very minimal. Just what is necessary to make the 3D Viewer link in the gcode list
-
@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?
