Ha, nice dig! Thanks! (no offence taken by the way and also not taken even remotely personal)
I do have a remote camera setup - probably should have mentioned that in the beginning, but to address concerns - I think we all agree that even a remote camera isn’t the safest thing to use as you we should all be closely monitoring the print by being in the presence of the machine during the print. This topic wasn’t about safety or trying to convince people that if this feature existed that they shouldn’t be monitoring their GF (although cool pictures of GFs exploding is always good to remind us of the consequences of going to the bathroom in the middle of a 5 hour print).
@Tom_A - I will admit I am extremely ignorant of how much memory the GF has and how it handles processing the jobs that are sent. I do have 3d printers and a CNC machine and the GCode that they use is very minimal in size even for the largest jobs (under 5MB for sure), so I didn’t consider that there would be a bottle neck in the GF memory. I thought the issue on their memory is that they are actually processing the conversion of the .svg file (or bitmap) to some sort of G code which takes processing time and can also hit the max limit of the on board memory (not to go off subject, but if they had a native app on Windows/Mac that would solve that problem so you are only sending the ‘gcode’ or whatever - maybe that should be another RFE to solve your max memory issue you had in the past…).
Back on topic - the camera snapshots would just simply be great to track the accuracy of the print versus the layout so you can monitor how close the final result will be to what you desired. That’s all.