@jlauer I’ll take a look after lunch. Bummer.
Hmm. I wonder if it’s due to parsing the gcode on plane shift lines… eesh. Will need to review all that
I had to put a lot of effort into making sure the 3D viewer’s final array of Gcode lines had the same array indexes as the Gcode widget’s. That’s not to say you can’t do fun workarounds, but it is important that at some level a Gcode line can match up to 3D viewer XYZ data. That point really comes together in that pubsub call.
@jlauer exactly
I see the issue, I stopped adding the lines property to the userData of objects as it slowed things down… Ill add it back, but its not an optimal approach to this problem
I just pushed up a fix for the flyout menu
Ok, after a little more debugging, I have it rendering all the gcode I throw at it flawlessly!
missing/deleted image from Google+
No more little nuggets floating in space.
missing/deleted image from Google+