Selection priority of ghosted mode

Hi all.

On Ghosted mode it seems the selection (simple single click) priority have curve/wires/edges always above rendermeshes, whatever the “depth” is:
ghosted
Even when a wire/curve is completely hidden:
ghosted2

I don’t know if this was meant to work this way, but personally I would really like to have selection to work exactly the same way as in Shaded mode, selecting the nearest object “hitted” by the clicked pixel…

Hello- that is indeed by design.

-Pascal

Thanks for the prompt reply.

I don’t understand that.


There is some control over this? To change the selection priority?

On crowded models, with Ghosted mode, selection feels like more randomic than else…

Hey Riccardo,

did you find out where to set the priorities? I also want a solution for that, because I love the artic mode, but working here is really annoying, because selection is alsways catching things in the backround…:frowning:

Hi Homa -

That shouldn’t be happening in the Arctic mode, only in modes where you can see through objects.

Please copy-paste the results from the Rhino SystemInfo command and provide a simple 3dm file that can be used to check this issue.
-wim

I still don’t understand how selecting something that is completely hidden is “expected”.
I understand “filtering” objects from selection by “how much transparency of meshes decreased visibility” is probably a too-expensive task.
Instead, giving the option to have the selection behave like in shaded mode should be simpler… not?

This happens incredibly often, for me.
When you have dozens of geometries in the same place, selection with a simple click is absolutely random, or it prompts the drop-down selection all the times…


Anyway, is this expected too?
selection bug
selection bug.3dm (2.0 MB)

First:

  • select both
  • deselect (CTRL-click) red by clicking on the surface > good

Then:

  • select both
  • deselect (CTRL-click) red by clicking on the edge > bad, the edge lose all priority and is “bypassed”, deselecting instead the object behind

Hi Riccardo - I see this, thanks.
RH-73197 Deslection glitch

-Pascal

RH-73197 is fixed in the latest WIP

1 Like

I have something similar, but where it does not want to select the frontmost object at all in ghosted mode.

See the recording here: Recordit: Record screencasts fast & free! with GIF Support!

In shaded mode I can easily select the boxes. But in ghosted mode most of the time they are not selected and not even part of the selection list. Shouldn’t they at least be in the selection list all the time and probably on top of that list, seeing they are closest to me?

Seems really weird and like mentioned above, that the edges of other geometry always take precedent over the geometry closest to the view position.

It’s kind of annoying, since I now always have to switch to shaded just to select the boxes, then back to ghosted to see the plan beneath.

Thanks for fixing!

1 Like

In a similar vein, could you make it so Text Dots are always selected when you click directly on them. I click on one and it changes color to pink to show it is selected, but then it ALWAYS shows the selection box and I have to select it there. That means there is no way to select a bunch of text dots. If you have a lot of text dots you need to select individually, it will start to drive you mad…

Thanks for fixing!

This bug is still present.
On ghosted display mode (and similar), completely hidden objects are selected first, even if you click on something nearer the camera.

@mikko @KelvinC @pascal

I beg you considering this problem not with just a couple of simple geometries (like the one I shown ^ … where the problem is already 100% there).

It’s 2023. We can have rhino files of hundreds and hundreds of MB.
Packed situations where you have motor, brackets, screws, frames, cutting geometries, etc … a lot of geometries overlapping!
I go inside the geometry of the project and look from inside to see better (usually with camera lens length at 15mm …)
In that situation, shaded mode is way less useful than ghosted mode.
In that situation, with ghosted mode, selection is useless. Every time I try, I select something that is behind 10+ other geometries. Something completely unrelated to what I needed.

I know what It’s best for me.

You know what is best for us… (?)

Wouldn’t it be possible to give a custom order to selection priority?
I would always set it to “nearer to camera first”… as other options make absolutely no sense to me.

1 Like

This won’t be backported to V7? I’ve begun using ghosted mode (or a custom variant), and I can’t de-select things which is really problematic.

No, it won’t be backported to Rhino 7.