Setting OffsetParentMatrix Transforms Causes Selection Problem

[Anonymous]

I'm just getting started digging into the new OffsetParentMatrix functionality in Maya 2020 and have hit a snag.
Setting the OffsetParentMatrix transform attributes on a curve to something other than default seems to change whether I can select by clicking on the curve in the viewport. I'm wondering if anyone else is having a similar issue?

Simple test: Create a nurbs circle, in its transform attrs -> transform offset parent matrix -> composition -> translate X 10.0

Can you select the circle by clicking the curve? Unable to click it directly, I seem to only be able to marquis select it. If I click near where the curve was before I set the OffsetParentMatrix, I can select it. Now in a interesting wrinkle, if I switch to Legacy Default Viewport, the transforms in OffsetParentMatrix no longer seem to effect the shape, and I can select the curve like normal. I'm aware Legacy Default is deprecated, but selection seems to be respecting what I'm seeing there.

Am I missing something? Is there a preference or setting somewhere that deals with this?

[mspeer]

Hi!

"Can you select the circle by clicking the curve?"

- Yes, no problem here (with Maya 2020.1) .

[Anonymous]

Thanks for trying that out.
It's the strangest thing. Clearing preferences doesn't seem to make any difference either.

[Anonymous · Accepted solution]

I got lucky digging into the preferences.
Changing Preferences -> Display -> Rendering Engine-> OpenGL - Core Profile (Strict) allows me to select curves with OffsetParentMatrix transforms as I would expect.

I was unable to select the curve in both OpenGL - Core Profile (Compatibility) and  OpenGL Legacy. Any idea why that might be happening?

[zewt]

FWIW, I haven't seen this and I use opm a lot now.

[mspeer]

Hi!

This is for sure a GPU/driver problem, but without further information I can't say exactly what happened here.

Just keep the setting that works for you.

[zewt]

Click selection involves the GPU to figure out what you clicked, but I'm not sure why that would be happening.  It's just another matrix in the transform hierarchy, it's hard to imagine that being a driver issue.  I don't see it in OpenGL Legacy, though.  Are you up to date (2020.2)?

[Anonymous]

No, I'm limited to 2020.1 at the moment. It's reassuring to hear its likely a GPU/ driver issue, I can work around that.