Plugins Not Compatible with SU2015-64bit
-
@pixero said:
I get this when trying to start SU2015,64bit with Julia Eneroths Texture positioning plugin installed:
...
It's soo good. Please fix. :bounce:version = "1.0.3" from EW warehouse works...
john -
@pixero said:
I get this when trying to start SU2015,64bit with Julia Eneroths Texture positioning plugin installed:
That looks to be related to Ruby 2.0 - meaning SU2014. What version do you have?
-
@tt_su said:
@pixero said:
I get this when trying to start SU2015,64bit with Julia Eneroths Texture positioning plugin installed:
That looks to be related to Ruby 2.0 - meaning SU2014. What version do you have?
What version of what?
I have both 2014 32 bit and 2015 64 bit latest versions.Edit. Do you mean her script?
I downloaded with Sketchucation tool I believe.
Will check version tomorrow. -
the version is in the error
C;/ProgramData/SketchUp/SketchUp 2015/SketchUp/Plugins/ene_texturepositioning.rb;48; syntax error, unexpected tFLOAT, expecting keyword_end ex.version = "1.0.1"
sorry, I wasn't clearer, that's why I pointed to the EW version, which is 2 versions higher 1.0.3
john
-
Now I've removed the old version and reinstalled 1.0.3 and the error message is gone.
Still nothing happens when I try to use it.
Not even errors in the console.
I have it installed in: C:\ProgramData\SketchUp\SketchUp 2015\SketchUp\Plugins -
Why did you install it there?
The default location is "C:\Users\YourUserName\AppData\Roaming\SketchUp\SketchUp 2015\SketchUp\Plugins"
If you use the Install button on the Extension Warehouse from within SU it install to the correct folder and works in 2015. -
3skeng piping plugin doesn't work with SU2015
Edit: I've been in contact with the 3skeng Team and I've received an update of the 3skeng piping plugin, which - so far - works perfect with SU2015 64-bit...
-
Why is there two locations to install Plugins then if they are not the same?
In Sketchucation Plugin Store you can choose between the two.
(Even three if you count the preinstalled ones from Trimble.) -
Do you have twilight?, that is one plugin I know of that creates that folder.
-
@pixero said:
Why is there two locations to install Plugins then if they are not the same?
From the Installed 2015. No Plugins folder??? thread...
@dave r said:
The only Plugins folder you should be putting plugin files into is the one under User/AppData. The reason it is where it is has to do with Windows applying security settings to folders in Program Files which prevented users from installing files. This caused users all sorts of trouble because many didn't know about the security settings or how to change them. You can see evidence of that by looking through some of the longer threads in the Plugins folder. An endless run of questions about how to install plugins and claims that the plugins didn't work in this version or that. In most cases, the problem was found to be the security setting for the Plugins folder.
Now, the folder is not secured by the operating system. Also, between Preferences>Extensions>Install Extension, The Extension Warehouse and the Sketchucation Plugin Store, there's no need to directly access the Plugins folder under AppData. Those three tools will auto-install plugins at the click of a button.
In order for plugins to be installed by these tools, they need to be packaged as .rbz files. And plugins you download from the Extension Warehouse or the Plugin Store will come as .RBZ files. For files you might get from elsewhere such as Smustard, you can package them yourself so Install Extension will handle them. If you download a .rb file, use a zipping application such as 7Zip to create a zip file. Then change the extension from .zip to .rbz. If the file you've downloaded is already a zip file, just change the extension. It's easy and you don't have to go hunting for the folder.
And further...
@tig said:
DaveR just posted before me, and said much of this...
But as I had justed typed this I'll still post it anywayYou only place you actually need to install Plugins is in your default AppData User's Plugins folder, which is pre-made by SketchUp.
To find its path copy/paste+<enter> this in the Ruby Console:
Sketchup.find_support_file('Plugins')
BUT why do you need to look in it ?The EWH auto-installer, Preferences > Extensions > Install... button and/or the SketchUcation PluginStore dialog's AutoInstall button, all extract the contents of the RBZ files into there...
When SketchUp starts all RB/RBS files in there are auto-loaded.
Only you, logged in as your User-name loads those.Do NOT make a Plugins folder in the ProgramData path UNLESS you want to share plugins with other users on the same PC, as if that Plugins folder exists any RB/RBS files in there are also auto-loaded as SketchUp starts, this time for any user logged into that PC.
You cannot use the native Installer with that folder, however the SketchUcation PluginStore AutoInstall and Archive-Installer submenu item does see and offer it as an alternative 'custom-plugins-folder' destination.
It's pointless having the extra folder unless you want to share...There are a couple of other folders that you should NOT add files to, these are reserved for SketchUp's use: they often have little security permissions of mere Users [even Admins].
They are 'Tools', which contain some 'system' ruby stuff, and 'ShippedExtensions' - which, as its name suggests, contains some extension files [aka plugins] that come with SketchUp's installer - like Sandbox and DC stuff...In passing, you can also install your Plugins in any folder you like [provided you have security clearance], and link it into SketchUp's
$:
, so that its contents auto-load with SketchUp.
You need to install a tool into the default Plugins folder, like Fredo's AdditionalPluginsFolder, which does this for you... Read up on it if you feel you really need this level of sophistication...It is usually unwise to copy your plugin files from one SketchUp version's Plugins folder to another.
Many were updated to be compatible with v2014, and a few more recently for v2015.
So it's best to get fresh copies of all extensions/plugins whenever possible.
Also you need to ensure all related files and subfolders of files are copied - a mega-balls-up is waiting in the wings...
It may be that copying some over will do no harm, but if you subsequently get initial loading errors or just missing tools, then that's a sign of an issue, and time for an updated version...
If you have the SketchUcation Toolset then the PluginStore's dialog had a MySetup page which includes 'Bundles' - a tool which lets you let you duplicate/manipulate sets [aka Bundles] of plugins from an earlier SketchUp version and then make a bulk auto-installation of all of those into your newer SketchUp version's Plugins folder... -
OK. Got it, then I think the Sketchucation Plugin store should make it much clearer what to choose and why since now there are just two options. In 2014 I used the one in AppData. Now in 2015 I just clicked the other one without knowing that was not the best choice.
-
The thing is Pixero, that folder wouldn't exist if a plugin wasn't creating it.
The fault lies with .exe installers that choose to create that folder. -
I think the only plugin I installed prior to Sketchucation store was Thea.
Maybe have a talk with Thomasz about it? -
Thea4SU isn't using the old plugin folder...
-
Kim, it's not the old folder, it's a different one.
C:\ProgramData\SketchUp\SketchUp 2015\SketchUp\Pluginsthe old one was for example
C:\Program Files (x86)\SketchUp\SketchUp 2013\PluginsI don't know if thea does it, but Twilight certainly does create this other folder when it is installed.
-
@box said:
Kim, it's not the old folder, it's a different one.
OK - I see...
Thea4SU is located in the C:\ProgramData\SketchUp\SketchUp 2015\SketchUp\Plugins folder... -
So yes, it is the Thea installer in this case that has created the folder.
-
@box said:
So yes, it is the Thea installer in this case that has created the folder.
But just because the Thea installer is creating that folder, doesn't mean that it's wrong...
Thea4SU works correct from that folder...
If users then move other plugins/extensions to that folder, doesn't mean that they will work correct... -
Very true, I never said they wouldn't work there, just that it isn't the default location and is created by an exe. Tig explained it all in the post you posted.
-
We're on the same page in the same book...
Advertisement