Object selection is cleared when switching to a component mode in Maya 2020 (very annoying!)

Object selection is cleared when switching to a component mode in Maya 2020 (very annoying!)

SpaceCoyote
Enthusiast Enthusiast
2,263 Views
6 Replies
Message 1 of 7

Object selection is cleared when switching to a component mode in Maya 2020 (very annoying!)

SpaceCoyote
Enthusiast
Enthusiast

I think this is a new quirk with Maya 2020, but when I have an object selected in object mode and then chose a component mode, like edge mode, my selection is cleared and I have to attempt to select the object again while in a component mode. I believe in the past when an object was selected, the object would stay selected when I switched to a component mode - is there any way to make selections work like this again in Maya 2020? Thanks!

0 Likes
Accepted solutions (1)
2,264 Views
6 Replies
Replies (6)
Message 2 of 7

SpaceCoyote
Enthusiast
Enthusiast

I just wanted to add that I'm switching between modes using the Modelling Toolkit shelf.

0 Likes
Message 3 of 7

mspeer
Consultant
Consultant

Hi!

 

There is no difference to previous Maya versions as far as I know (I tested this already in older versions).

 

1) If you just switch the selection mode to components, nothing is selected (at first), that's normal.

2) If you convert the selection to components, then all components will be selected.

3) If you already had some components selected anytime before on a particular object, then this selection will be restored when you switch to component selection. (If this is enabled in Preferences).

0 Likes
Message 4 of 7

SpaceCoyote
Enthusiast
Enthusiast

Thanks for your reply, mspeer. I'm not sure if your 3 scenarios describe my situation. When using the Modeling Toolkit to switch between selections types, if I'm in object mode and I already have an object selected and then I go into any component mode, everything is deselected. In the past, I don't believe this was the case because this creates an unnecessary step where I need to reselect the object after I go into a component mode.

 

I did some more testing and using the F keys to switch between object and component modes gives the results I'm looking for: while in object mode, and when an object is selected, if I switch to a component the selected object stays selected and I can begin editing the components of the selected object, as should be the case.

 

It could be something weird with my setup but I believe something has been overlooked with selections in the Modeling Toolkit in Maya 2020.

0 Likes
Message 5 of 7

mspeer
Consultant
Consultant

Hi!

 

Sorry, I don't understand what you mean with everything is deselected.

Please provide a video that shows the issue.

 

Please also try a reset of your Maya Preferences in your user documents folder.

https://knowledge.autodesk.com/support/maya/troubleshooting/caas/sfdcarticles/sfdcarticles/Reset-May...
a) Rename the folder prefs in folder 2020 to something like prefs_backup, or the folder 2020 to 2020_backup
(Don't copy preferences from previous Maya versions.)
b) For a complete reset of ALL Preferences, rename the maya folder to maya_backup.

0 Likes
Message 6 of 7

cavescholar
Advocate
Advocate

Hi, so I been fiddling with selections and noticed there are quite a few options for selections that are helping me. I would check to make sure that PreserveComponentSelection is checked. (Windows>settings>preferences>Selection)

PreserveComponentSelections.jpg

Hope this helps, good luck!

0 Likes
Message 7 of 7

SpaceCoyote
Enthusiast
Enthusiast
Accepted solution

It has been months since I initially posted about this, but I've discovered that this annoying bug was the result of the drivers for my 3Dconnexion 3D mouse. I'm not sure if it's a result of my specific 3D mouse or because of the latest drivers but this selection bug immediately stopped when I uninstalled all the 3Dconnexion software and unplugged my 3D mouse. The 3Dconnexion software was also causing very consistent crashing when using modelling tools like multi-cut and weld and I was only able to discover the source of these errors after digging through some very long crash reports. Thanks to all who tried to help me with this!