You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability to import the plugin from within the application is a nice touch for a non-technical stand-alone user, but in a school environment with hundreds of lab PCs used by a couple of thousand students, a zero touch approach to deploying apps and plugins is a must.
In Sketchup 2014, there was a plugins folder you could copy a plugin to and all users had access to a consistant experience.
In Sketchup 2015 the folder landscape and the way "plugins" are handled seems to have changed significantly. After installing the stl extension on a test machine, I searched against the various filenames to discover where the extension's files landed- and I came up empty.
Perhaps someone in the know could insert a bit of doco with the plugin files to explain mass deployment options would be a good idea.
The text was updated successfully, but these errors were encountered:
This request isn't specific to the STL plugin, so I would suggest you ask this on the official SketchUp forums[1] where some very expert users are more likely to see it.
The folder locations didn't change for SU2015. In SU2014 it was changed so that extensions where installed in the user folder in order to avoid permission issues.
To install extensions for all users you can manually install (extract) them to: C:\ProgramData\SketchUp\SketchUp 2015\SketchUp (Replace version number as appropriate.)
The ability to import the plugin from within the application is a nice touch for a non-technical stand-alone user, but in a school environment with hundreds of lab PCs used by a couple of thousand students, a zero touch approach to deploying apps and plugins is a must.
In Sketchup 2014, there was a plugins folder you could copy a plugin to and all users had access to a consistant experience.
In Sketchup 2015 the folder landscape and the way "plugins" are handled seems to have changed significantly. After installing the stl extension on a test machine, I searched against the various filenames to discover where the extension's files landed- and I came up empty.
Perhaps someone in the know could insert a bit of doco with the plugin files to explain mass deployment options would be a good idea.
The text was updated successfully, but these errors were encountered: