Fredo6 crashing SU Pro 2014
-
Hi, maybe this should be in the newbie forum, but I figured here would be a smidge more specific.
I've been going through hours of grief trying to convert an .ai image into a 3D object. I ended up converting it to .dxf successfully (eventually!) and get the basic 2D shapes into SU without any problems. However I've had untold horrors once I push/pull everything into different heights with various faces being reversed or not in a seemingly random way. I figured there must be tiny gaps, so started Welding all the edges but that became incredibly time consuming. Then I stumbled on Fredo6 Edge inspector which beautifully put lovely pink circles (polygons?) around all the gazillions of non-welded gaps (?) that I was trying to fix.
However, whenever I choose FIX, the whole thing crashes: KERN_INVALID_ADDRESS at 0x00000000e2116abe
I'm on a MacBook Pro running OSX 10.9.4 with SU Pro 2014 (14.0.4899). It makes no difference if I select a small area - say a single shape - and run the fix on it, it still crashes. I then tried to use the Joint Push/Pull tool to see if that would skin the cat slightly differently, however then it crashes with a similar Kernel error.
The extrude push/pull has better manners and just throws the following error without killing SU:
Date: 04-Sep-14 00:38:53
An error occurred in Extrude Push Pull
Error in generation of the geometryundefined method `smooth?' for nil:NilClass
JointPushPullGeometry.rb:: 1107 -- block in geometry_coplanar_edges_overhang
JointPushPullGeometry.rb:: 1105 -- each
JointPushPullGeometry.rb:: 1105 -- each_with_index
JointPushPullGeometry.rb:: 1105 -- geometry_coplanar_edges_overhang
JointPushPullGeometry.rb:: 354 -- block in geometry_robot_erase_coplanar_edges
JointPushPullGeometry.rb:: 352 -- each
JointPushPullGeometry.rb:: 352 -- geometry_robot_erase_coplanar_edges
JointPushPullGeometry.rb:: 214 -- robot_call_action
JointPushPullGeometry.rb:: 177 -- geometry_robot_exec
JointPushPullGeometry.rb:: 160 -- geometry_robot
JointPushPullGeometry.rb:: 75 -- block in geometry_execute
Lib6Operation.rb:: 317 -- call
Lib6Operation.rb:: 317 -- step_geometry
Lib6Operation.rb:: 278 -- block in yield?
-e:: 1 -- callAny and all help gratefully received!
-
You must have a complication in the model, maybe due to the import of DXF.
Then acting on the geometry, scripts may end up crashing when trying to update it.The best is to post the model so that we can have a look.
Fredo
-
It sounds like your model has issues that are causing SketchUp to crash when you run the fix routine in Edge Inspector. You could confirm this by running Fix on a simple model. If the problem is due to Edge Inspector, you should still see the crash. Otherwise I would be looking at the model.
Perhaps you can simplify the model to identify what geometry is causing the problem. Or maybe if you scale the model up by perhaps a factor 100, the tiny gaps you've created can be filled during the fix. Maybe you could share the model so we can see what you've got to start with.
-
Thanks for the help guys. I've spent the morning removing all the other plugins to see if there was a clash - but to no avail, so it is helpful for you to have zoomed in so quickly on the model as the problem. I scaled it up by 100 and ran the tool - at first it didn't detect any gaps, but then I bumped the threshold up to it's max and it only picked up 3 or 4, which seemed good enough to test. But just as the fix was nearly finished and my hopes were soaring - Bug Splat!!
Here's the model, which is still just a 2D jobby at this stage - one I'm slowly (?) growing to hate
Thanks again for such quick, pertinent, friendly suggestions.
-
Test... my reply and upload don't seem to have materialised.
-
@blippy said:
Test... my reply and upload don't seem to have materialised.
A couple of first posts by new members have to be approved by a moderator.
-
Ah! That explains it. Thanks.
-
I tried the model but got no bugsplat.
The model is clearly full of defects, in particular very small edges (some below 0.01 mm). So it is quite interesting because it pushed EdgeInspector to the limits.
This helped me to find a few problems in EdgeInspector which I have fixed and will publish in a new release.
In the meantime, here is a cleaner version of the file. I scaled it up by x10 before using EdgeInspector.
By the way, have you tried thomthom's CleanUp plugin on your model, with the "repair Edges" feature?
Fredo
-
Do you get the BugSplat dialog or the Apple crash dialog?
-
Wow - thanks Fredo!! That all seems to be behaving itself now. Yes, I've tried Thomthom's CleanUp - but I couldn't detect any improvements with it - although that may have more to do with me having little idea of what to expect/look for. I've been trawling the plugin world fairly intensively trying to find something that would work and your magical Edge Inspector was the closest I got to a solution. So, many thanks for your plugin(s), and many thanks for being generous enough to also help me individually with my problem. I'm sort of a little bit glad I managed to inadvertently given you a challenge that made it all a little more worth while (hopefully)
Thanks again!
-
-
Did you submit the BugSplat? If you did - and provided some description, name or email, then I can use that to look it up and perhaps get any idea of where it crashed.
(In general, please submit any BugSplats - even the ones you have sent before. For first time crashes, please include some info about what happened prior to the crash.)
-
@tt_su said:
Did you submit the BugSplat? If you did - and provided some description, name or email, then I can use that to look it up and perhaps get any idea of where it crashed.
(In general, please submit any BugSplats - even the ones you have sent before. For first time crashes, please include some info about what happened prior to the crash.)
Oh, ok, I didn't realise there was any action I could do - certainly no menu items or submit reportbuttons that I noticed... is there a log I can post that would be helpful?
-
You have raw geometry on the wrong layer.
Move it to layer0 and your model will work. -
@box said:
You have raw geometry on the wrong layer.
Move it to layer0 and your model will work.Ooooh... and there was I wondering just last night what all this layer business is about in sketchup! Obviously I can have a dig to find out more, but if you are able to point me to a nice SU Layers 101 I'd appreciate it. And hopefully it will tell me how to move raw (as opposed to cooked?) geometry!!
This process is proving far more educational than I imagined
-
Here's most of what you need to know about using layers in SketchUp.
http://help.sketchup.com/en/article/38572 -
@dave r said:
Here's most of what you need to know about using layers in SketchUp.
http://help.sketchup.com/en/article/38572Ah, very nifty. Thanks again!!
-
@blippy said:
Oh, ok, I didn't realise there was any action I could do - certainly no menu items or submit reportbuttons that I noticed... is there a log I can post that would be helpful?
The BugSplat dialog has a button to Send. And a textarea to enter description.
-
@tt_su said:
@blippy said:
Oh, ok, I didn't realise there was any action I could do - certainly no menu items or submit reportbuttons that I noticed... is there a log I can post that would be helpful?
The BugSplat dialog has a button to Send. And a textarea to enter description.
That hasn't been my experience of BugSplat. Whenever SU has crashed I've only been aware of BugSplat when I cycle through my open apps (squiggle-tab) and the BugSplat icon (very cute btw) is in the list. When I select it there is no dialog or text box, just the generic OSX menu with zero functionality - certainly nothing like what you describe.
-
That's what I get on my Mac when SketchUp crashes, too. Thankfully it is extremely rare but I am never able to send in those splat reports. Some folks do get the Splat window on Mac, though. No idea what's different about ours though.
Advertisement