Installation of Armory fails with amdgpu

[ShalokShalom]

Thank you for contributing to Armory!

Description

When I try to install the app (unpacked zip) Blender freezes, and I have to kill the process.
Running from command line doesnt reveal anything specific.

When switching to llvmpipe (CPU fallback driver) its all fine.

To Reproduce

I am on Arch Linux (Garuda, should be identical) and try to install the current version of Armory in the Blender, that is part of the official repos (also tried it with Blender binaries, same)

Expected behavior

Plugin installs

System
Blender: 4.3.1
Armory: 2024.12
OS: Linux
Graphics card: Vega 8

Test File
none

Note: It also fails to fetch the SDK path automatically

[Onek8]

You seemed to have resolved the freezing on discord but you opened a github issue here?

Freezing:

• Does this happen with any installation of addons or just armory
• Does this happen with all versions of blender or only 4.3 (go as far back as 2.8 as your freezing is likely an amd/blender conflict)
• Does your process use any resources or is it hanging doing nothing before you kill it
  SDK Path Detection:
• Is killing your process causing the sdk path detection to not trigger before you kill it
• Can you confirm the contents of these 2 (clipboard data / regex results) when installing a clean armory (a blender with no armory restarted with 0 traces of armory in the home user /.config/ blender installed addons)
  https://github.com/armory3d/armory/blob/main/armory.py#L81
  https://github.com/armory3d/armory/blob/main/armory.py#L85C1-L85C100

[ShalokShalom]

I will check on your questions, once I find time.

First:

Yes, I did resolve the freezing by uninstalling the driver.

Sadly, I was too hopeful that switching to another GPU driver would help.

Only the CPU driver (llvmpipe) got to work.

As a short overview, for somebody who is not using AMD drivers on Linux themselves:

There is amdgpu, the official kernel level driver, that is part of mesa.

Amdvlk is an extension of it, for Vulkan.

Those two are officially developed by AMD, and most of the time, they are stellar.

In fact, this is the first time I had a problem with it, and problems with it are sparse across the community generally.

Then there is Radv, that one is done by Valve, and used on the Steamdeck.

Gamers often go back and forth between the two, since they perform differently between games.

I imagined I just use Radv and call it a day, and assumed Blender would be able to run on Vulkan.

But that's not the case yet.

Radv has no OpenGL mode, so that is no escape hatch.

The only other driver for AMD OpenGL is the proprietary one from AMD.

They initially thought, companies would buy for it, but the open source version got so many performance updates, that it quickly surpassed the proprietary version, so AMD decided to basically fade it out.

Its still available and supposed to work, but it just causes a memory access error, when I want to launch Blender with it.

My plan is to a) try it with the experimental Vulkan version of Blender, or simply see if I can find any other extensions, that fail for the same reason, or at least in the same fashion.

Its my job now, to see if this an issue in regards to the extension, Blender or Linux/the driver, and just judging by the stability of the driver, I would assume its Blender or Armory.

So far as I know, is AMD support in Blender relatively recent. Hope the Vulkan version gets better support.

[ShalokShalom]

The problem also happens with version 3.6.

It does seem to work with version 3.3 LTS

With 2.8, I get the following error message.

The problem does not happen with the Poly Haven plugin in Blender 4.3.

And yes, the process does use resources.

My SDK path detection for Armory does not work at all.

I don't understand, how to check for these two regex results.
Is this supposed to show up in the Blender console?

[Onek8]

I have not worked the sdk backwards to 2.8 yet. That appears to be a python version issue and for 2.8 we will need to use the list import from typing. You can just message me on discord and I can walk you through some debugging steps for the path resolve since I am not on github as much.