[Plugin] RichSection V0.5.8 UPDATED march 2015
-
Yes,it's a temple for new year,it attracts much people to ring the bell on the three floors,it is supposed to be a kind of memorial tower.
However,in some complex models,the plugin could give section lines but never fill the hole,I don't know is there some problem has not been solved? It seems to work right.
-
@ladcwei said:
However,in some complex models,the plugin could give section lines but never fill the hole,I don't know is there some problem has not been solved? It seems to work right.
Missing faces also happens with
TIG's Section Cut Face. He has done a lot of checks on it but there can still be situations in a model where a face can be missing without reason. 
-
@unknownuser said:
Cant get it to work like in the videos....it just works as sketchup native section cut, also sketchup crashed a few times (bugsplat)....but i love the intention. It would save me the time to go put in hatches in my layout documents
Hallo,
To know what is going on first exclude this :- ...as native Sketchup : Did you used groups or components ?
- Did you activate the plugin? (Menu Windows/preferences >> extensions). Is there RichSection-panel and a RichSection menu ?
- Open de Ruby console (open the 'Windows' menu, and then click 'Ruby Console'): do you have any errors here while placing RIchSection cuts?
- Bug Splat : What other plugins are installed? There can be incompatibility : see first post. Unactivate all other plugins, restart SU and test again the RichSection plugin. This should work !
I see you have SU 8 installed. I suggest to install SU2013 make (you can keep SU8). It faster and much more stable.
Then install (first and only) the RichSection plugin. It should work ! If it is the case, instal the other plugins, and test after each installation.Please tell me if you got it working
-
@ladcwei said:
Yes,it's a temple for new year .....
However,in some complex models,the plugin could give section lines but never fill the hole,I don't know is there some problem has not been solved? It seems to work right.Nice to have some feedback. B
Beautifull and complex models
RichSection and also TIG's plugin use a method of the Ruby Sketchup-API (entities.intersect_with).
Indeed ArCAD-UK This method handels the Intersection and automatically creates faces with speed. My experience is that the method can't handel very small faces Sometimes you can avoid this limit by scaling the model (x100 ... x1000). -
My missing faces were in repeated components and should have formed a 50 x 100mm face in a rectangular box, so size wasn't the issue. The final solution in that case was to delete the failing group and create a fresh box. TIG spent time updating his plug using some of my models but I can still get face errors with abutting groups for no obvious reason. If you and TIG are both seeing this then you may need to get Trimble to look at the API.
-
@unknownuser said:
Hi Joel
Supposing
-
Model : you used layers L1 and L2
-
Model : you applied the following materials to groups and components : N1 and N2
First possibility : -
Model : existing materials in library 'in model' : #L1.... / NOT existing materials : #L2
-
RS-options : prefix = #
-
RS-options : default material = #default
-
RS-options : section material = prefix+layername, default
-
RS section materials for a group or component in layer L1 : #L1
-
RS section materials for a group or component in layer L2 : #default (because #L2 doesn't exist)
2nd possibility : -
Model : existing materials in library 'in model' : #N1.... / NOT existing materials : #N2
-
RS-options : prefix = #
-
RS-options : default material = #default
-
RS-options : section material = prefix+materialname, default
-
RS section materials for a group or component with material N1 assignd: #N1
-
RS section materials for a group or component with material N2 assignd: #default (because #N2 doesn't exist)
Got it
Thanks...I managed to get both material names and layer names working (apparently I can't use default material names straight from the SU library; I have to change them for them to work), but I still don't understand the difference between the two richsection options highlighted in the attached image:
Thanks!
Joel
-
-
@ivreich said:
Thanks...I managed to get both material names and layer names working (apparently I can't use default material names straight from the SU library; I have to change them for them to work), but I still don't understand the difference between the two richsection options highlighted in the attached image:
Thanks!
JoelIt's a matter of priority
Supposing- Model : you used layers L1 and L2
- Model : you applied the following materials to groups and components : N1 and N2
- Model : Group1 in layer L1 and material N1 (assignd to the group)
- Model : Group2 in layer L2 and material N2 (assignd to the group)
First case :
-
Model : existing materials in library 'in model' : #L1,#N1,#N2....
-
Model : NOT existing materials in library 'in model' : #L2
-
RS-options : prefix = #
-
RS-options : default material = #default
-
RS-options : section material = prefix+layername, prefix+materialname, default
-
RS section materials group1 (L1,N1) : #L1 (priority for prefix+layername)
-
RS section materials group2 (L2,N2) : #N2 (#L2 doen't exist)
2nd case : -
RS-options and model as before, except:
-
RS-options : section material = prefix+materialname, prefix+layername, default
-
RS section materials group1 (L1,N1) : #N1 (priority for prefix+materialname)
-
RS section materials group2 (L2,N2) : #N2
Like for standard materials : nested groups can inherit the RichSection-material of a parent group
-
@arcad-uk said:
My missing faces were in repeated components and should have formed a 50 x 100mm face in a rectangular box, so size wasn't the issue. The final solution in that case was to delete the failing group and create a fresh box. TIG spent time updating his plug using some of my models but I can still get face errors with abutting groups for no obvious reason. If you and TIG are both seeing this then you may need to get Trimble to look at the API.
My experience is that SU (and his ruby method 'intersect_with') can't create an intersection-face if:
- small faces; small is relative : it depends of the extends of the model
- to many entities (edges, faces) in the same context (context = in the same group or component)
- to many (complex) loops to create in the same context
ArCAD-UK, for the repeated 'small' components, does SU recognizes them as a solid? What are the dimensions of the model?
Maybee jou can send me the problematic skp-file (private if necessary, I will only use it for testing....) -
This is unbelivable! Thank you soo much pgarmyn for sharing this.
It is just what i have been searching for for years. Now sketchup could be finally used as a proper drawing tool, without worrying are cetions up to date, visible to other scenes etc.I downloaded it yesterday via sketchucation plugin manager and it says it's expired back in march 2014?.
https://dl.dropboxusercontent.com/u/35033714/expired.jpgI thought i should report this.
Thank you again pgarmyn! -
@mladen90 said:
This is unbelivable! Thank you soo much pgarmyn for sharing this.
It is just what i have been searching for for years. Now sketchup could be finally used as a proper drawing tool, without worrying are cetions up to date, visible to other scenes etc.I downloaded it yesterday via sketchucation plugin manager and it says it's expired back in march 2014?.
https://dl.dropboxusercontent.com/u/35033714/expired.jpgI thought i should report this.
Thank you again pgarmyn!Yes, thanks for reporting this.
Indeed this (full) DEMO expires on 1 march 2014. I will replace it by a free (limited) and a FULL version. But strange that you have this message.
Are you living in the future Did you changed the date of your computer
Is the licence-file in de directory (plugin/PiGa_RichSection/RichSectionLicense.rb)Let me know....
-
I haven't change my date on PC.
I have resources folder, RichSection.rbs and RichSectionLicence.rb in folder you mentioned.I have had experienced similar thing with RealSection, but that was common problem ( It truly had expired and nobody continued to work on it). I guess RichSection doesn't use any of RealSections libs? Could this be the problem?
Thanks for your quick reply.
-
New video added to the first post... 
-
@mladen90 said:
I haven't change my date on PC.
I have resources folder, RichSection.rbs and RichSectionLicence.rb in folder you mentioned.I have had experienced similar thing with RealSection, but that was common problem ( It truly had expired and nobody continued to work on it). I guess RichSection doesn't use any of RealSections libs? Could this be the problem?
Thanks for your quick reply.
Strange, you are the first having this problem after 380 downloads!
The RichSection plugin can't interfere with other plugins.
When did you got this message. Directly after putting the first RichSection? .... When updating?Can you switch 'on' logging in the menu (plugins/RichSection/settings) and open the ruby console.
What is printed in the Ruby console, when you place a RichSection... -
Wow! Astonishing new video. Just what I imagined it cold be done with RichS.
Considering expiration problem. I did enable logging.
It happens when I try to make real section (via menu-bar or right click).Here is the log:
---------------------------onElemAdd : Sketchup::SectionPlane
toolRScreate_part2 :
toolRScreate_part2: createRS :
Plugin: RichSection
Copyright: 2013X, All rights reserved for RichSection plugin : Name, code and functionality are the intellectual property of the author. Distribution, reproduction or integration of code or functionality, even partly, is only permitted with the explicit permission of the author
Version: V00.01-2013.11.17-18:00 DEMO_________________________
:
proc createRichSection :
licensefile found : C:/Program Files (x86)/SketchUp/SketchUp 2013/Plugins/PiGa_RichSection/RichSectionLicense.rb
licensed for computer: : any
licensed for MAC-adress: : any
licensed for version: : V00.01-2014.11.17-20:00 DEMO
licensed until: : Sat Mar 01 00:00:00 UTC 2014
license type: : DEMO, valid until 2014-03-01
license to (name): : Everybody
license to (mail): :
key1: : SoftwarekeyForTheDemoLicenseUntil-2014-03-01
key2: : fz1njmunn7pfa45t9o1bv0yatdvaln7wvrpl8oitml3301vizcszy0cjyepk1r14mkve
Faces : 12
Instances : 1
Definitions : 1
@modelcomplexity : 0
thisRSversion = V00.01-2014.11.17-20:00 DEMO? : V00.01-2014.11.17-20:00 DEMO
License VALID :I hope that this help.
-
thank you very much for this fantastic plugin.
On my computer, now shows the same error message, because the plugin expired.
you can fix that? thank you very much
-
I was about to check the models TIG worked with and got the same EXPIRED DEMO message.
-
@unknownuser said:
The RichSection plugin can't interfere with other plugins.
But sems at least 2 plugins "windowizer.rb" and "wxSU.rb" bugsplat it!
-
@unknownuser said:
But sems at least 2 plugins "windowizer.rb" and "wxSU.rb" bugsplat it!
As i said before, every method, variable in the RichSection plugin is declared in the RichSection namespace.
As Windowizer ads a base method and extends SU classes, it interfears with ALL the SU plugins!
I didn't look at the wxSU code..... -
@pgarmyn said:
@emerald15 said:
I use RichSection to great effect. I really like all the additional optional colours, line types & infills.
May we see the result
Here's the section part of the drawing. Having all the none visible objects shown in dashed lines really helped.
-
[highlight=#ffff00:e4viin5e]:bounce: UPDATED, but probably not yet on the plugin store. (Need time to find out if I can do this by myself... )
[/highlight:e4viin5e]
Advertisement