Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    3D GCode Viewer integrated with DWC

    Scheduled Pinned Locked Moved
    Duet Web Control wishlist
    42
    284
    30.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Sindariusundefined
      Sindarius @A Former User
      last edited by

      @the_dragonlord By chance did you remove my plugin just to make sure it's not anything I am doing?

      A Former User? 1 Reply Last reply Reply Quote 0
      • Sindariusundefined
        Sindarius @DaBit
        last edited by Sindarius

        @DaBit Just by sheer curiosity have you tried on max render setting and when you see that line zoom way out? This really has me stumped because I have never seen that behavior.

        1 Reply Last reply Reply Quote 0
        • DaBitundefined
          DaBit
          last edited by

          It seems to end and not continue in height above the bed indefinitely:

          gcodeviewer093_switchtomax3.png

          Sindariusundefined 1 Reply Last reply Reply Quote 0
          • A Former User?
            A Former User @Sindarius
            last edited by A Former User

            @Sindarius said in 3D GCode Viewer integrated with DWC:

            @the_dragonlord By chance did you remove my plugin just to make sure it's not anything I am doing?

            no because I urgently needed the printer and I had no time to make a try, I've downgraded the whole... tomorrow I will give it a try... but I'm sure that yesterday DWC was sooooo slow to connect even before I installed your plugin

            1 Reply Last reply Reply Quote 0
            • Sindariusundefined
              Sindarius @DaBit
              last edited by

              @DaBit that’s pretty cool! I am stumped on that one. I am putting together a build that will turn on some debug tools and maybe help us figure out what is going on.

              1 Reply Last reply Reply Quote 0
              • DaBitundefined
                DaBit
                last edited by

                Let me know how I can help!

                Sindariusundefined 1 Reply Last reply Reply Quote 0
                • Sindariusundefined
                  Sindarius @DaBit
                  last edited by

                  @DaBit I added a debug version which is going to throw a lot of stuff to the console and show some debug tools in the UI.

                  What would help me is after you refresh and the first load works clear out the browser debug console and hit "reload view" Mainly I am looking to make sure the gcode line count remains the same and that meshes are actually loading. You may want to try a slightly larger model in medium+ render setting to make sure several meshes get rendered.

                  https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.9.4

                  It should look something like this
                  ccda3b22-171d-47a6-bbce-3456631b5d75-image.png

                  191c9798-95e6-4702-bc36-dbbc6edb0f6d-image.png

                  1 Reply Last reply Reply Quote 0
                  • DaBitundefined
                    DaBit
                    last edited by DaBit

                    A larger file, 19MB of Gcode:

                    Screenshot 2020-11-27 161911.png

                    After hitting Reload View:

                    Screenshot 2020-11-27 162123.png

                    I do get the same 32 meshes and line number.

                    Mesh 0 is the only one shat shows some form of a boundary box when I click the checkbox in the scene explorer.

                    Screenshot 2020-11-27 162833.png

                    (on first load I see every mesh containing a slice of the model)

                    Can I see the data in the vertexarrays somewhere? OpenGL has been some time ago for me, but I have a gut feeling something goes wrong when filling those.

                    Sindariusundefined 1 Reply Last reply Reply Quote 0
                    • Sindariusundefined
                      Sindarius @DaBit
                      last edited by

                      @DaBit It's almost like your points rendering to a massive scale or off into the nether. What is confusing is it renders the first time. Looking at the last picture the axes for the bed are very tiny which means the scale of that boundary is massive. I use PrusaSlicer for a majority of my prints and haven't seen this before. Have you updated your video drivers? At this point maybe getting your printer's config and sample gcode may be necessary to solve this. You're the only person I am aware off having problem and you're seeing it on both desktop and mobile.

                      If you can make an issue on github and attach supporting files that may help me get down to the bottom of this.

                      1 Reply Last reply Reply Quote 0
                      • DaBitundefined
                        DaBit
                        last edited by

                        Yes, graphics driver is recent. That is the first thing I update when encountering display issues in software.
                        (it never ever resolved them though 🙂 )

                        Sindariusundefined 1 Reply Last reply Reply Quote 0
                        • Sindariusundefined
                          Sindarius @DaBit
                          last edited by Sindarius

                          @DaBit You can go to the tools in the inspector tab and export a babylon file. That will export all of the meshes vertices to a file and you can look at them. may show if they are really wrong.

                          Edit : Thanks for sharing your gcode file. I was able to recreate the issue by using your gcode.

                          1 Reply Last reply Reply Quote 0
                          • DaBitundefined
                            DaBit
                            last edited by

                            I am seeing quite large numbers in the Babylon file in the vertexData array for index 8 after 'weird behaviour', and further in the list the numbers are only growing, in the 3-million-range.

                            Screenshot 2020-11-27 180015.png
                            (left is OK, right is 'weird behaviour')

                            Sindariusundefined 1 Reply Last reply Reply Quote 0
                            • Sindariusundefined
                              Sindarius @DaBit
                              last edited by

                              @DaBit I think I found it! There was an issue where my processor was throwing away commands like G90 and G91 because it didn't have any tokens like X0 etc. Clearly a problem on my side. What happened is at the end of your gcode you had a line "G91 G1 Z20 F500" which caused my processor to pick up the G91 and go into relative mode. The next render would stay in relative mode and not read the G90 early on so it would just keep adding the coordinates to each other which lead to the massive numbers.

                              Got it fixed here.

                              https://github.com/Sindarius/DWC_GCodeViewer_Plugin/releases/tag/0.9.5

                              1 Reply Last reply Reply Quote 0
                              • DaBitundefined
                                DaBit
                                last edited by

                                That makes sense indeed!

                                OK, next! 😁

                                Given the 'small-ish' sample G code file, zoom in like this:

                                Screenshot 2020-11-27 195102.png

                                Zoom 1 step further, and the model disappears:

                                Screenshot 2020-11-27 195124.png

                                And a personal preference: I don't like the 'viscous' behaviour while rotating/panning/zooming very much. I would love to have a checkbox to turn that off.

                                Anyway, quite happy with the plugin. Thanks for giving us that!
                                Very useful to check if the file on the SD card that you printed 3 months ago is indeed the one you want to print now.

                                Sindariusundefined 1 Reply Last reply Reply Quote 0
                                • Sindariusundefined
                                  Sindarius @DaBit
                                  last edited by

                                  @DaBit I know what is causing the zoom in thing. with orbit cameras there is a target point and when you shift and pan that target moves. When you hit that 0 point the camera flips sides. It's annoying and something I am trying to find a better solution for. I can look into an inertia toggle but it's been fairly low on my list.

                                  1 Reply Last reply Reply Quote 0
                                  • Exerqtorundefined
                                    Exerqtor
                                    last edited by

                                    I have a little suggestion/wish for a feature or improvement to how the object model "block" is displayed. How if instead of being a translucent green box all the time, it would be a neon-green "outlines" (like the volum view in settings) until you hover over the object and it then turns to the green box. i think that would look much cleaner.

                                    And maybe a slider for adjusting the hue of the lines and transparancy of the box as well?

                                    Sindariusundefined 1 Reply Last reply Reply Quote 0
                                    • Alex.crundefined
                                      Alex.cr
                                      last edited by Alex.cr

                                      Reporting a small issue, upgrading to Beta_4 breaks the plugin. Not surprisingly I guess.

                                      An error is reported saying "Error: Plugin GCODEViewer requires incompatible DWC version (need 3.2.0-beta3, got 3.2.0-beta4)"

                                      Great plugin though!

                                      Voron2.4/Duet3 SBC+6HC+3HC+1LC+1HCL(x2) - Delta/Duet2 Wifi - CubePro/Duet2 Wifi+Duex5 - Laser/Duet3 Mini5+ - Cel Robox - U̶p̶3̶0̶0̶+/D̶u̶e̶t̶3̶ ̶6̶H̶C̶+̶LC1̶ - F̶T̶-̶5̶/̶D̶u̶e̶t̶2̶ ̶W̶i̶f̶i̶ - S̶o̶l̶i̶d̶o̶o̶d̶l̶e̶

                                      Sindariusundefined 1 Reply Last reply Reply Quote 0
                                      • Sindariusundefined
                                        Sindarius @Alex.cr
                                        last edited by

                                        @Alex-cr The screenshot didn't come through but I have updated the plugin zip file to flag to the latest beta4 version.

                                        1 Reply Last reply Reply Quote 0
                                        • Sindariusundefined
                                          Sindarius @Exerqtor
                                          last edited by

                                          @Exerqtor I'd have to play with it because the hit testing may ignore the transparent area and honestly I tend to think people wouldn't leave it on after cancelling objects because it is so easy to misclick and potentially cancel something you didn't mean to (even with the dialog).

                                          Exerqtorundefined 1 Reply Last reply Reply Quote 0
                                          • Exerqtorundefined
                                            Exerqtor @Sindarius
                                            last edited by

                                            @Sindarius said in 3D GCode Viewer integrated with DWC:

                                            @Exerqtor I'd have to play with it because the hit testing may ignore the transparent area and honestly I tend to think people wouldn't leave it on after cancelling objects because it is so easy to misclick and potentially cancel something you didn't mean to (even with the dialog).

                                            Yeah that's a valid point 😅

                                            Sindariusundefined 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA