You know, it would be great if the programmers put in a file size check and if too big then tell the user it’s is too big! … just sayin…
This could go into CC when the *.nc file Is saved and also in CM when an attempt is made to load a large file. This sort of thing i have always referred to as “user-friendly programming” where the user is given an understandable reason why something either doesn’t work or is a bad idea… and preferably give a suggested solution ( or a link to a longer solution.
Another of many examples is if the user selects a path that is far deeper than the stock, or a far too slow or fast feed rate or plunge rate etc. there was a post here the other day when someone put in a plunge of say 5 thinking it was mm and in fact it was in inches. Please save us from ourselves!
Gone are the days of “USER ERROR 3478” and other equally useless and unhelpful behavior…lol