G-Code Viewer when running a print (or previewing) is showing individual executions instead of the whole layer for me. This started happening with the release of 1.10.
What did you already try to solve it?
Adjusted slicer settings, scrolled through settings in octoprint, but couldn't find anything relevant
Have you tried running in safe mode?
Yes
Did running in safe mode solve the problem?
No
Systeminfo Bundle
You
can download this in OctoPrint's System Information dialog ... no bundle, no support!)
OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible
OctoPrint V: 1.10
OctoPi V: N/A running build on old desktop, seeing issue across all platforms. (octoprint web browser on multiple computers, phone, octoeverywhere, etc)
Printer: Anycubic Kobra Plus, upgraded with Wabbitguy's custom firmware, rebuilt for an E3D Revo 6 printhead
This is an example of the code I'm using. This has verbose turned on because I was trying to track out what could be causing it. I've also uploaded a version with verbose turned off.
Yes, It won't let me add directly to the site, as it's larger than 4mb, but here is a we-transfer link
I wanted to add that the first layer shows the whole layer fine, but any layer after that causes the gcode viewer to only show one small segment at a time.
It does look like this is a print that is sliced in "vase" or "spiralize" mode. The z-coordinate, after the 1st layer, is continuously increasing. I managed to access your google drive, link, and an example section of the file AKMAX_blade_5h52m.gcode:
It doesn't look like a typical vase/spiralize mode print - it still has flat infill, but then the outer perimeters are continuous rather than being drawn in layers.
The gcode viewer shows a new 'layer' for each z coordinate that it sees. This is why you'll see only a few moves on each layer.
After I did some testing, I discovered it's OrcaSlicer's "Scarf Joint" feature. What it does is over a pre-determined amount of steps, increase the z-axis around a perimeter. This is why there's the super super incremental increase in Z (0.001) over the perimeter.
I will let @foosel know about it, but as @Charlie_Powell - this is how the viewer is designed and it works as intended. Nobody thought of such a feature back then.
