Yep, the value is hardcoded. The dotnet can be used to access some SDK stuff, for example: iGlobal = (dotNetClass "Autodesk.Max.GlobalInterface").Instance<br> --Get the node<br> myNode = iGlobal.COREInterface.GetINodeByHandle So, maybe this can be used to change this value. I've checked the SDK for 3ds Max 2019 and the…
Well it's not maxscript, so it's not that easy. This is C++ code which needs to be compiled. You would then replace your Edit Poly Object Plugin in 3ds Max with your own compiled version. Buuuut I don't know if the SDK sample code is up to date with all the fixes that the 3ds Max Team is pushing with each update/new…
Where excatly miauu? I looked through the Edit Poly Object cpp files and it's all hardcoded, no chance to change that. By default the hit region is 4 pixels and it will be mutliplied by 2 if you are in highlight mode. This is from EditPoly.cpp in the 2018 SDK There is a HIGHLIGHT_PICK_OFFSET constant at the top of the…
I think I would generalize it. Increasing the selection range should affect the selection of objects/components in general, not just the Editable Poly preview selection range. Also if you dissect maya's selection behavior it's a bit smarter than just having selection range. E.g. if you are in vertex/edge mode and hover…