News:

 

Topic: Isolate Select  (Read 5773 times)

0 Members and 1 Guest are viewing this topic.

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
February 20, 2014, 02:32:06 pm
I often need to isolate select an object or component and model that.  I would love to have a toggle that views only what i have selected. The difficulty with the current method is that if i have many objects hidden, I do not want these objects to be made visible when I toggle "hide unselected".

  • No avatar
  • Posts: 2103
  • Polygon
February 20, 2014, 07:54:49 pm
[By default) F10 > "Toggle Unselected object visibility".

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
February 20, 2014, 08:13:21 pm
sadly, only works on object level and not polygon level.

  • No avatar
  • Posts: 2103
  • Polygon
February 20, 2014, 08:39:13 pm
Possibly a composite tool could deal with polygon level.

I will have a quick look.

-------------------------

This appears to work:-

Hide unselected polygons.



Show polygons.





« Last Edit: February 20, 2014, 09:09:47 pm by steve »

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
February 20, 2014, 09:22:20 pm
wow...i have to have a go at this...still learning obviously  8)

  • No avatar
  • Posts: 2103
  • Polygon
February 20, 2014, 09:43:32 pm
Give it a try, if you find problems, I will see if there is a different way to composite.

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
February 21, 2014, 10:14:04 pm
Yeah i got it working, only  thing is that 2x tools requires 2x hotkeys so I cannot make it toggle.  Its better then nothing though!

  • No avatar
  • Posts: 2103
  • Polygon
February 22, 2014, 12:46:33 am
Tools like that, I usually place in a streamline tool with one hotkey + mouse clicks.

Hotkey + LMB = Hide polygons
Hotkey + RMB = Unhide

  • No avatar
  • Posts: 289
  • Triangle
    • Portfolio
March 20, 2014, 08:37:52 am
So I have been using this solution for sometime now and find it difficult.

The process involves hiding unselected, and then toggling their visibility.  So I must often go to object level and unhide EVERYTHING to reset the process.

Thats bad, because there are a lot of objects that should remain unhidden regardless.

I want to view only the select object or subobject, without changing the visibility state of other objects in the scene. 

Its a subtle differance.

  • No avatar
  • Posts: 2103
  • Polygon
March 20, 2014, 11:40:27 am
The process involves hiding unselected, and then toggling their visibility.
The composite tool toggles unselected object viability, then hides unselected polygons.

Quote
So I must often go to object level and unhide EVERYTHING to reset the process.
Either you are not using the "Unhide" composite tool, or you are making object visibility toggle again, or the toggle is becoming corrupt.

Quote
Thats bad, because there are a lot of objects that should remain unhidden regardless.

I want to view only the select object or subobject, without changing the visibility state of other objects in the scene. 
I do not understand.
 You wanted to only view selected objects, which the composite does, so it should not change the state for selected objects. If you are now saying unselected objects should not be hidden, then that is completely different.

-------------------------------------

Comment(or maybe a rant).

 The object visibility toogle would not be needed if Nvil was more consistent between functions.
As example.
 We can select multiple objects, make sub_objects selections from one or more of those objects and save that selection as a "Group".
With "Save sub_object selection" we can only have one object selected, or an error popup will show.
 I did originally think that was due to a sub_object selection of an object being saved for each object,(as we currently see from selections, when changing object selection and changing the sub_object type selection) but it is not. It acts like a temporary group restriction to one object, that is written to, but over written if "Save sub_object selection" is made again on a different object.

Why have the inconsistency? Why does the "Save sub_object selection" not save to a temporary group, and/or behave like saving to a group?

 I find inconsistencies a pain, as they are usually due to tools being added without thought to tools already in place.



« Last Edit: March 20, 2014, 11:48:28 am by steve »