2013 crashes everytime i use fredo6's bz tools?
-
I wasn't suggesting that you remove SU8 at all. I must have misread your previous post.
The current version of BZ_Spline with the current version of LibFredo6 works fine on my Mac and for others. Is it possible that it's a folder permissions problem? The load error you posted has nothing to do with Fredo's tools but are you still getting that error?
-
well.
I trashed the utilities plugin and got rid of the load error message i included in my original post.
i've tried re-installing the plugin.
i ran repair permissions in my disk utility.
all without success. not sure how to proceed at this point, but thank you everyone for your suggestions and ideas. will report back if i solve my problem. till then back to 8.
-
Does repairing permissions set them back to the factory defaults? If so, you don't want that.
-
I have the same problem. SU2013 crashes many times with this version of the plugin. I went back to a version that I have for SU8 that is dated 2008. It works perfectly without any crashes.
It is a repeatable error:
Sequence of Steps to Crash;
1 - Select Polyline divider
2 - Set Length to 5' for spacing
3 - Set one point
4 - Set second point
5 - Line drawn with intervals
6 - Start to set third point
7 - Pause
8 - Crash -
@didgtecture
Have you installed all of the latest versions of these tools AND the required Lib - these were updated to suit v2013 some weeks ago.
Have you set your permissions properly for the v2013 Plugins folders etc 'FULL read/write for all?].
Have you set SketchUp always to run as admin [Win7 etc]?
Do you have plugins like Vray beta loading, which are known to cause clashes/crashes ?? -
@tig said:
@didgtecture
Have you installed all of the latest versions of these tools AND the required Lib - these were updated to suit v2013 some weeks ago.
Have you set your permissions properly for the v2013 Plugins folders etc.
Have you set SketchUp always to run as admin?
Do you have plugins like Vray beta loading, which are known to cause clashes/crashes ??I updated this plugin and the libtranductor plugin. The plugin crashed 2013 repeatedly many times, like 10 times within 30 minutes.
I am running on OSX, so there are no settings like on Win for admin or permissions. I have Maxwell and I disabled that to test and no change. There are two plugins that I have that have crashed SU and that is this one and a control point plugin that caused a strange crash. That is all.
-
Please update your profile to include your OS and SU version.
There are permission settings for the Plugins folder on Mac OSX, at least the most recent two versions.
Did you update the entire LibFredo6 files? You didn't say.
-
@dave r said:
Please update your profile to include your OS and SU version.
There are permission settings for the Plugins folder on Mac OSX, at least the most recent two versions.
Did you update the entire LibFredo6 files? You didn't say.
Yes, I am using the Sketchucation plugin store to manage plugins so I update from there.
I updated the Fredo libs, and the plugin to the newest that is available from there.
What should the permissions be set to other than for my user read and write, fetching read only, and everyone read only?
BTW - I just autoinstalled again all of Fredo's plugins that I use from Sketchucation plugin store. Most are updated from April 2013 which is before the release of SU 2013.
-
I would set your Plugins folder's permissions to be FULL read/write for everyone ?
Fredo updated some of his tools before to the release of v2013 - in anticipation of its impending changes...
The Fredo tools' files AND FredoLib etc at the SCF PluginStore are all the latest versions, and will work with v2013 and earlier too...
Note that v2013 uses a different default Plugins folder location to v8 - are you doing this right?
You should have FULL permissions to it as it's now in your personal 'users-path'
What does this code return for you - Ruby Console copy/paste+<enter>:
Sketchup.find_support_file('plugins') -
@tig said:
I would set your Plugins folder's permissions to be FULL read/write for everyone ?
Fredo updated some of his tools before to the release of v2013 - in anticipation of its impending changes...
The Fredo tools' files AND FredoLib etc at the SCF PluginStore are all the latest versions, and will work with v2013 and earlier too...
Note that v2013 uses a different default Plugins folder location to v8 - are you doing this right?
You should have FULL permissions to it as it's now in your personal 'users-path'
What does this code return for you - Ruby Console copy/paste+<enter>:
Sketchup.find_support_file('plugins')I know where the 2013 plugins are located.
/Users/xxxx/Library/Application Support/SketchUp 2013/SketchUp/plugins
When I look at the info for the plugins folder it is set to ready and write for everyone but when I look at individual plugin folders within that folder these are not set to that. Do I have to set each file and folder to this?
-Okay, I applied those settings to all enclosed items.
This should be done when Sketchup installs. Does everyone do this when they upgrade to the next version?
-
I only needed to set permissions for the Plugins folder. I have had no reason to touch any of the folders inside of that folder. Perhaps if you had set the permissions for the folder up front before adding the plugins to it, you wouldn't have had any problems.
-
@dave r said:
I only needed to set permissions for the Plugins folder. I have had no reason to touch any of the folders inside of that folder. Perhaps if you had set the permissions for the folder up front before adding the plugins to it, you wouldn't have had any problems.
The problem is unless you have encountered this problem, the general user would never know about this.
This is the first time, I have had SketchUp crash like this that required a search for an answer.
-
@digitecture said:
The problem is unless you have encountered this problem, the general user would never know about this.
This is the first time, I have had SketchUp crash like this that required a search for an answer.
I'm not scolding. It's true, you wouldn't.
On the other hand, a huge number of the posts in the original thread for the plugin cover this exact problem. This also shows threads for a number of other plugins. So the information is available. Fredo's RoundCorner plugin thread makes it clear in the first few lines. Maybe he could add that comment to his other threads as well.
-
Was there a solution? I have the same problem, Mac 2013pro, permissions, etc, reloaded - still crashes....The only plug in that does...Fredo6's loft tools do not, so I have an updated library, etc
-
Same question?
Also on mac ML with Sketchup 2013. BZ tools crash every time.
I went through all the suggestion in this and the plugin thread and unfortunately nothing helped.
-
@castromann said:
Same question?
Also on mac ML with Sketchup 2013. BZ tools crash every time.
I went through all the suggestion in this and the plugin thread and unfortunately nothing helped.
Do you get a crash too with my other plugins (like FredoScale, RoundCorner, ...)?
Fredo
-
no, not at all. everything else works perfectly fine.
-
I have the same problem in one of my 3 machines. they all run Mountain Lion, the latest SU and the latest Fredo plugins, but the crashes occur in only one of them.
-
@edson said:
I have the same problem in one of my 3 machines. they all run Mountain Lion, the latest SU and the latest Fredo plugins, but the crashes occur in only one of them.
What would be helpful is that you describe the context of the crash
- at startup or when drawing or when generating or when modifying
- which tool or all tools
- etc....
Fredo
-
@fredo6 said:
What would be helpful is that you describe the context of the crash
- at startup or when drawing or when generating or when modifying
- which tool or all tools
- etc....
Fredo
Ok, I played around with the different tools for some time each. Problem is: There's seems to be no pattern in when or which tool crashes. Sometimes first click into the canvas, sometimes some control points into the operation. It seems that each tool crashes equally probable.
Let me know if I can do anything else to find the cause of this?!
Advertisement