I had Claude help me setup Makera Studio on linux using Wine, for anyone else in my shoes, here's a write-up (from Claude).

Makera Studio on Linux under Wine — three fixes that make it fully usable

Got Makera Studio (the Carvera CAD/CAM beta) running properly on Ubuntu 26.04 with stock Wine 10.0. It installs fine out of the box, but three things break in ways that give you no error message at all. Writing them up because none of them were findable when I searched.

TL;DR: install an OpenCL driver, register the makera-studio:// URL scheme with your desktop, and set the Wine prefix DPI. None of this needs a patched Wine or a staging build.

Install

Grab MakeraStudio_Setup_For_Windows.exe from makera.com/pages/software. Use a dedicated prefix so it can't disturb anything else:

export WINEPREFIX="$HOME/.wine-makera"
wineboot -u
wine MakeraStudio_Setup_For_Windows.exe   # Inno Setup, /VERYSILENT works

Fix 1: clicking "Devices" instantly kills the app

No dialog, no message, the window just vanishes. The real error, which I only got by digging the exception out of a crash dump, is:

> no OpenCL platform found for volume rendering

The Devices tab renders its machine preview with OpenCL. It throws a std::runtime_error from inside a Qt event handler, and Qt can't unwind exceptions through those, so the whole process dies.

This is not a Wine bug. My machine had libOpenCL.so.1 installed but /etc/OpenCL/vendors/ did not exist — the ICD loader was there with zero drivers behind it. That combination reports "0 platforms" instead of erroring, so everything looks healthy until an app asks for a device. A native Linux app doing GPU compute would have hit the identical wall.

sudo apt install intel-opencl-icd   # Intel; mesa-opencl-icd for AMD,
                                    # NVIDIA's proprietary driver ships its own
clinfo -l                           # must list a platform and a device

Second half, and this part is Wine-specific: Makera bundles its own OpenCL.dll, a Windows ICD loader that searches the Windows registry and finds nothing even after you install the Linux driver. Force Wine's builtin so the calls bridge to the host:

export WINEDLLOVERRIDES="opencl=b"

You can confirm the whole chain is live with grep -i opencl /proc/$(pgrep -f MakeraStudio.exe)/maps — you should see Wine's opencl.dll, opencl.so, the host libOpenCL.so.1, and your vendor driver.

Fix 2: login opens the browser, you click Accept, nothing happens

Auth0 redirects to makera-studio://callback?code=.... The installer registers that scheme in Wine's registry, which your native Linux browser has never heard of, so the redirect lands nowhere and the app waits forever for a code.

[Desktop Entry]
Type=Application
Name=Makera Studio (URL Handler)
Exec=/home/YOU/.local/bin/makera-studio %u
NoDisplay=true
Terminal=false
MimeType=x-scheme-handler/makera-studio;

update-desktop-database ~/.local/share/applications
xdg-mime default makera-studio-url-handler.desktop x-scheme-handler/makera-studio

The app is built on Qt's SingleApplication, so the handler's second invocation forwards the URL over a local socket to the instance you already have open instead of starting a duplicate — but only if it runs in the same WINEPREFIX, which is why the handler must point at a launcher script and not a bare wine command. Test it without touching a real login:

xdg-open 'makera-studio://callback?code=TESTPROBE123'

The app log under AppData/Roaming/MakeraStudio/logs/ should show socket message: "TESTPROBE123".

One caveat: a Snap or Flatpak browser is confined and may not be able to invoke host handlers. My Chrome is a native .deb and works directly.

Fix 3: file dialogs are microscopic on HiDPI

Everything else looks right, only the file picker is tiny. The app's own windows are Qt, which handles HiDPI itself (devicePixelRatio 2). The file dialog is Wine's comdlg32 common dialog, which is drawn at whatever the prefix's LogPixels says — 96 by default.

wine reg add "HKCU\Control Panel\Desktop" /v LogPixels /t REG_DWORD /d 192 /f
wine reg add "HKLM\System\CurrentControlSet\Hardware Profiles\Current\Software\Fonts" \
  /v LogPixels /t REG_DWORD /d 192 /f

Restart the app; my dialog went from ~660x469 to 1320x938. The usual fear is that this makes a Qt app double-scale, but Qt doesn't derive its ratio from LogPixels — I checked the log before and after and devicePixelRatio stayed at 2, main window geometry unchanged. Use 144 for 1.5x displays.

Launcher that ties it together

~/.local/bin/makera-studio, also what the desktop entry and the URL handler both point at:

#!/bin/sh
export WINEPREFIX="$HOME/.wine-makera"
export WINEDLLOVERRIDES="opencl=b"
cd "$WINEPREFIX/drive_c/users/$USER/AppData/Local/Programs/Makera Studio" || exit 1
exec wine MakeraStudio.exe "$@"

Odds and ends

Connect over WiFi, not USB. The installer registers a Windows USB driver that does nothing under Wine. If you need a cable, Makera ships a native Linux build of Carvera Controller: github.com/MakeraInc/CarveraController
ERROR::FREETYPE: Failed to load font in the log is the app looking for AGENCYR.TTF (Agency FB, a real-Windows font). Cosmetic. Drop any TTF at that name into drive_c/windows/Fonts/ to silence it. It is not the Devices crash, which is where I initially wasted time.
If you're debugging your own crash: the app writes real minidumps to AppData/Roaming/MakeraStudio/dmp/ and a verbose log next to it in logs/. Far more useful than WINEDEBUG=+seh, which only gives you the exception type.

CAM side, toolpaths, and simulation have all been solid since. Happy to answer questions.

u/bytemynd