Material Maker Lags on AUR Install, Fails to Start When Built from Source (Arch Linux)

[ms-solly]

Material Maker version: V1.4a3

OS/device including version: Arch Linux

Issue description:
I installed Material Maker using the AUR (yay -S material-maker). It starts, but it lags heavily the screen freezes completely, making it unusable.

Then, I tried building it from source using Godot, but this version fails to start at all.

I encountered multiple errors in the terminal logs, including Vulkan related issues and missing HDR resources. My integrated GPU has incomplete Vulkan support, so I’d like to know if it’s possible to use the OpenGL renderer instead.

Steps to reproduce:

1. Install Material Maker via AUR:

   yay -S material-maker
   

2. Run the AUR-installed version—it starts but lags heavily, freezing the screen.
3. Clone the Material Maker repository and open it in Godot.
4. Run the project from Godot—it fails to start.

Expected behavior:
Material Maker should run smoothly without lag, and the source build should start properly.

Actual behavior:

• AUR version: Starts but freezes completely, making it unusable.
• Source build: Fails to start.
• Terminal logs show multiple errors, including:

• Missing HDR files:

  ERROR: Error opening file '/usr/bin/environments/hdris/epping_forest_01_1k.hdr'.
  at: load_image (core/io/image_loader.cpp:89)
  

• Vulkan rendering issues:

  ERROR: QueuePresentKHR failed with error: VK_ERROR_DEVICE_LOST
  at: command_queue_execute_and_present (drivers/vulkan/rendering_device.cpp)
  

• Threading warnings:

  WARNING: A Thread object is being destroyed without its completion having been realized.
  

• Various Godot errors about missing or unimported resources.
  

Question:
Is there a way to force Material Maker to use the OpenGL renderer instead of Vulkan? My integrated GPU does not have complete Vulkan support, and this may be causing the issue.

Any help would be appreciated!