danielboxer / uvgami Goto Github PK

"Engine path is incorrect." What engine path?

I can see an option to set it in the addon preferences "path to the unwrapping application stored on your computer", what unwrapping application? Why is there no explanation as to what it is anywhere?

If the installation requires something other than just installing the addon, perhaps it would make sense to explain the process instead of assuming that it's understood telepathically.

I'm using UVgami as part of an automated workflow, unwrapping low poly meshes. (And it's awesome, thank you for creating this.) Frequently UVgami will get stuck unwrapping 1-4 shells of the model (out of 60 or so) and never finish.

If I click the eyeball by on the 'stuck' shells, the window appears but doesn't have anything in it. If I click the stop button, a message in the console says a stop is initiated, but it never stops. Canceling works as expected, but shows the error mesage: "An unknown error occurred: -1073740791"

For some of the failing meshes, if I try to unwrap them as their own object, it works immediately. For some, it always gets stuck.

A common factor between the shells that fail to unwrap is that they have few vertices, like 20 or less.

In progress, so far so good:

Stuck on these 4:

Eyeball preview is empty:

These are the "stuck" meshes:

Console output:

Possible workaround: If there could be a timeout option for each unwrap, where it stops unwrapping a shell after x seconds if unwrapping isn't finished yet, then I could detect whether the unwrap has happened on each shell and maybe subdivide the faces and try again.

Again thanks for this tool! I hope we can find a way past this bug. Let me know if I can provide any more info.

trying to activate UVgami in blender 4.0.1 but keep getting a python Traceback error.
the error message is as follows:

Traceback (most recent call last):
File "C:\Program Files\WindowsApps\BlenderFoundation.Blender_4.0.1.0_x64__ppwjx1n5r4v9t\Blender\4.0\scripts\modules\addon_utils.py", line 364, in enable
mod = importlib.import_module(module_name)
File "C:\Program Files\WindowsApps\BlenderFoundation.Blender_4.0.1.0_x64__ppwjx1n5r4v9t\Blender\4.0\python\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\Users\Rowse\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\UVgami_init.py", line 17, in
from .src.manager import manager
File "C:\Users\Rowse\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\UVgami\src\manager.py", line 18, in
from . import progress_bar
File "C:\Users\Rowse\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\UVgami\src\progress_bar.py", line 14, in
SHADER = gpu.shader.from_builtin("2D_UNIFORM_COLOR")
ValueError: expected a string in ('FLAT_COLOR', 'IMAGE', 'IMAGE_COLOR', 'SMOOTH_COLOR', 'UNIFORM_COLOR', 'POLYLINE_FLAT_COLOR', 'POLYLINE_SMOOTH_COLOR', 'POLYLINE_UNIFORM_COLOR'), got '2D_UNIFORM_COLOR'

when I try the addon I get error that engine path is not set, I am not sure what should I enter here? please can you help

AttributeError: module 'numpy' has no attribute 'bool'

"np.bool" was a deprecated alias for the builtin "bool". To avoid this error in existing code, use 'bool' by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use 'np.bool_' here.

The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:

https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

Based on the error message looks like it should be an easy fix?

I am using macOS, and noticed with engine "Mac Not Supported".

Is there anyway anyone could help to compile the engine so it works on macOS?

If possible, it would be great to keep existing vertex groups on the unwrapped mesh object.

I checked the binaries in the latest Release Engine.zip.

The binaries do contain malware.

You can check the virustotal scans of the binary here:

Windows: https://www.virustotal.com/gui/file/273acc0c5f29ce42ce7ae7fca2e8e9fe55551f0d6de24a8835bb758bfd01cc95