Hi, i get really weird behaviors with the quadrify tool.
While testing on a torus sometime it will work just fine, sometype throw a python error (see #1), sometime it crash blender (see#2)
I got #2 first and was looking for an issue with my install since it’s linux , but i ended up testing and ended up more confused.
I’m using a wayland compositor with an amd gpu (maybe relevant for #2)
#1
Python: Traceback (most recent call last):
File "/home/albedo/.config/blender/4.5/extensions/user_default/ZenUV/ops/quadrify.py", line 1441, in execute
p_total_sel_edges = len([k[1] for o in Storage for k in o.selected_items.selected_loops if k[1] is True]) // 2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/albedo/.config/blender/4.5/extensions/user_default/ZenUV/ops/quadrify.py", line 1441, in <listcomp>
p_total_sel_edges = len([k[1] for o in Storage for k in o.selected_items.selected_loops if k[1] is True]) // 2
~^^^
TypeError: 'int' object is not subscriptable
#2
albedo@fedora:~$ /opt/blender-4.5.7/blender "$@"
Repository data: /home/albedo/.config/blender/4.5/extensions/blender_org not found, sync required!
Zen UV Library: REGISTERED.
Read blend: "/home/albedo/git/ws_arch/Source/Enviro/Exterior/Antenna/Antena.blend"
Info: Deleted 3 object(s)
Read blend: "/home/albedo/git/ws_arch/Source/Enviro/Exterior/Antenna/Antena.blend"
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 15 (X_QueryTree)
Resource id in failed request: 0x1
Serial number of failed request: 8
Current serial number in output stream: 8
Error: Not freed memory blocks: 87957, total unfreed memory 143.540768 MB
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions. To fix this error, use the 'construct on first use' idiom.
blender: ../external_epoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed.
Aborted (core dumped) /opt/blender-4.5.7/blender "$@"