2017 crashes constantly
-
I'm on windows 10, installed sketchup yesterday, and today it crashed simply opening the blank program. Not happy.
-
@bobrsta said:
The main ruby I have is the 3Skeng modules.
Did you send them the file to see if it is related to their plugin?
Does it crash if you disable it?
125MB is not so large but if you have a style enabled that draws on GPU resources it could chug a bit.
-
What graphics card? Crashes on startup have generally been traced to graphics drivers. Try updating the drivers.
On Mac there's not much control over graphics drivers because they are pushed with OSX updates. What version of OSX are you running?
-
MacBookĀ Pro (15Ā pouces, 2016)
Sierra 10.12.4 (16E195)
2,9 GHz Intel Core i7
16 Go 2133 MHz LPDDR3
RadeonĀ ProĀ 460 4096 Mo
IntelĀ HD GraphicsĀ 530 1536 MoSketchup pro 2017
Plugin Thea RenderLot of crashes and often force to quit the application
-
@dave r said:
Crashes on startup have generally been traced to graphics drivers.
... and the used plugins. For evaluating this try if disabling them one-by-one at "SketchUp > Extension Manager" fixes the crashes and identifies the causing plug:
-
Sometime technic kills the technic!
Does the application crashes with a simple cube and a 3sKeng tube?
-
Yea, apparently there is an issue in 2017 with 3Skeng causing crashing in app. I just learned that this morning from Hans over at 3Skeng. That plugin is such a huge part of my workflow that I can't see working with out it. Maybe I just go back to 2016, not near as many issues there.
Thanks for weighing in.
Bob
@sketch3d.de said:
@dave r said:
Crashes on startup have generally been traced to graphics drivers.
... and the used plugins. For evaluating this try if disabling them one-by-one at "SketchUp > Extension Manager" fixes the crashes and identifies the causing plug:
-
I'm one update behind on Mac OS Sierra. I could try updating that, see if anything changes.
Another odd behavior has surfaced this morning
I am working on a "wing" of the house that is rotated at 63.4 degrees to the rest of the structure. So, I have temporarily rotated the drawing axis to facilitate. I'm having a devil of a time drawing rectangular objects to this new axis orientation. I need to draw the walls surrounding the room, and I keep trying different approaches but they are all "breaking down", as in, becoming problematic "solids". Right now, I'm trying to use the "outer shell" tool to just join different segments of the walls I've drawn. I select one particular wall and I get a volume in the relevant box on the entity info window. ThomThom's solid inspector shows it as a solid as well. Yet, when I go to perform the outer shell operation, the tool tip on this wall object says "not a solid"! What in the world??
Phew, thanks, Dave. Its at least comforting that you, and the rest of the group here weighing in, are out there somewhere in the night helping me to remain sane! Haha
Bob
@dave r said:
What graphics card? Crashes on startup have generally been traced to graphics drivers. Try updating the drivers.
On Mac there's not much control over graphics drivers because they are pushed with OSX updates. What version of OSX are you running?
-
Apparently, there is some conflict in the plug in. Just learned that this morning. Apparently, they're (3Skeng) waiting on info / analysis from the SU team at Trimble.
So, when do we get "D'oh" version 2, Rich?! Great little guide, was very happy to get that a the last confab in Steamboat.
Bob
@rich o brien said:
@bobrsta said:
The main ruby I have is the 3Skeng modules.
Did you send them the file to see if it is related to their plugin?
Does it crash if you disable it?
125MB is not so large but if you have a style enabled that draws on GPU resources it could chug a bit.
-
@unknownuser said:
Maybe I just go back to 2016, not near as many issues there.
Why change something that works fine ?
Keep old version(s) is a good habit!
-
Probably good advice! I always think there's some new whiz bang feature that I can't live without...
@pilou said:
@unknownuser said:
Maybe I just go back to 2016, not near as many issues there.
Why change something that works fine ?
Keep old version(s) is a good habit!
Advertisement