Ancient mesh bug in Rhino 7

Mesh command always places the mesh in the same layer as the original object. The two objects are difficult to distinguish because they have the same shape, size, location, color, and layer. Rhino users have been complaining about this bug for at least one decade, but the same bug is in Rhino 7. :scream: :tired_face: :rage: :angry: :face_with_symbols_over_mouth:

For the quad remesh command it would be nice if the remesh was created on the active layer.

3 Likes

Yes, it is almost the same bug. The only difference is that the QuadRemesh automatically selects the new object. There is the same bug in ToSubD and ToNURBS command.

selmesh, change layer?

1 Like

What is the benefit of having the mesh or SubD on the same layer?

We typically do not force behaviors on our customers where it can be avoided. The second we do, someone else screams about it and wants it changed back. Since we can’t possibly predict how each tool will be used in the hundreds and hundred of occupations that use rhino It’s a lose-lose for us.

In this case selmesh and change layer are scriptable so you can even customize your quadremesh tool to add this functionality assign it to a custom button and have it tailored for your specific needs. We try to just put tools on the table and let you decide how best to use them. Is that a guaranteed win? Clearly this is a case where the answer is no, but we find it’s the best path for most.

If that’s not an acceptable answer, let us know what would be, and we’ll figure out how to get this fixed for you.

1 Like

You wrote long post that is completely devoid of common sense and useful information - apparently you ran out of coffee. I am not trying to force Rhino users to do anything. I am trying to give them the freedom to do their work quickly. You are trying to force them to struggle with the stupid bug. Almost all Rhino commands place new objects on the current layer. The only exception that I know are the following commands: Mesh, QuadRemesh, ToSubD, and ToNURBS. If the new objects are placed on the current layer, the user can easily separate the new objects from the old ones. Your claim that this bug can be remediated with user-made scripts is a copout. If this argument is valid, we do not need new Rhino versions because we can fix all our problems with our own scripts.

Kyle, we really really like the fact that meshed object inherit all properties of what we are meshing: name, color, material, layer.

I’m sorry but I’m afraid we cannot approve a change of this behavior. It’s not a bug, it’s a really useful workflow when working with a lot of complexity.

Best,

G

I am 100% certain that you do not believe that. Here is the proof: how many times have you complained about enormous hardship that you have suffered due to the fact that almost all Rhino commands place new objects on the current layer?

1st stay civil, this is the rhino forum not a minecraft server, no need for snark or rudeness. we are all here to help each other.

2nd. You complain about the so called problem, but offer no solutions to how you actually want it to behave.

This is how it works currently… if your input object is on layer 2 your mesh is also on layer 2.

I want these buggy commands to behave the same way all the other Rhino commands behave - place new objects on the current layer.

I don’t know what to tell you… so just click on the gif below to see how it currently works.

I just want to make sure I’m not missing something here…

mesh- input object layer 1 = output object on layer 1
to subd - input object layer 1 = output object on layer 1
to nurbs- input object layer 1 = output object on layer 1
quadremesh- input object layer 1 = output object on layer 1

are you expecting something different?

You have a bad day, but you are still great instructor!
I had may bad days due to severe insomnia. You have seen the results on this forum - I looked like an idiot. (As a matter of fact I am an idiot, but very unusual idiot - an idiot savant who remembers next to nothing but solves very difficult problems in many fields of science and technology.)

it’s all good man. I just want to get to the bottom of stuff that bugs you all and try and make it better…

You are really having a bad day - I suggest that you return to this thread tomorrow.

ok… for what ever reason we are not connecting…

you say you want the new objects to be on the same layers as the input objects.

QUOTE- "Almost all Rhino commands place new objects on the current layer. The only exception that I know are the following commands: Mesh, QuadRemesh, ToSubD, and ToNURBS. If the new objects are placed on the current layer, the user can easily separate the new objects from the old ones."
[/quote]

these commands absolutely place the result (new objects in your quote above) on the same layers as the input object.

I show it in the gif, and I have just restested each command. The input and the output are on the same layer.

what am I missing?

I think he wants the new objects to be on the current layer.

ok, great…we are done here then because that’s what it does currently.