Not much chnaged, but the read error happened in the early SectionTools version for V7.
You should not see this issue if you only used V6.
Ok, thanks
On the drawings I am working with (where I experienced this issues) i always used Rhino v6
Are you sure you did not open/save in Rhino (even if you saved as Rhino 6 file from within Rhino 7).
At any rate, if you experience this issue in an examples you can share, please send to me.
Sure 100%
That file is born in Rhino 6 and always been saved there.
Send me your mail and will send the file.
Thanks
Hi Luca, SectionTools should not change the layer “Lock” state of attributes like “Color”.
The one state that I can see is changing with update right now is to turn it back ON if it was turned off. Is that what you are referring to?
The clipping plane of the section is hidden by default in a locked section layer. Unless you manually make it visible by unlocking the later and use “Show” command, it remains hidden. That is said, if you indeed show the ClippingPlane, updates do not hide again. What is the expected behavior?
Hi @rajaa, I think we are misunderstanding this Point, Let’s start from Scratch.
Please follow my example:
- I have a file which has some objects on different Layers, say Layer A, B and C
- Each Layer contains some Objects
- Layer Visibility: A → ON / B → ON / C → OFF
- I place Section 1 including all currently visible object
- Section 1 contain geometry from objects contained inside Layer A & B
- Change Layer Visibility: A → OFF / B → OFF / C → ON
- Update Section 1
- Section 1 now display only geometry from objects contained by Level C discarding original Geometry from Level A & B
This is quite simplified but in real world I have many elements on several Layer and Sublayers.
What I think could be useful is adding an option to Section Tools which save layer state and store it along with list of object to be sectioned.
This way when I refresh my section it will contain all geometry from original Section.
Hope this is more clear!
Thanks

Section 1 now display only geometry from objects contained by Level C discarding original Geometry from Level A & B
Ok, I think get it now. By default, sections only calculate through visible objects only.
Let me rephrase your request:
- If specific objects are selected to be sectioned (not stCreate>Enter to select through all visible objects), you prefer that sections be visible even if you hide source objects or their layers at some stage. For example, you select an object from layer A, create the section, then hide layer A. Later, you update sections and you expect to continue to see the section through the object in the hidden Layer A?
Hi Rajaa, thanks for your prompt feedback,
this is not actually what I mean:
I would like Section tools to have an option to automatically save an “internal” Layer State during section generation and use that Layer State to control Object visibility during refresh.
When I ask for a refresh it is most likely that some changes happened (some object modified, some added and some deleted maybe).
This way I am sure that all geometry originally sectioned is included in the new updated section.
Do you typically use “Enter” to cut through all visible objects?
Yes,
I keep my objects deeply organized in Layers and sublayers.
Then adjust Layer visibility to have visible the objects I want to section.
Finally I place section through all currently visible objects.
I see.
How about when you add new objects that you’d like your section to cut through after the initial creation? How do you propose the workflow to add them?
The original design uses the “Enter” option to cut through all visible objects which allows using any new objects added to the scene followed by stUpdateAllSections.
If you’d like to cut through specific set of objects in your section, then it is best to select those when you run stCreate. Would that work for you?

“Enter” option to cut through all visible objects which allows using any new objects added to the scene followed by stUpdateAllSections.
This is best option for me but there is the need, before updating, to restore same Layer visibility as initial section. This should be managed internally by section Tools.
Does this has a sense for you?
I am wondering why there is not much feedback from other users:
Section Tools is actually the only “dynamic” tool which could help managing layout and technical drawings.
Is it posted in the wrong way?
Luca,
There is the LayerState panel where you can save your layer state and be able to restore or update anytime. You can save one for each section. Would it work for you?
I think Luca is asking that (as an option at least) the Section, when it is first set up, is bound to the Layer State in force at the time. The LS would “own” the Section, if you like. Restoring that Layer State at a later point in time would also restore the Section settings. I think…
That would mean nesting the Section Tools within the Layer State panel?

Luca,
There is the LayerState panel where you can save your layer state and be able to restore or update anytime. You can save one for each section. Would it work for you?
I use already LayerState but what I am asking Is Sectiontools to be able to manage this.

That would mean nesting the Section Tools within the Layer State panel?
I do not think this to be necessary. Section Tools should simply save a LayerState during creation and restore that before updating.
That’s viewing things the other way around (Section owns LS). But you could have several Sections within a particular LS. If you then change the LS to suit an edit to one of the Sections, what would then happen to the other ones?
Ok, so this is what we can do:
- When stCreate is called, it saves a layer state in the LayerState Panels and give it the same name of that section, and save a reference to it in SectionTools.
- When call stUpdateSections, it saves the current state temporarily, restore each section layer state, update each section, then restore the current state.
- If the user deliberately deletes the section layer state, then one of the 2 might happen: 1)There will be no state association and the section should simply use the current layer state to update that section. 2)Additionally, we can save a new Layer state for that section (using the current state) and save that new association for future updates?
Does this workflow sound reasonable?
Sounds good. I logged an item here: https://mcneel.myjetbrains.com/youtrack/issue/ST-34