That's what I've been doing. I'ts quite an effort though to do that with every item you want to use..... Thanks for your reply though.

@tig said: ...on a side issue... ... and even a lone RB can be made into a ZIP and then that .zip file re-suffixed with .rbzso that it can be auto-installed... Thank you, TIG - this is great information. Won't add rb directly to the Tools folder anymore.

Thanks for that - turning off HWA solved my exporting .dwg problem.

Ok - I've found the problem - following a suggestion in another thread about crashes I turned off hardware acceleration and the problem was fixed!! Could you please pass it on to Trimble.

i don't run any of those.. but the problem seems to have gone away. i disabled Fredo scale and a few other plugins that I don't need on a daily basis and it seems to have corrected itself. will reply back if i find things get wonky again.

Never used 7 myself...

I am also experiencing crashes on my laptop (Windows 8.1, Intel M 5Y10, 8 gig RAM). No bugsplat, no warning, no other error message. Window simply disappears. I am experiencing no problems whatsoever on my older desktop (Win7, Intel Core i3, 4 gig).

thanks for the tip TIG, will try it soon. edit: TIG you were right. works fine when keeping the materials closed.

Nah. It should stay. Maybe someone else will come along with the same issue and happen on this thread. Glad you got it sorted out.

+1 to thumbnails

@unknownuser said: The problem with Window Explorer seems to be fixed. Whoopie. So thanks to everyone who figure this out and took care of the problem. Ken Yes, Hurrah! And skp preview as well! (Although, for some reason, not for all of them).

Forgot to mention its difficult to reset the axes accurately without seeing them to right click them. thanks, chad

Got it fixed installed a new version of SU.

Yes, the Save_As in the CAD app could go back, even to r2000, the DWG's geometry/layers etc imported into SketchUp will be unaffected by that... but newer things like DC's, which could break it, are not supported in those earlier DWG formats, so they are avoided...

have you tried 'Export 3d' >> 'dxf' this will export as 'vector' rather than 'raster' john

agreed, dave. came in useful for creating an arrary of vertical curtain wall louvres w/ random offsets! error occurs w/ edges both hidden and not hidden.

Hi everyone, had another of this crash this morning, new files send as Bug splat and upload to googledrive as a new folder. Also I'm attaching a screenshot of how the model was saved after the crash. A moulding panel I was rotating, end up several meter from the rotating point (yellow dot). If anyone could bring some light to this, I will very appreciate. Thanks! [image: MI1Z_Captura.JPG]

What render are you trying to do ? What renderer ? More info needed please...

Just following up........I looked to the Trimble SU........Knowledge center.......(search) HLR. As I suspected.......the HLR print (output) option is vector based output. So...somewhere......somehow.....the black dimension boxes are cause/effect of......?? SU dimension text fails to convert/display as vector? User "success" in printing to HLR (w/o blacked out dimension text) .....most likely does not contain any vector based attributes. (IOW: print driver is really printing as .jpg/or other "image" file) I do not have an answer/solution.......but to say the HLR print option......when used with a vector capable print driver.......will unfortunately create the blacked out text/dims. as depicted above. Best, C [image: 1FqZ_TrimbleSU_HLR.PNG]

@driven said: @Steve, have you ever ran this on SU? https://developer.apple.com/library/mac/documentation/GraphicsAnimation/Conceptual/HighResolutionOSX/Testing/Testing.html#//apple_ref/doc/uid/TP40012302-CH6-SW1 john john, I messed some with the Quartz debugging tool back when Fredo's view.draw_text was discovered to be too tiny on retina, but a) found no way to change what SU does in that method, and b) never thought it had anything to do with flaky cursors so didn't dig deep into that. The annoying thing is that the cursor issues though not infrequent are not consistently repeatable. Sometimes they happen, sometimes not...I've never detected a specific trigger. Steve