- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi all,
I’m automating Bake to Texture in 3ds Max 2026 (with Arnold).
When I launch baking from the UI, the “Baking Progress (Arnold)” dialog appears and remains responsive: the Cancel button and ESC key work as expected.
When I call baking from script, however, the situation is different:
BakeToTexture.autoCloseProgressDialog = false
BakeToTexture.showFrameBuffer = true
BakeToTexture.bake()
The “Baking Progress (Arnold)” dialog does not show.
My own PySide2 QDialog shows before the bake, but once the bake starts it becomes frozen (no button clicks or keypresses are processed).
I understand this is because the render loop blocks the main UI thread, but the native progress window somehow still accepts Cancel.
Questions:
Is there a way to force the native “Baking Progress (Arnold)” dialog to appear when calling
BakeToTexture.bake()
from script?
If not, is there any supported way to create a custom cancel mechanism (via a Qt dialog, keyboard shortcut, etc.) that remains functional while baking?
More generally, how does the native BakeToTexture progress dialog remain responsive to Cancel when the render blocks the main thread?
Any guidance or code snippets would be appreciated — I’d like to give users a reliable Cancel button when baking via script.
Thanks!
Solved! Go to Solution.