max 2015
There bug ! After the custom settings in the window and select cross- check does not work!
这里设置好了后,在工作里选择模型却不起作用,形同虚设,请及时更正!!
Solved! Go to Solution.
Solved by darawork. Go to Solution.
Confirmed here too. The display shows the correct selection border type, but both are only selection windows, no crossing window.
Product version 17.00 commercial.
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
Finally i learned a feature in Max i was not aware of. I always thought that the option simply would set the default behavior like in the toolbar ( crossing or window selection ). So i now learned about this clever, cool little feature's existence
And yes - it's broken here too - so definitely a bug
xujieone:
Do not hope only - but do report too 😉
http://download.autodesk.com/us/support/report_a_bug.html?SelProduct=3dsMax
Same here. But it works in Sub-Object mode...
thanks!
did this SP1 for 2015 fix it or not?
No. 😞
Daniel Santana found a workarround and posted on cgsociety
Just enter this in the listener ( note: there' a chance that selecting/picking in heavy scenes might become slower )
NitrousGraphicsManager.HardwareHitTestEnabled = false
Original post
http://forums.cgsociety.org/showthread.php?p=7811994#post7811994
Great news, thank you!
I just put it in the startup script 🙂
@Anonymous wrote:
can anyone confirm if this script slows down scenes with huge amounts of objects ? i dont want to touch it if it will make things any slower.
Don't be too shy 😉
It's not really a script anyways, it's just one command. Test your typical heavy scene with hardware hit-testing selection on and with it being off. If you suffer a performance drop, you have to decide yourself, wether you'd rather have the cross/window selection thingy working or a faster in viewport object picking....
i just wasnt sure how i would turn this magic potion off if i dont like it. would it be a case of re-entering that text and typing "positive" instead of "false" ? (sorry - i have no idea )
I was noticing a very slow performance with regard to picking objects in the scene even without doing this - and i think maybe (not sure) it was to do with having the scene explorer open.
@Anonymous wrote:
what is the exact procedure ? i entered the text into the listener but nothing has changed ? (i restarted max)
No - dont restart ! that would reset to the inital enabled, just enter the command and work on
if you want to have this constantly fixed with the hack, you have to put it into a max script (*.ms) which you put into your scripts/startup folder
But honestly i would'nt do this and miss the hardware hittesting speedup in every session...
Can't find what you're looking for? Ask the community or share your knowledge.