ZenUV permantently crashing under blender 4.5.3 an...
# zenuv-support
s
ZenUV reliably crashes with the default scene, just have to switch to uv editing workspace with the default scene ( cam cube light) and then select the light. Getting an access violation crash with python311.dll Its crashing in this line of gizmo_draw.py The whole stacktrace is filled with repeatings of this line. Sometimes it stated as recursion depth level reached. AppData\Roaming\Blender Foundation\Blender\4.5\extensions\user_default\ZenUV\ui\gizmo_draw.py", line 235 in zenuv_depsgraph_ui_update Testwise deactivated zenuv as addon and the crashes instantly stopped.
v
s
Thank you for the tip. I just read the thread you linked, but if I havent missed anything important it seems not to relate. I eg dont have machinetools as activated plugin.
Normally even not the recursion depth mentioned. Typically it exits with the crash report popup
ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FFF4C803127 Exception Module : python311.dll
v
Machin tools is the first addon where we noticed this and together with the developer corrected the situation. But it is not the only one. You have to find the culprit, and this tool will help you do it quickly. https://discord.com/channels/695619708879372398/695620319741870150/1415052703884771479
Provide the OS name, Blender version, and Zen UV version, system log. Check if the problem recurs when only Zen UV is active.
s
Discord scrolled a bit awkard with your last link, but you were referring to this "Add-ons Presets for Blender v2.0.0" right?
I'll test it with other addons deactivated. But will need to find some time. So it will take some hours. Thanks for the help.
v
Under these conditions, everything should work stably. If you have the latest version of Zen UV, then all you have to do is find the broken addon.
s
Yes its the current version of zenuv as I wrote in the thread title. (5.1.0.7) Beside that using your linked addon helped indeed. Thanks . Overall it went quicker than I thought. I wanted to test to reactivate them all at once first, and two to reactivate addons had a shader compile error and one was a camera info gn node that had now nameconflicts with the now builtin node. But with those turned off it directly worked. All of them were not needed at all, so thanks for the heads-up.