Yes, I also understand that with my pipeline I am bypassing LayOut which is designed for the process. OpenGL, printer driver, system font rendering or the like) can be very useful on the user side when bug tracking. I reckon, however, even a simple one-line reply like “This is a known issue which has/has not been addressed for the next version.” or “Call stack indicated that this crash is outside SketchUp code” (e.g.

To SketchUp team: I completely understand that it is not feasible to reply individually to all bug splats, especially where these might just be repetitions of the same known bug or something that has long been fixed. I reckon I still need to go through the official email contact chain to Trimble. It is more a combination of factors and likelihood.ĭan: I have sent in well over 20 bug splats with details by now but never heard back.

Scenes without any dimensions or leader text don’t crash.

It is still definitely Text/Font-related.

I use AutoHotkey to automate some tasks and twiddling with timing and delay reduces crash likelihood. Basically, pressing ‘Enter’ on the print dialog immediately makes a crash more likely than waiting two seconds before proceeding.

When printing several scenes in succession, the speed at which I run through the print dialog matters.

The 64-bit system with 64-bit SketchUp (and a slightly newer graphics card) crashes less likely than the 32-bit system.The issue is definitely performance-related. For now I need to weave the bug-tracking in with actual production work. I will go for more in-depth investigation when I find the time.

Sketchup make 2016 bug splat printing