[Plugin] TIG-export_SKP_by_layer.rb
-
TIG,
I am having trouble finding out where to locate and how to actually use the plugin...
any help would be much appreciated!
thank you,
Stephen
-
Stephen, does this answer your question?
Example 1. The location where the ruby script needs to be copied to.
Example 2. How to execute the ruby script (ignore the short-keys for the "Window" menu
as these are my custom shortcut key assignments).
-
I was going to say much the same... but thanks to John !
His explanation is better than mine anyway
-
Thank you TIG! I didn't knew i need this one until i read the description! Life saver, really
-
Originally I did that approach and it was not recognizing it... now on a monday morning it works... Figures! haha
The program must have checked out for the week/weekend Friday...
Thank you for the timely response,
Stephen
-
Thanks TIG!
-
Tig,
Just a quick question regarding your Layers to SKP plugin:
I have been searching for some ways to get SKP into Revit, and have a couple workflows that I am able to use well currently, however I am trying to just find some quick optimizations and found your old plugin! I am currently using SKP Pro 2015, and just tried your script and this is what the ruby console spat back at me:
TIG.export_SKP_by_layer
Exporting from...
//Mac/Home/Desktop/SKP2RVT/RVT2SKP.skp
as//Mac/Home/Desktop/SKP2RVT/RVT2SKP-Layer0.skp
Error: #<TypeError: reference to deleted Layers>
C:/Users//AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TIG-export_SKP_by_layer.rb:43:inpurge_unused' C:/Users/*****/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TIG-export_SKP_by_layer.rb:43:inblock in export_SKP_by_layer'
C:/Users//AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TIG-export_SKP_by_layer.rb:40:ineach' C:/Users/*****/AppData/Roaming/SketchUp/SketchUp 2015/SketchUp/Plugins/TIG-export_SKP_by_layer.rb:40:inexport_SKP_by_layer'
<main>:in<main>' SketchUp:1:ineval'I am using a Mac Laptop with Windows 10 on Parallels if that info helps at all? Anyway, it just creates the first "RVT2SKP-Layer0.skp" file and then stops... I am wondering what is going wrong?
If we can get past this hurdle, one feature I have been looking for in this whole deal is to make sure that whatever files are saved, are saved in SKP8 format
Let me know if you can see where I am erring...
Thanks! -
Updated v2.0 now available.
See first post full full chanage-log: http://sketchucation.com/forums/viewtopic.php?p=422953#p422953@unknownuser said:
v2.0 20171105
Now compatible with newer versions of SketchUp.
Exported SKPs are put into a 'SKP_by_layer' subfolder with the model.
Optional SKP version argument added to the command*.
Unused Components, Layers & Materials are properly purged from the SKPs.
SketchUp Plugins | PluginStore | SketchUcation
SketchUp Plugin and Extension Store by SketchUcation provides free downloads of hundreds of SketchUp extensions and plugins
(sketchucation.com)
-
So, everything is working beautifully on the simpler SKP2RVT file, but something is happening where the more complex SKP2RVT2 file is crashing Sketchup and aborting the process after the Layer0 begins to save. I am attaching both files below.
-
Thanks for the feedback.
At first I thought it was because in the more complex SKP Layer0 is the current layer, BUT it contains NO 'raw' entities using that layer...
You can always try and save an entirely empty SKP... but is not valid and messes up !
However, I trapped for this by adding a single guide-point at the origin, if the SKP has no entities.
BUT this still doesn't work !
I added extra 'Garbage-Collection' but it hasn't helped.I also noted that 'OFF' layers export, but they are not visible - so I fixed that side-issue !
I also saw that your Styles varied - material by material v. none ... but that makes no difference.
So at the moment I am at a loss to see what's up...
I'll publish v2.1.
Watch out for it...Please install that.
I expect it'll still BugSplat on some of your files...
Can you submit the BugSplat to Trimble, add an email and also email your full details and the problem SKP and my latest RBZ [with my email-address too] so they have all of the details - they might have some ideas... V2017 is full of new issues that developers are not always aware of... -
I'm currently troubleshooting things on my end as well, I simplified the model by removing all instances of components, nested layers inside components and groups (not ideal, but workable; ideally I could keep a "window" component that is LayerWhatever but have SKP-GLASS and SKP-WINDOWS inside so that if I change one instance of windows in the model, they all update as well...) until I explore more, I can at least have glass groups on SKP-GLASS... I am going to try out 2.1, and start slowly adding complexity again until I break it, but what I also did that seemed to help the most (oddly) was remove all ifc tags, group names, and component definitions? I am attaching the SKP2RVT2 working file below.
One thing I did notice was that for whatever reason in Revit, whenever I brought in the linked SKP, the other layers were still being pulled in (SKP_FLOORS had SKP_DOORS, WINDOWS, etc.) at least on the first linking if I did not choose specify layers to link inside Revit, again, not a problem, I just make sure to only bring in the layers associated with the link, just more FYI.
I will play around with this all tonight.
-
Here's v2.1...
https://sketchucation.com/pluginstore?pln=TIG_export_SKP_by_layer
It fixes a few issues in the previous post - however, I suspect that sometimes it might still BugSplat !
Please test and feedback - submit splats too... -
TIG, still getting problems here. On more complex production files, the routine ends up bogging down hard, prompting the option to abort the script. On "nested" layers geometry is butchered so that solids are not retained, only bringing in line segments. At least named components in layers do work. I am attaching a "simple complex" file that does work as far as finishing the routine, however, on a large scale file, the process bogs down to untenable, and I have yet to sit through a full cycle of the script running...
Advertisement