{"version":"https://jsonfeed.org/version/1.1","title":"Code Scrambler Productions Blog","home_page_url":"https://codescrambler.eu/blog","feed_url":"https://codescrambler.eu/blog/feed.json","description":"Programming tutorials, project stories, and development tips from Code Scrambler Productions.","language":"en","items":[{"id":"https://codescrambler.eu/blog/the-definitive-guide-to-autodesk-fusion-on-cachyos","url":"https://codescrambler.eu/blog/the-definitive-guide-to-autodesk-fusion-on-cachyos","title":"The Definitive Guide to Autodesk Fusion on CachyOS (KDE Plasma 6 + Wayland)","summary":"A complete, start-to-finish blueprint for installing Autodesk Fusion on CachyOS, bypassing system Wine, and fixing KDE Wayland window quirks.","content_html":"

Getting professional CAD software running on a Linux machine is a rite of passage. If you are reading this, you probably already know that installing Autodesk Fusion on rolling-release Linux distributions usually ends in disaster.

\n

This is the final, definitive blueprint. It takes everything we’ve battled through—from the black screens to the Wayland window quirks—and packages it into a clean, start-to-finish guide. All personal directory names have been stripped and replaced with standard Linux ~/ (Home) paths so this works universally for anyone following along.

\n

\"Autodesk\n

\n
\n

Credit & Inspiration: This guide builds upon the foundational work of the cryinkfly project and the community troubleshooting found in this Reddit discussion on r/cachyos.

\n
\n

The Core Problem: Why Standard Installations Fail

\n

Running standard system Wine packages (like wine-staging) frequently breaks Fusion’s embedded Qt6 web browser. This results in either a black screen at the login prompt or instant int3 memory crashes. Furthermore, running heavy X11 Windows applications through XWayland on KDE Plasma 6 introduces severe "mouse stealing" and window focus bugs that make modeling impossible.

\n

The Solution: We are going to bypass system Wine entirely. Instead, we will use the community-maintained cryinkfly installer script paired with a contained, gaming-optimized Proton-GE build.

\n
\n

Phase 1: Preparation & Proton

\n

First, we need to install the Secure Boot utility the setup script expects to see, alongside a GUI tool to manage our custom Proton builds.

\n

1. Install System Dependencies

\n

Open your terminal and run the following pacman command to pull the required utilities:

\n
\n
sudo pacman -Syu mokutil protonup-qt
\n
\n

2. Download GE-Proton

\n

Fusion relies heavily on specific media foundation codecs and Qt6 patches that are only found in GloriousEggroll's custom Proton builds.

\n\n
\n

Phase 2: The Clean Installation

\n

To prevent the installer from losing its directory mapping and throwing terminal "Permission Denied" errors at the root of your drive, always run it from a dedicated setup folder in your home directory.

\n

1. Create the Setup Workspace

\n
\n
mkdir -p ~/fusion-setup\ncd ~/fusion-setup
\n
\n

2. Run the Cryinkfly Installer

\n

This single string of commands downloads the latest setup script directly from Codeberg, makes it executable, and forces it to use the GE-Proton build we just downloaded.

\n
\n
curl -L https://codeberg.org/cryinkfly/Autodesk-Fusion-360-on-Linux/raw/branch/main/files/setup/autodesk_fusion_installer_x86-64.sh -o "autodesk_fusion_installer_x86-64.sh" && \\\nchmod +x autodesk_fusion_installer_x86-64.sh && \\\n./autodesk_fusion_installer_x86-64.sh --proton=GE-Proton10-32 --default
\n
\n

Let the script run. Depending on your hardware, this will take some time. It will download the Fusion client and set up a completely clean Proton prefix at ~/.autodesk_fusion.

\n
\n

Phase 3: The Login Redirect Fix

\n

Fusion uses a custom URL protocol (adskidmgr://) to pass the authentication token from your web browser back to the local application. KDE Wayland will almost always block this hand-off natively.

\n

1. Register the Link Handler

\n

Run these commands to explicitly tell KDE how to route the Autodesk login link:

\n
\n
update-desktop-database ~/.local/share/applications\nxdg-settings set default-url-scheme-handler adskidmgr adskidmgr-opener.desktop
\n
\n

Now, log in via your web browser and click "Go to product". If prompted by your browser, allow it to open xdg-open or adskidmgr-opener.

\n

2. The Manual Fallback (If the browser refuses)

\n

If absolutely nothing happens when you click "Go to product", the token is being blocked. Here is how to manually inject it:

\n
    \n
  1. Press F12 in your browser to open Developer Tools and navigate to the Network tab.
    2. \n
  2. Click the "Go to product" button on the webpage again.
    3. \n
  3. Look for a blocked network request starting with adskidmgr://. Right-click it and copy the full URL.
    4. \n
  4. Open your terminal and manually inject the token using the script provided in your prefix:
    5. \n
\n
\n
bash ~/.autodesk_fusion/bin/adskidmgr-opener.sh "PASTE_YOUR_COPIED_URL_HERE"
\n
\n
\n

Phase 4: Fixing Wayland Window & Mouse Bugs

\n

Because Fusion is an X11 application being translated through XWayland, pop-up dialogs (like Save or Upload) can become entirely invisible or unclickable. Worse, the 3D rendering engine may "steal" your mouse cursor, trapping it inside the window.

\n

1. Add Wayland Environment Variables

\n

We need to tweak how XWayland handles input and rendering priority for this specific application.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
VariablePurpose
WINE_X11_NO_DIRECT_INPUT=1Prevents XWayland from improperly locking the mouse pointer to the 3D viewport.
WINE_RT_PRIO=1Grants real-time priority to the Wine thread for smoother engine rendering.
GDK_BACKEND=x11Forces GTK dialogs to render through X11 compatibility, preventing invisible menus.
\n

Edit the launcher script using your preferred text editor (like Kate):

\n
\n
kate ~/.autodesk_fusion/bin/autodesk_fusion_launcher.sh
\n
\n

Add the variables near the top of the file, directly under the other export commands:

\n
\n
export WINE_X11_NO_DIRECT_INPUT=1\nexport WINE_RT_PRIO=1\nexport GDK_BACKEND=x11
\n
\n

Save and close the file.

\n

2. Apply KDE Window Rules

\n

We must force KDE to treat Fusion's pop-ups as normal windows so they can receive mouse clicks.

\n
    \n
  1. Open KDE System Settings -> Window Management -> Window Rules.
    2. \n
  2. Click + Add New...
    3. \n
  3. Description: Fusion 360 Fix
    4. \n
  4. Window class: Exact Match fusion360.exe
    5. \n
  5. Window types: Select Normal Window, Dialog Window, and Utility Window.
    6. \n
  6. Click + Add Property and configure the following overrides:\n
    7. \n
  7. Click Apply.
    8. \n
\n
\n

Phase 5: Known Limitations & Workarounds

\n

Even with an optimal environment, XWayland on KDE Plasma 6 has a few quirks you need to commit to muscle memory.

\n\n","date_published":"2026-03-24T18:27:45.475Z","date_modified":"2026-09-16T07:23:28.075Z","authors":[{"name":"Zsombor Rózsa"}],"tags":["cachyos","linux","autodesk","fusion360","wayland","kde","wine","proton"],"language":"en","image":"https://firebasestorage.googleapis.com/v0/b/code-scrambler.firebasestorage.app/o/blog-media%2F1774377039868-screenshot_20260324_193022.webp?alt=media&token=24ca80dc-0198-4917-a9eb-750101d2fb3b"},{"id":"https://codescrambler.eu/blog/windows-to-bazzite-to-cahcyos","url":"https://codescrambler.eu/blog/windows-to-bazzite-to-cahcyos","title":"My Journey from Windows 11 to Bazzite, and Finally CachyOS","summary":"Engineering, gaming, and development without Microsoft. A look at why I left Windows 11 and how I found the perfect OS balance with CachyOS.","content_html":"

The Pragmatic Migration: From Windows 11 Sludge to CachyOS Speed

\n

Let’s get one thing straight: abandoning an operating system you rely on for engineering coursework and daily tasks is never a casual decision. It requires a catalyst. For me, that catalyst was a deteriorating Windows 11 experience characterized by unfixable screen flickering, a highly unstable Tailscale connection, and a Sunshine host that simply refused to maintain a consistent stream. The entire OS felt sluggish, bogged down by telemetry and legacy cruft.

\n

I needed a system that could handle native software development, rendering, and gaming without fighting me for system resources.

\n

\"My\n

\n

The Hardware Foundation

\n

Before diving into the OS hopping, here is the architecture this stack is running on. Optimizing the OS means nothing if you don't understand the metal underneath it.

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ComponentSpecification
CPUAMD Ryzen 5 5600X (6-Core, 12-Thread)
GPUAMD Radeon RX 6700 XT
Memory32 GiB (31.2 GiB usable)
EnvironmentKDE Plasma 6.6.2 / Frameworks 6.23.0 / Qt 6.10.2
Display ProtocolWayland
Kernel6.19.6-2-cachyos (64-bit)
\n

The Compromise: The rEFInd Triple-Boot

\n

I would love to say I wiped the drive completely, but pragmatism had to win. Engineering university requirements mean I am still held hostage by Autodesk Inventor, a notoriously Windows-dependent piece of software. Furthermore, taking a sledgehammer to a drive housing years of undocumented files is a recipe for disaster.

\n

Currently, the system is managed by rEFInd, handling a triple-boot configuration. It isn't the final form, but it provides a safety net. Ironically, I don't even boot into Windows for Rainbow Six Siege anymore; GeForce Now handles that perfectly, proving just how obsolete the local Windows partition is becoming.

\n

Phase 1: Bazzite and the Immutable Ceiling

\n

The search for a native Linux daily driver initially led to Bazzite. Positioned as the premier hassle-free gaming OS built on an immutable (atomic) Fedora base, it seemed like the perfect plug-and-play solution.

\n

For standard use and gaming, it absolutely lived up to the hype. The containerized approach to package management was an interesting shift:

\n\n

However, the immutable architecture quickly became a bottleneck for advanced productivity. Engineering pipelines require software that isn't always packaged neatly for atomic systems. I successfully hacked Fusion360 onto Bazzite, but it came at a severe cost. A localized bug emerged when running Unity or Fusion360: opening any new window would lock the entire compositor. The desktop would freeze entirely—sometimes for 2 to 4 seconds, occasionally hanging for minutes.

\n
\n

"Bazzite is an engineering marvel for the living room, but if you need to hack together native CAD and game engines, an immutable filesystem will eventually fight back."

\n
\n

Phase 2: CachyOS and the x86-64-v3 Advantage

\n

The pivot to CachyOS was entirely impulsive. I saw this specific distro war thread on Reddit, comparing Linux distros. Realizing I had exactly two hours of free time, I decided to benchmark the migration.

\n

I copied over the essential dotfiles and assets from the Bazzite partition, flashed the CachyOS ISO, and initialized the installation. The difference in responsiveness was immediate and violently apparent.

\n

CachyOS compiles its packages using the x86-64-v3 microarchitecture instructions (and v4 where applicable). Because the Ryzen 5 5600X supports these advanced instruction sets (like AVX2), the entire user space executes with significantly lower overhead than standard generic-compiled distributions.

\n

The Arch Reality Check

\n

Moving from an atomic Fedora base to a bleeding-edge Arch derivative means trading safety for absolute control. It requires a more hands-on administrative approach:

\n
    \n
  1. Package Management: Transitioning muscle memory from rpm-ostree to pacman and paru (for the AUR) takes a few days, but the compilation speed via paru is heavily optimized out of the box.
    2. \n
  2. Kernel Panics & Quirks: Bleeding edge breaks occasionally. Right out of the gate, the Plymouth startup splash screen was causing hard system crashes during the boot sequence. Disabling the graphical boot completely resolved the kernel panic, dropping me back into a reliable, verbose TTY boot sequence.
    3. \n
  3. The Compositor: Unity and Fusion360 now run flawlessly under Wayland. The window mapping freezes that plagued Bazzite are entirely gone.
    4. \n
\n

Current Optimization Tasks

\n

While the system's speed is a completely different breed compared to Bazzite, there is still minor tuning required. Currently, I am debugging some slight visual artifacting and glitches with the Sunshine host under the CachyOS kernel.

\n
\n
journalctl --user -u sunshine -f\n
\n
\n

The migration proves a crucial point for power users: containerization and immutable file systems are the future of consumer electronics, but for development and engineering, unhindered access to the root filesystem on a highly optimized kernel still reigns supreme.

\n","date_published":"2026-03-12T20:51:20.926Z","date_modified":"2026-09-16T07:23:46.228Z","authors":[{"name":"Zsombor Rózsa"}],"tags":["CachyOS","Bazzite","Linux","Windows 11","Wayland","KDE Plasma","Engineering","Gaming","Distrobox"],"language":"en","image":"https://firebasestorage.googleapis.com/v0/b/code-scrambler.firebasestorage.app/o/blog-media%2F1773348837757-screenshot_20260312_215313.webp?alt=media&token=4c75f410-b016-4ce6-b6cc-4c09c8f50f5b"}]}