This is really consistent and happens everytime I’m moving/copying vertexes or edges around and autosave kicks in.
It also crashes when moving/copying components and groups, but there I haven’t been able to capture what happens exactly with the geometry I’m manipulating.
I suppose this doesn’t happen with simple models, but I don’t know.
Exactly. That’s been happening to me for over a year!
It only happen when I’m performing operations with (ctrl+) command to copy geometry around. Will be great is anyone from Sketchup could investigate this crash.
I agree with John - my experience has been that when SketchUp suddenly crashes with no apparent reason it is often from a misbehaving extension’s observers. Observers run constantly in the background, and a user is not aware of when they fire unless a crash results! Observers have to be carefully written to avoid problems with “sawing off the branch you are sitting on”.
I have installed few extensions, no rendering extensions though! but I haven’t got a clue how to investigate the attributes of the files. If anyone could tell me how, that will be fantastic.
I can tell you Trimble is already investigating several bugsplats with autosave.
We are aware of problems with Skalp in combination with autosave. We use indeed the onPreSave observer for writing attributes to the model. But there are scenarios also without Skalp or any plugin.
I can confirm that as I don’t use Skalp… (sorry Guy, it’s an amazing plugin, but my workflow is too dependendent on drawing on SectionCutFaces and having 2D hole cutting component details on them… maybe if this workflow is one day integrated in Skalp.)
LOL. It’s not a beast! It’s just such a sweet computer (well it’s more like something around a GPU)…
I would seriously have issues if I wouldn’t use Layer’s Panel. Basically I’d have to start using some serious software like Revit or the likes. I’d be damned if that they would come!
Let me add that I’ve been using Layer’s Panel since it came out, and never had an issue before 2017.
However my brother and fellow architect has had this same issue on previous versions.
So, this might run deeper into SU’s core, and just something pulled it to surface in 2017, as I’m noticing more people having the issue (or probably it’s just that now I’ve got the issue too.)