Tested at 4 computers (windows 7,10 and 3d max 2016 x64bit)
In max 2014 it doesn’t crash.
The code is very simple:
try (destroydialog EasyKill) catch()
rollout EasyKill "Easy Kill Max 2016" width:200 height:200
(
radiobuttons rad_buttons labels:#("Option1", "Option2", "Option3") columns:1 pos:[50, 50]
)
createdialog EasyKill
You have just to choose among options a couple of times and then select a window/application outside of max. This will throw “An error has occurred and the application will now close…”
I thought it was a bug in my script, and tested every function I have till I got to this. I spent some beautiful 5 days of my life thanks to this error. Any ideas?
i’ve checked the radio_buttons code, and see that screen resolution might relate to the result. i use 4K monitor btw, and can’t reproduce the crash issue
Very nasty bug. Thank you for reporting it.
One thing than appears to fix it is to change the focus of the control.
(
try (destroydialog ::EasyKill) catch()
rollout EasyKill "Easy Kill Max 2016" width:200 height:200
(
radiobuttons rad_buttons labels:#("Option1", "Option2", "Option3") columns:1 pos:[50, 50]
on rad_buttons changed arg do [B]setfocus EasyKill[/B]
)
createdialog EasyKill
)
I guess it would also work if you set the focus to another control instead of the Rollout, but havent tried it.
Hey, Jorge! Thank you, so much.
I added this setfocus to all radiobtns in my script. It is able to bypass this bug of max 2016 .
Can anyone please check in other versions of max?
Very strange situation. Try more times to change the options, then wait a little, then again. From time to time open any folder in Windows. During 2 minutes I certainly get max crashed.
Been trying for a few minutes now, I can’t reproduce the bug either. Win7, Max 2016.
No, it’s a regular monitor; although a dual monitor setup (horizontal + vertical).
I forgot to mention it’s Max 2016, SP3. Tried some more, still no crash.
Crashed on mine. 3dsmax 2016 EXT1 SP1
Aha, I lost a chunk of time with this bug too! I tell you it takes quite a while to chop back chunks of a massive script till you’re left with a single radiobutton!
I logged this bug with Adesk. Glad someone else has recreated it… and found a solution. Thanks for that!
Doesn`t crash on 2017 Sp2+Windows10. Tried it for almost 10 minutes.
I tried at monitors with such res:
1920×1200 px
1920×1080 px
1024×1280 px
at all the same bug.
I do not repro in the official 3ds Max 2016 release and an internal test build. I will test with the official 3ds Max 2016 release with the various SP’s and Extension’s now.