Z-Ray Documentation

Facetracker FAQ

2025-12-28T17:38:00+00:00

Why does Facetracker not use Portals to access Webcams</h2>
While in theory Facetracker could use Portals to access webcam devices it is OpenSeeFace which uses OpenVC to access webcams which in return has a hard requirement on Video4Linux2 (v4l2). Video 4 Linux 2 is the legacy API to access webcam devices on Linux and Unix based systems. To work with Portals it is required to access Webcams via PipeWire as Portals do not magically map a v4l2 device into the Flatpak sandbox. OpenVC however does not work with PipeWire and depends on v4l2.</p>
We could implement a dummy webcam which mimics a v4l2 device but actually talks to PipeWire. But this means a lot of additional work we're not willing to invest.</p>

OpenVC PipeWire support</a></li>
Facetracker attempt to implement Portals - #22</a></li> </ul>
Does Facetracker support handtracking?</h2>
No. Facetracker is only an OpenSeeFace wrapper application which does not have support for handtracking.</p>
Does Facetracker use GPU Acceleration?</h2>
While the GTK4 interface itself is GPU accelerated this does not apply for the facetracker of OpenSeeFace. This one only runs on CPU.</p>
Where can I find the source code of Facetracker?</h2>
The source code of Facetracker is hosted on Codeberg</a>.</p>
Where can I install Facetracker from?</h2>
Officially we only support Flathub</a> as a distribution platform. It might still very well be possible for any Linux Distribution to ship Facetracker in their repositories.</p>

Installing Kalpa Desktop

2025-12-28T14:25:00+00:00

</div> While Kalpa Desktop is aimed at novice users due to it's ALPHA development stage it is not very trivial to install it. Once setup even your grandma can use it. On this page we describe the necessary steps to install and setup Kalpa Desktop.

Prepare installer</h2>

Download the openSUSE MicroOS ISO from here</a></li>
Burn the ISO onto a USB stick with at least 4 GB

On Windows</strong> you may want to use Rufus</strong></a> for this</li>
On Linux</strong> you may want to use Impression</strong></a></li>
Note:</strong> Some might prefer Balena Etcher</strong></del>, but this tool is known to modify</strong> the installer image</li>
Attention:</strong> Make sure you do not have any important files on that USB drive</strong> as all data will be erased</strong></li> </ul> </li> </ol>
Install Kalpa</h2>
Once the installer has been copied onto a USB drive as explained above you now need to stick it into the target device where Kalpa should be installed. Shutdown the system if it is running and while booting it up press F1</em>, F12</em>, DEL</em>, ESC</em> to enter the UEFI Boot menu</em>. Which button applies depends on the device and UEFI.</p>
Start the installer</h3>
After the system has booted from the USB drive the openSUSE MicroOS</em> boot menu should appear. Select Installation</em></p>
</div>
Afterwards wait for the actual installer to boot up. This may take a while.</p>
Language and Keyboard</h3>
As the first step, after the installer has been loaded, choose your preferred langauge and keyboard layout.</p>
</div>
System Role</h3>
Afterwards the installer ask for the System Role. As Kalpa currently shared the same installer as the server orientated MicroOS there are several MicroOS roles. Choose openSUSE Kalpa (Plasma) [ALPHA]</strong></p>
</div>
NTP Configuration</h3>
You can leave this screen as it and just advance with Next</strong>.</p>
Local User</h3>
Now you can setup the default user for the new Kalpa system. It is recommended to setup at least one user here.</p>
Choose as User's Full Name</em> anything you'd like. Username</em> will then be filled automatically.</p>
Set any Password</em> you'd like. Additionally you can Use this password for system administrator</em> (root) if you do not plan on remembering two different passwords. Note:</em> This will NOT make the default user root.</p>
</div>
Installation Settings</h3>
Here we need to change a few things as Kalpa still shared the same installation media with MicroOS. While MicroOS is a server orientated operating system Kalpa is aimed at desktop users.</p>
Attention:</strong> Kalpa is not meant to be dual booted with other operating system. Therefore this guide assumes Kalpa to be the only system on the target system.</p>
Security</h4>
Click on the green text Security</em></p>
</div>
As first uncheck</strong> Enable SSH Service</em> as we do not run a server which requires remote access.</p>
Optionally</strong> you can also change SELinux Mode</em> to Permissive</em> or change Selected Module</em> to None</em>.</p>
</div>
Attention:</strong> Changing the default SELinux mode or disabling it will weaken the over all system security. As we do not have any form of Anti-Virus or Firewall in Kalpa.</p>

Changing</em> the SELinux Mode</em> can be done to skip</em> the later step Update SELinux Policies</em></a></li>
Disabling</em> SELinux all together will prevent</em> the system for occasionally Relabel</em> the entire file system after certain updates. This, depending on the amount of data you have, can take a few seconds up to several minutes.</li> </ul>
</div>
(NOTE: This is an extreme example with over 5TiB of data across multiple HDDs, relabeling on SSDs or with less data is significantly faster)</em></p>
Hit OK</em> and continue with Install</em></p>
System Setup post install</h2>
After the installation has been completed Kalpa will boot</strong> right into the text interface</strong> (also called tty). This is not due to a mistake during install but because, as previously mentioned, Kalpa shares the install media with the server orientated MicroOS. This is why we need to change SELinux and also will not have a graphical user interface enabled by default.</p>
Login as root</em> using the previously set passwort for the system administrator. While typing in the passwort there is not visual indicator that you've typed a character. Be assured it does.</p>
Enable Graphical interface</h3>
Now that we have logged in as root enable the sddm.service as follows:</p>
`systemctl enable --now --force sddm.service</code> and press enter.</p>`
`</div> The KDE login screen should appear right away. This step has only to be performed once. Now login with your default user.</p>`
</div>
KWallet</h3>
If connecting to a WiFi network KDE will show the initial KWallet setup screen. Choose Classic, Blowfish encrypted file</em> type in an easy to remember passwort, or none.</p>
</div>
</div>
Hit OK</em>.</p>
Attention:</strong> Currently there is a Bug in KWallet which causes it to fail to unlock after the first setup. If your system can not connect to WiFi and claims the password is wrong. reboot the system and try again.</p>
Update SELinux Policies</h3>
As Kalpa is not a server operating system the default SELinux configuration is rather strict. Unless you haven't change the SELinux mode to Permissive</em> above or disable it entirely here are some essential tweaks required for a smooth desktop experience.</p>
Open Konsole</em> and enter:</p>
sudo setsebool -P selinuxuser_execmod 1 sudo setsebool -P selinuxuser_execheap 1 sudo setsebool -P selinuxuser_execstack 1 </code></pre> This is required because applications such as Steam, Wine/Proton, native Linux Games and probably others do not work as expected causing all sorts of issues who's root cause is not very clear. With these 3 policies enabled there shouldn't be any additional SELinux headaches, despite relabeling.</p> Install Kalpa (for real now)</h3> As we are currently running MicroOS with KDE Plasma Desktop we're still not running Kalpa Desktop. To change this open Konsole and enter:</p> sudo transactional-update -i pkg in --force-resolution patterns-kalpa-base </code></pre> Press Enter</em> and wait for the install to finish.</p> </div> Install language packs</h3> In case you're locale is not English (US) you may need to install additional langauge files. Despite choosing the language in the installer.</p> Open Konsole and enter:</p> sudo transactional-update -c run zypper inr </code></pre> Press Enter</em>.</p> </div> Install nVidia drivers</h3> For installing nvidia drivers reboot your system and continue with our dedicated guide which can be found here</a>.</p> Or follow the official instruction as provided by Kalpa Desktop at: https://kalpadesktop.org/documentation/nvidia/</a>.</p> Note:</em> These guides are more or less identical as I wrote both of them.</p> Quality of Life Improvements</h2> The following steps are not necessary to install Kalpa but are considers QoL tweaks. Restart your system before continuing below.</p> Silent Boot</h3> If you are not a fan of text scrolling over your display while booting the system we can suppress this screen as follows:</p> Open Konsole and enter:</p> sudo vim /etc/kernel/cmdline </code></pre> Press i</em> to enter Insert</em> mode</p> Navigate to systemd.show_status=1</code> and change it to systemd.show_status=auto</code>.</li> Navigate behind quiet</code> and add loglevel=3</code>. Make sure quit</em> and loglevel</em> are separated by a space.</li> Press ESC :x</em> to save the file</li> Run sudo transactional-update initrd</code></li> </ol> </div> Hide boot loader</h3> In case you do not want to see the bootloader and wait for 5 seconds until the system boots you can hide this interface so it only comes up if required (pressing any arrow key or space while booting).</p> Open Konsole and enter:</p> sudo vim /boot/efi/loader/loader.conf</code></li> Press i</em> to enter Insert</em> mode</li> Set timeout 8</code> to timeout 0</code></li> Press ESC :x</em></li> </ol> The boot menu should disappear right away on the next reboot.</p> FAQ</h2> Why does Kalpa not have a dedicated install media?</h3> This is because KDE Plasma does not have a first boot / setup assistant for user creation as Gnome does. This is why the old YaST based openSUSE installer is still used. KDE Plasma was planing on adding KDE Initial System Setup</strong> (KISS) for Plasma 6.5.0 but it did not made it into the the actual release.</p> See: https://blogs.kde.org/2025/08/23/this-week-in-plasma-kde-initial-system-setup/</a></p> As soon as a future release of KDE Plasma has a working Initial System Setup Kalpa will also be separated from the MicroOS installer.</p> Why do we have to install Kalpa twice?</h3> This is related to the previous question. In the first step we install MicroOS with KDE Desktop. But this is still MicroOS (hence the branding you may have noticed during the first boot) but not the actual Kalpa. Since there is no dedicated Kalpa Installer we have to install and tweak our installation for it to become the real thing.</p>

E:D Market Connector on Linux and Steam Deck 2025-11-30T16:08:00+00:00 </div> An essential community tool used for fueling websites like INARA</a>, Elite Dangerous Star Map</a> or coriolis</a> with data about the game the Elite Dangerous Market Connector is used by many. Running it on Linux or the Steam Deck is for new users probably not as straight forward as it might be on Windows. On this page we describe the whole process to install and setup the connector as well as how to launch it automatically along side the game</p> If following this guide on Steam Deck please enter Desktop Mode.</strong></p> Install</h2> Download the latest version from Github</a></li> Install Protontricks</a> on your Linux system or Steam Deck via the local Software Center (eg. Discover or Gnome-Software)</li> Launch EDMarketConnector_Installer_(version).exe via Protonticks This can by done by right clicking the installer in your file browser and choose Open with Protonticks</li> </ul> </li> </ol> </div> Choose Elite: Dangerous from the list of installed games</li> </ol> </div> Walk through the installer</li> </ol> Auto start E:D Market Connector with Elite: Dangerous</h2> To not always need to manually launch the connector we can add a little Launch Option to Elite: Dangerous ia Steam.</p> Locate the actual file path on your computer / Steam Deck</li> Right-click Elite: Dangerous in Steam</li> Choose Manage</em> -> Browse installed files</em></li> Move on directory up and enter compatdata</em></li> Enter ./359320/pfx/drive_c/Program Files (x86)/EDMarketConnector/</em></li> Copy the full path to the EDMarketConnector.exe from your file browser adressbar including the name of the .exe itself</li> Right-click Elite: Dangerous in Steam and choose Properties</em></li> Enter PROTON_REMOTE_DEBUG_CMD="[path to market connector]/EDMarketConnector.exe" %command%</em> If the address contains spaces escape them with \</em> right in front of the space</li> Example: PROTON_REMOTE_DEBUG_CMD="/opt/datalake_ssd/vortex/.steam/steamapps/compatdata/359320/pfx/drive_c/Program\ Files\ (x86)/EDMarketConnector/EDMarketConnector.exe" %command%</code></li> </ul> </li> </ol> If you now launch Elite: Dangerous the E:D Market Connector should be launched right with it.</p> </div> (right-click open in new tab to enlarge)</em></p> Setup E:D Market Connector</h2> If launching the market connector for the first time it will open up the Frontier Development Authentication page in your default browser. You can allow E:D Market Connector to access your profile here if you wish. This is not mandatory.</p> Setup INARA API Key</h3> In order to connect the E:D Market Connector with INARA you have to obtain an API key form inara.cz. For this you'll require an account on inara.cz once you have one you can get an api key as follows:</p> Inside the E:D Market Connector chose File</em> -> Settings</em> -> Inara</em></li> Click on the blue text reading Inara-Logindata</em> This will open up the user settings of inara.cz and will either allow you to generate a new API key or if you have one already right away reveal your API key.</li> </ul> </li> Copy</em> and paste</em> the API key</em> into the market connector and hit OK</em></li> </ol> </div> That's it you should now be all set to use the E:D Market Connector on Linux and the Steam Deck</p> Waydroid on Kalpa Desktop and Aeon Desktop 2025-11-18T19:44:00+00:00 </div> While there is a guide online on how to install Waydroid on Tumbleweed it is unfortunately slightly out-dated and does not translate one by one to Aeon or Kalpa Desktop.</p> Install Longterm Kernel</h2> Throughout our testings we've noticed some instability using the -default Kernel using the binder kernel module as installed via anbox-modules. This can be Waydroid simply crashing at random or even cause the entire desktop to freeze.</p> Therefore we recommend installing the -longterm kernel as described on our dedicated documentation</a> page.</p> Configure Kernel</h2> Afterwards we need to add an additional parameter to our kernel commandline. This can be done by editing:</p> sudo vim /etc/kernel/cmdline </code></pre> Press i</em> to enter Insert</em> mode and add psi=1</code> at the very end of the cmd line.</p> It should look similar to this:</p> root=/dev/nvme0n1p2 [...] psi=1 </code></pre> Save the file by ESC :x</em></p> Then rebuild the initrd by running sudo transactional-update initrd</code></p> Install Waydroid</h2> sudo transactional-update -c run zypper addrepo https://download.opensuse.org/repositories/home:jimed-rand:waydroid/openSUSE_Tumbleweed/home:jimed-rand:waydroid.repo sudo transactional-update -c pkg in waydroid anbox-modules </code></pre> Then reboot the machine and continue below.</p> SecureBoot</h2> For SecureBoot enabled systems we also have to enroll the Machine Owner Key for the anbox-modules. As Kalpa has a root account it should prompt you right away with the MOK enroll screen. The default password on Kalpa is the one of the root</em> account.</p> </div> To enroll the MOK key do the following:</p> Enroll MOK</em></li> Continue</em></li> Yes</em></li> Enter root passwort (Kalpa) or the chosen password while using mokutils on Aeon</li> Reboot</em></li> </ol> Setup Waydroid</h2> First start the Waydroid container service:</p> sudo systemctl enable waydroid-container</code></p> After opening Waydroid and downloading the Android image it will ask for two OTAs. Enter these:</p> System OTA: https://ota.waydro.id/system Vendor OTA: https://ota.waydro.id/vendor</p> </div> Register Device</h2> If you've chosen the Android Image with Google Apps you also need to register your new "device". For this you'll need a google account.</p> While Waydroid is running open up a terminal and enter:</p> sudo waydroid shell -- sh -c "sqlite3 /data/data/*/*/gservices.db 'select * from main where name = \"android_id\";'" </code></pre> This should return something similar to this: android_id|xxxxxxxxxxxxxxxxxxx</code>. For the registration to work we only need the number after the pipe |</em>.</p> Open Goggle's Device registration</a> and login with the Google account you want this device to be connected with.</p> Enter the previously obtained device number and enter it into the textfield shown on the Device registration page. Confirm you're not a Robot and click on Register</em>. Now we have to wait a few minutes up to several hours.</p> Afterwards you should be able to use Goggle Apps with Waydroid or better said with Lineage OS just fine.</p> Unroot Waydroid device</h2> By default the Android Image running via Waydroid is a rooted device. THis means the ANdroid user has full system access. While some Apps, often times Streaming Apps, do refuse to work on rooted devices. In oder to use them we have to disable root access as follows:</p> Open the file: sudo vim /var/lib/waydroid/waydroid.cfg</code>. Press I</em> on your keyboard to enter Insert mode and add below [properties]</code>:</p> # fix root liapp ro.product.brand=google ro.product.manufacturer=Google ro.system.build.product=redfin ro.product.name=redfin ro.product.device=redfin ro.product.model=Pixel 5 ro.system.build.flavor=redfin-user ro.build.fingerprint=google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys ro.system.build.description=redfin-user 11 RQ3A.211001.001 eng.electr.20230318.111310 release-keys ro.bootimage.build.fingerprint=google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys ro.build.display.id=google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys ro.build.tags=release-keys ro.build.description=redfin-user 11 RQ3A.211001.001 eng.electr.20230318.111310 release-keys ro.vendor.build.fingerprint=google/redfin/redfin:11/RQ3A.211001.001/eng.electr.20230318.111310:user/release-keys ro.vendor.build.id=RQ3A.211001.001 ro.vendor.build.tags=release-keys ro.vendor.build.type=user ro.odm.build.tags=release-keys </code></pre> Afterwards update the device by running: sudo waydroid upgrade --offline</code>. The issue should now be fixed.</p> Source</h2> Runa-Chin - Tumbleweed Waydroid Guide - on Jun 18, 2024</a></li> </ul> Notes</h3> If you're coming form the Tumbleweed Guide provided by Runa-Chin this guide differs in a few things:</p> The repository was changed from where we get waydroid and anbox-modules</li> Installing weston or cage is not explained as both Aeon and Kalpa are Wayland centric distributions and thus do not run via X11. Hence, we already run a Wayland compositor by default.</li> We added a SecureBoot section which was missing in the original guide.</li> Changing the Kernel commandline is done differently on Kalpa and Aeon as both use SystemD-Boot by default.</li> Obviously we also changed every zypper command to transactional-update as zypper can not be used as it on Aeon and Kalpa</li> Added Register Device section</li> Added unroot section</li> </ol> Install Need for Speed Underground, 2, Most Wanted and Carbon on Linux 2025-11-08T19:39:00+00:00 </div> Installing Need for Speed Underground, Underground 2, Most Wanted (2005) and Carbon on Linux is rather simple. On this page we will also learn how to setup the No-CD fix and widescreen patch for these games.</p> Setup Bottles</h2> In case there is not Bottles environemtn to run these games with create a new one.</p> Install Bottles</em> from flathub</a></li> Create a new environment by clicking on the Plus Icon</em> in the top left</li> </ol> </div> Supply a Name</em></li> Select Gaming</em> as preset</li> Hit Create</em></li> </ol> </div> Install the games</h2> If using disk images make sure Bottles has proper read access to /run/media/<USER_NAME></em>. You can use Flatseal or KDE's Build-in permission screen for this.</p> </div> </div> Restart Bottles after this change.</p> Mount</em> the disk images</em> or insert</em> the retail disks</em></li> Open</em> up the newly created Bottles environment</em></li> Choose Run Executable...</em></li> </ol> </div> Navigate to the mounted disk or disk image</li> Choose the game installer</li> Click on Run</em></li> Walk through the game installer</li> </ol> If you plan on using disk images</strong> the No-CD fix</strong> is mandatory</strong> . As the ISO format does not carry all aspects of the Secure Disk DRM</strong>. Continue with the No-.CD fix section. If using the retail disks all should work as expected already and you can play the game.</p> No-CD fix</h2> Download</em> the No-CD fix from GameCopyWorld for your game:</li> </ol> Need for Speed Underground</a></li> Need for Speed Underground 2</a></li> Need for Speed Most Wanted (2005)</a></li> Need for Speed Carbon</a></li> </ul> Extract</em> the downloaded Archive</li> Copy and paste</em> all content into</em> the install path</em> of the required game</li> Overwrite</em> the main game executable</em> if asked or create a backup of it</li> </ol> You should now be able to play the game without a disk or disk image required.</p> Widescreen fix</h2> Download</em> the widescreen fix for your game from GitHub</em></li> </ol> Need for Speed Underground</a></li> Need for Speed Underground 2</a></li> Need for Speed Most Wanted (2005)</a></li> Need for Speed Carbon</a></li> </ul> Extract</em> the Archive</li> Copy and paste</em> all containing files and directory into the game install path</em></li> Open</em> Bottles Environment</em></li> Choose Settings</em></li> </ol> </div> Scroll down until you read DLL-Overrides</em></li> </ol> </div> Add a new entry: dinput8</em> and set it to native, then build-in</em></li> </ol> </div> Troubleshooting</h2> While most of the time these steps are the same for all 4 games there a few occasions where some of them require some special tweaks.</p> Need for Speed Underground 2</h3> For Underground 2 we will require the No-CD and the widescreen fix in order to be able to play the game without any physical or virtual disk. With just the No-CD fix we would still require a mounted disk image to play. Therefore I recommend using both the No-CD and the widescreen fix for this game.</p> Need for Speed: Most Wanted</h3> For Most Wanted we need to configure the widescreen fix as by default the game UI might be misplaced. Therefore if you want to play Most Wanted with the fix you have to open up the scripts</code> directory we copied into the game install from the widescreen fix.</p> Then open the file NFSMostWanted.WidescreenFix.ini</code> with any text editor you'd like.</p> Below [MAIN]</code> change FixHUD = 1</code> to FixHUD = 0</code>. This will keep the in-game user interface at the original 4 by 3 aspect ration and might stretch it. But at least it is not off screen and all elements can still be seen.</p> Video</h2> </iframe> </div> Long term support (LTS) Linux kernel on openSUSE Tumbleweed 2025-10-08T15:00:00+00:00 </div> The openSUSE Project offers two kernels versions for Tumbleweed. The -default</em> one which is the latest upstream Kernel and the -longterm</em> which is the current LTS version of the Linux Kernel.</p> Under certain circumstances you may want to switch to the LTS Kernel in order to validate an issue with the recent Kernel or maybe some is reliant on certain proprietary drivers which do not always work correctly with the latest upstream Kernel and hence a slower moving Kernel might be desired.</p> Install -longterm</h2> To install the long term support kernel is rather simple by running:</p> Tumbleweed:</strong> sudo zypper in kernel-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in kernel-longterm</code></p> Upon the next boot you'll be able to choose which Kernel to boot from the bootloader.</p> nVidia</h2> If you are using the propriatary nVidia driver you may laos install teh appropriate -longterm Kernel module:</p> Open Kerne Modul</h3> Tumbleweed:</strong> sudo zypper in nvidia-open-driver-G06-signed-kmp-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-open-driver-G06-signed-kmp-longterm</code></p> Closed Kernel Modul</h3> It is also important to know which driver series you have installed. As there are -longtermn modules for G06 and G05. G04 has no such module.</p> G06:</h4> Tumbleweed:</strong> sudo zypper in nvidia-driver-G06-kmp-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-driver-G06-kmp-longterm</code></p> G05:</h4> Tumbleweed:</strong> sudo zypper in nvidia-driver-G05-kmp-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-driver-G05-kmp-longterm</code></p> Uninstalling -default</h2> Attention:</strong> Uninstalling the -default Kernel will will remove the patterns-kalpa-base</strong> and patterns-aeon-base</strong> meta packages. by this future updates which are beyond application and library dependencies and hence make up the full Aeon or Kalpa experience will not get installed. Or in other words you'll put your system in an untested and undefined state!</p> If you do not plan on using the default Kernel afterward consider uninstalling it. This way there will only be one bootloader entry available for the LTS Kernel.</p> Tumbleweed:</strong> sudo zypper rm kernel-default</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg rm kernel-default</code></p> History</h2> 2025-11-19: Added warning about uninstalling -default Kernel</li> </ul> </li> </ul> CUDA cuInit: Unknown error on Linux 2025-09-27T21:02:00+00:00 </div> With recent Linux Kernels and flatpak, podman and docker CUDA does not get correctly initialized from within a sandbox or a container. Affected workloads are:</p> Games using compute shaders and running via flatpak or a podman container (eg. Distrobox) Hunt Showdown 1896</li> The Talos Principle 2</li> Satisfactory (running in DIrectX 12 mode)</li> Hellblade II: Senua's Saga</li> </ul> </li> DaVinci resolve via podman container with shared nvidia driver</li> Blender and using CUDA to render with Cycles running via flatpak</li> OBS Studio via flatpak if using NVENC</li> Upscayl via flatpak</li> InvokeAI via distrobox eg. pytorch</li> Ollama via prodman or flatpak for example if using Alpaca</li> </ul> Common error codes are:</strong></p> CUDA cuInit: Unknown error</li> cuda_init_999</li> DirectX 12 not supported on your system. Try running without -dx12 or -d3d12 command line argument</li> </ul> </div> Kick-start CUDA</h2> To work around this error we found that "kick-starting" CUDA from outside a sandbox and not using any containerization technology does solve the issue. Without a reboot and by simply re-starting affected applications CUDA gets initialized correctly.</p> Download Blender from blender.org</a></li> Extract and run Blender</li> Navigate to Edit → Preferences → System</li> Enable CUDA</li> If your GPU is shown CUDA is working</li> Re-start affected applications</li> </ol> If you are affected by this error please help to report this issue to nVidia.</p> Known affected systems configurations</h2> Linux Kernel: 6.14.6 or newer</li> Flatpak: 1.16.0 or newer</li> Podman: 5.4.2 or newer</li> nVidia driver 570.144 or newer</li> CUDA 12.8 or newer</li> </ul> Also, this seems to be independent of the desktop environment as this error occurred on KDE Plasma as well as Gnome. This error has been observed on different Linux distributions like Aeon, Kalpa, EndevourOS.</p> Sources</h2> nVidia Bug report - Unrelaibale cuInit with sandboxes and containers (CUDA cuInit: Unknown error)</a></li> </ul> Missing videos in Wine / Proton 2025-09-23T17:45:00+00:00 </div> If you encounter missing videos e.g. by seeing a black screen and only hearing sound or by looking at a test image here is what you can do.</p> On this page you'll find steps required for Steam, Bottles and Lutris.</p> </div> Steam</h2> If you play your games via Steam you can install alternative Versions of Proton with additional multimedia codec support. To ease up the setup we recommend also intalling ProtonPlus</a> or ProtonUp-Qt</a>.</p> Install ProtonPlus</em> / ProtonUp-Qt</em></li> Open</em> the installed application</li> Select</em> the Launcher</em> you run your game with. In our case this is Steam</li> Open the GE-Proton</em> section</li> Install the latest version</em></li> </ol> </div> Restart Steam (or the Launcher you have installed GE-Proton for like Lutris or Bottles)</li> Set GE-Proton as the runner to run the game with</li> </ol> Set GE-Proton as game runner</h3> Right-click</em> the game in your library</li> </ol> </div> Choose Properties</em></li> Navigate to Compatibility</em></li> Enable (if not already) Force the use of a specific Steam Play compatibility tool</em></li> Select the newly installed Proton</em></li> Run</em> the game and see if it has fixes the issue</li> </ol> </div> Note:</strong> We do not recommend to set GE-Proton as default for all games as it might introduce other regressions over Vavles Proton.</p> Bottles</h2> Unlike with Steam you do not have to use extra Tools to install additional versions of Wine for Bottles. If you encounter issues with missing videos in a game add GE-Wine from within the application and set it as the runner for the environment your game runs with.</p> Click on the Hamburger menu</em> at the top right of the main UI</li> </ol> </div> Select Preferences</em></li> Navigate to Runner</em></li> Open the GE-Wine</em> section</li> Install</em> the latest version</li> </ol> </div> After Bottles has downloaded and installed the new runner navigate back to your Bottles environment and set the newly installed GE-Wine as the environment runner.</p> Enter the Environment</em></li> </ol> </div> Click on Settings</em></li> At runner chose GE-Wine</li> </ol> </div> Then launch your game and check if the issue was solved.</p> Lutris</h2> For Lutris there is no external application needs as well to install additional versions of Wine. You can install those from within Lutris itself.</p> Add GE-Wine vie the runner manager and configure the game to use the newly installed version of Wine.</p> Open Lutris</em></li> Click on the hamburger menu</em> in the top right</li> Select Preferences</em></li> </ol> </div> Afterwards navigate to Runners</em></li> Scroll down until you read Wine</em></li> Click on the little package icon</em></li> </ol> </div> Search for Wine-GE</em> and install it</li> </ol> </div> Chose your game in the library</em></li> Click on the little arrow next to the Play-Button</em></li> Navigate to Configure</em></li> </ol> </div> Switch to Runner options</em></li> Chose the previously installed Wine-GE</em></li> Save</em></li> </ol> </div> Launch your game and check if the issue was resolved.</p> Proton / Wine Troubleshooting 2025-09-23T17:45:00+00:00 </div> Here you'll find common troubleshooting steps involving Wine and Proton. For game specific tweaks we highly recommend looking up ProtonDB</a> instead.</p> Missing videos</a></strong></p> Win2Go Components 2025-09-18T10:11:00+00:00 Win2Go uses the following addional tools to acomplishit's mission.</p> Wimlib</h2> Since the Windows install ISO isn't the only image format involved in the process of installing Windows. Win2Go also ships with wimlib which is used to analyze and extract the actual Windows Edition onto the UBS device. All Windows Editions found on an ISO image are contained in an install.wim archive.</p> Win2Go therefore uses wimlib to fetch all available version of Windows contained in such image and to extract the chosen image to the USB device.</p> Website</a></strong></p> dasbus</h2> Is a Python DBus abstraction library which is leveraged to actually talk to UDisk2 in the first place. Since Win2Go also mounts the ISO of Windows it has to tell Udisks2 where the actual image is located. For this the dbus interface involved requires a Unix File Descriptor to reference the ISO image on disk.</p> While there are many dbus abstractions for Python dasbus is one of the few (or the only one at all) which has support for file descriptors. Many other python dbus interfaces even pydbus, which is mentioned by DBus itself, does not support this.</p> Therefore, we use dasbus.</p> dasbus - Gihub</a></strong></p> Hivex</h2> Since working with Windows also sometimes involves working with Windows Registy files Win2Go uses hivex to do exactly this.</p> At the moment it is used to set up the BCD file which is part of Windows Bootloader. The BCD tells the bootloader where the actual Windows can be found in order to launch it.</p> In future release we also plan on using hivex to disable certain hardware checks of Windows 11 for an even more portable Windows.</p> Win2Go uses a premade boot.reg file which contains a few not Windows registry conformant placeholders to set up the bootloader. All we do is to collect the required information, replaces them in the boot.reg and then merge them using hivexregedit with the more or less empty default BCD file shipped by Win2Go.</p> This modified BCD file is then copied to the Windows Boot partition.</p> hivex GitHub</a></strong></p> Win2Go Troubleshooting 2025-09-18T10:11:00+00:00 XDG Desktop Portal</h2> Win2Go has a soft requirement on XDG Desktop Portal version 1.20 but can work with older versions as well. Version 1.20 or higher is recommended because that version added support for the xattr::document-portal.host-path</code> file property.</p> Since files in flatpak are mounted into the sandbox by a temporary path which is not available outside the sandbox. WIn2Go needs to figure out the real path of the Windows ISO image on the host. This is done using the above file attribute.</p> Since xdg-dsktop-portal 1.19 this property is available for directories (but not files) and since version 1.20 also for files. Win2Go looks up this property. If it can not be found and the ISO file seems to be available via a temporary sandbox path it will inform the user about this and link to this page.</p> In order to fix this the user can do the following:</p> Update to xdg-desktop-portal 1.20</li> Move the ISO file to the Downloads folder (this folder is mounted as it into the flatpak sandbox of Win2Go)</li> Grand Win2Go additional file system access using flatpak overrides</li> </ul> In future releases we will drop the permanent access to the Download directory. But this may take a while because of slow moving point-releases which unfortunately are used by too many people to ignore this...</p> XDG Desktop Portal Documentation</a></p> vfat, ntfs or udf not supported</h2> Support for the vfat, ntfs and udf file systems is a hard requirement for Win2Go. If these are not met the application can not continue.</p> vfat: Is used to format the boot partition of Windows</li> ntfs: Is used for the main Windows partition (C:)</li> udf: Is the file system Windows ISO images are usually contained in</li> </ul> If one or more of these are missing the user has to install support for these using their local package manager.</p> vfat</strong>: Support for vfat should be present on all Linux distributions by default. Otherwise, they wouldn't boot themselves.</p> ntfs</strong>: For ntfs support please install ntfs-3g</code></p> udf</strong>: To add UDF support please install udftools</code></p> UDisks2 missing</h2> Since Win2Go is a flatpak application it relies heavily on DBus to communicate with things outside the sandbox. While there is a multitude of disk managing tools available on Linux Udisks2 is the only one with a DBus interface Win2Go can talk to.</p> To avoid granting Win2Go to broad permissions and access to the host system by allowing it to run flatpak-spawn --host</code> and run arbitrary commands as superuser it relies on Udisks2 instead.</p> If UDisks2 can not be found Win2Go will inform the user and link to this page. Please install Udisks2 for your distribution.</p> UDisks2 - GitHub</a></p> Win2Go Unsupported features 2025-09-18T10:11:00+00:00 The following features are not supported by Win2Go.</p> Legacy Boot (MBR)</h2> Win2Go does not and will not support for Master Boot Record based Legacy Boot.</p> Adding support for this would require us to weaken the flatpak sandbox by a lot as we have to run arbitrary commands on the host machine.</p> Also, it would skyrocket the list of components for Win2Go itself and tools required on the host.</p> Considering MBR based boot is on its way being phased out even on Linux adding support for this is not worth the extra work.</p> Repair damaged Windows Boot loaders</h2> While Win2Go is able to create a Windows Bootloader for the portable installation. We will not support repairing damaged bootloaders.</p> Supporting this would require us to do some extensive checks and validation about an exisitng Windows installation. Additionally, users might also expect Win2Go to also fix their dual boot setups or even create one in the first place.</p> No, thank you. Just grep a 2.5" SSD, an SATA to USB enclosure and just install Windows onto that device using Win2Go. It will save you a lot of headaches further down the road. Especially if a new Windows updated decided to nuke your dual boot again.</p> VHD(x) to USB</h2> Win2Go will not support installing virtual hard disk images from a Windows Virtual Machine onto a USB device.</p> While we understand the need for some users to "simply" flash their virtual machine onto a physical USB device and then use it as a portable system. We do not want to deal with yet another image and file system format.</p> Maybe, just maybe, and if it does not turn out to be too much of a hassle we MAY</em> add support for this in a future version. But do not expect this to happen at all or in the near future.</p> Create installation media</h2> While Win2Go creates a Windows installation onto a USB device it will not support creating Windows install media too. There are already tools doing this: Balena Etcher</a></p> We simply do not see any valid reason to clutter the UI with another option just for this while we provide an easier and faster way of installing Windows already.</p> Win2Go 2025-09-18T10:11:00+00:00 Win2Go is a graphical tool to create portable installations of Windows on USB devices from Linux. By this it does not create a bootable Windows installation media but an actual full-blown Windows installation ready to use.</p> All that is needed is a large enough USB device and an up-to-date Windows ISO install image.</p> Win2Go will then format the USB device and extract Windows from the ISO image onto the device. Set up the Windows bootloader and that's it.</p> Source Code</a></strong></p> Components</h2> For more details about additional components Win2Go uses see the dedicated components section</a></strong>.</p> Unsupported features</h2> Win2Go has a very specific use case: To install portable versions of Windows onto USB devices. However there a certain features users might request which are beyond the scope of Win2Go.</p> See the dedicated unsupported features section</a></strong> for more details</p> Troubleshooting</h2> If you ran into some issues with Win2Go please refer to our troubleshooting guide</a></strong>.</p> Special thanks to</h2> While Win2Go does not use any of these tools we still want to honor them as they revealed a lot about the underlying processes involved to create portable versions of Windows:</p> jxctn0 - win2go Shell Script</a></li> BCD-SYS - BCD Shell Script</a></li> </ul> 32bit Software on 64bit Linux 2025-09-07T14:51:00+00:00 </div> Many Linux distributions aim to drop execution support for 32bit Software. On this page we'd like to show ways of running 32bit Software on 64bit Linux systems.</p> Flatpak</h2> The simples way is by using Flatpak. Since flatpak is a universal Linux packaging format it ships dependencies required by applications via so called runtimes. This also included dedicated 32bit compatibility runtimes. Therefore application developers might consider shipping their 32bit software as a flatpak and publish it via flathub.</p> For end users it is recommended to look at one of the following solutions without going into packaging up a Flatpak application</p> Steam</h3> There is an unofficial Flaptak of Valves popular game front Steam available on Flathub. Simply download and install. It does contain all the required 32bit compatibility to run all your games and Steam right away with zero setup.</p> </div> Lutris</h3> Some can make use of Lutris from flathub</a>. Which allows for running any software via flatpak.</p> Add a new "game" by clicking on the plus</em> icon in the upper left of the man window</li> </ol> </div> Select Add locally installed game</em></li> </ol> </div> At Game info</em> supply a name</em> and set Runner</em> to Linux (Runs native games)</em></li> </ol> </div> Switch to Game options</em></li> Set Executable</em> to the main binary of the application or game</li> Working directory</em> to the directory containing the game or app selected previously</li> </ol> </div> (Optional): In case the application or game relies on custom libraries either set them at Preload Library</em> (One file only) or an entire directory at Add directory to LD_PRELOAD_PATH</em></li> Save and run the game or application</li> </ol> Distrobox</h2> Another option is to run 32bit software via Distrobox using a Linux distribution with 32bit execution support. For a list of Linux distributions offering 32bit support please refer to our dedicated documentation page here</a>.</p> A common use case might be 32bit application requiring to run an installer first.</p> Graphical Distrobox tools:</h3> BoxBuddy</a></li> DistroShelf</a></li> Kontainer</a></li> </ul> Create a new distrobox</li> Enter the distrobox shell</li> Run the installer</li> export the game or application to the host distrobox-export -a app-or-game-name</code> if the application creates a *.desktop</em> file</li> distrobox-export -b /path/to/binary</code> if the application does only get launched via a binary file</li> </ol> </li> </ol> Then the application can either be run by calling the binary from the terminal or via a application shortcut form the application launcher.</p> </div> Using graphical tools *.dep</em> or *.rpm</em> files can be installed into a distrobox container directly.</p> </div> BoxBuddy and DistroShelf support exporting applications from the UI into the host system.</p> </div> </div> Wine and Proton</h2> Wine and Proton are 64bit applications already. They use WOW64 (W</strong>indows-O</strong>n-W</strong>indows 64</strong>bit) to run 32bit and 16bit Windows applications on 64bit Linux already.</p> Video</h2> </iframe> </div> Facetracker with VSeeFace 2025-09-05T16:05:00+00:00 Even though VSeeFce uses OpenSeeFace itself the webcam based tracking does not work on Linux due to limitations of the Wine / Proton Webcam API. Therefore we need to use an external OpenSeeFace tracker such as Facetracker.</p> Assuming you already have installed VSeeFace on your Linux machine using Bottles, Lutris, PlayOnLinux or similar tools you just have to do the following:</p> Start VSeeFace.</li> Right in the main ui on the top right set Camera</em> to [OpenSeeFace tracking]</em></li> Make sure Port</em> matches the port in Facetracker.</li> </ol> Note:</strong> If you change IP</em> to an IP-Address on your local network running Facetracker you can get tracking data from that device.</p> Afterwards choose your Avatar or click on Start</em> to use the default one provided.</li> </ol> VSeeFace should pick up the tracking data from Facetracker right away.</p> </div> Facetracker with VTube Studio 2025-09-05T15:05:00+00:00 Facetracker can be used with VTubeStudio. The setup for this is rather simple.</p> Inside Steam right-click VTube Studio and chose Properties</em></p> </div> Navigate to Installed Files</em> and click on Browse...</em>.</p> </div> This will open up your file browser at the install location of VTube Studio.</p> In here navigate to VTube Studio_Data/StreamingAssest/</em> and create a new file called ip.txt</em>.</p> </div> </div> </div> Open that file and enter:</p> ip=0.0.0.0 port=11573 </code></pre> Make sure port</em> matches Facetracker's port.</p> Note:</strong> If you set ip</em> to any IP-Adress of any other device in your local network running Facetracker you can receive tracking data from that device.</p> After restarting VTube Studio and running Facetracker the tracking data should get picked up right away.</p> Reference</h2> DenchiSoft - Running-VTS-on-Linux</a></li> </ul> Milestone: Alpha - Space Conflicts: Empires 2025-09-04T14:12:00+00:00 </div> The Alpha milestone will include a fully working dedicated server as well as game client. There will be no single player available as of now because we do not have NPCs yet. What can be done is to host a local server and play with friends from the same network or just to explore the game.</p> Additionally, the alpha will include some test for scalability as the dedicated server will spawn child processes who's only purpose is to simulate independent scenes in the background the main server than will send over the network to clients in order for them to actually do something.</p> Players will not be able to do much except of building spacecrafts, command fleets to fly somewhere and colonize new worlds. Fleet to fleet combat will not be included in the alpha as of now or to conquer enemy worlds.</p> There will be a basic settlement systems where players can construct new buildings and mine resources.</p> The alpha primarily serves as a proof of concept that the game as we envisioned does even work with Godot and to uncover potential improvements we may be able to add to the engine.</p> The first actual milestone which will focus on more and actual gameplay is Stargazer. Parts of it are already included in Alpha but not fully wired up. Hence, Stargazer will improve on all the loose ends of the Alpha.</p> Space Conflicts: Empires is build with multiplayer in mind right from the start. In fact the single-player will function by running a local server too but just with one client connected.</p> KDE Plasma 6 tiling 2025-09-02T17:57:00+00:00 </div> Pressing Meta + T</em> opens up KDE's tiling editor. This is not to be confused with regular window snapping to one half or a quarter of the screen. In fact this is a more advanced tiling feature. Not as dynamic as with the likes of Hyprland, i3 or sway. But till very mighty feature.</p> </div> After users have setup their tiling layout hold down Shift</em> and drag</em> a window. Now it can be align along the tiling setup done before.</p> </div> Source</h2> Linux Guides Forum - Tiling in KDE Plasma 6: Wie nutzen?</a></li> </ul> Videos with alpha transparency 2025-09-01T21:56:00+00:00 Usually and on many sources online it is common to share special effects (VFX) used to enrich videos with a colored background. Often times green or blue. Then the artists has to use a chroma key filter to then extract said background color and make it transparent. But this does not need to be the case as we can create special effect video files with a baked in alpha channel.</p> For this we can make use of Blender.</p> Setup your effect in Blender</li> Navigate to Film</em></li> Check transparent</em></li> Render your animation into PNG</em> or webp</em> files with alpha channel</em> enabled.</li> </ul> </div> After this has been done then open a new Blender file New</em> -> Video editing</em></p> Import your previously rendered animation as an image sequence</em></li> </ul> </div> Navigate to Output</em></li> Choose FFmpeg Video</em></li> Select QuickTime</em> as Container</em></li> Set Video Codec</em> to QuickTime Animation</em></li> A new button will appear below FFmepg Video at Color</em></li> Set RGBA</em></li> Export the video</li> </ul> </div> Tada alpha channel VFX.</p> Here is a comparission between the color keyed VFX (right) and the alpha channel one (left). As we can see sometimes there will be get a colored shim around the effect. In this case green because the background of the VFX was green.</p> </div> Also using color key based approach will force artists to keep any eye out on colors used for the VFX as the chroma key filters do not know which part of an image is the VFX and which part is not. Or to work with masks and the likes. Green is Green. Also we save a ton of time setting up a chroma key filter in the first place. Simply put the VFX onto the footage and that's it.</p> Source</h2> </div> Spherical Textures 2025-09-01T12:58:00+00:00 While working on Space Conflicts: Empires</a> we had to create textures for spheres (eg. planets and stars). However a texture is a 2d rectangular image and mapping them on a sphere may cause distortions or seams. Therefore the texture needs to be "aware" of being mapped to sphere.</p> </div> The easiest way to generate such a texture is to create a procedural texture in Blender which is applied to a sphere and "just" render it into a file.</p> Put a camera inside a sphere</li> Disable all lighting as otherwise the camera will only see black</li> Switch to cycles as Eevee does not support the feature we need</li> Change the camera projection mode to panorama. Which tells Blender to render a 360° view of the entire scene</li> Render the image and store it into an image file</li> Import this texture into Godot and apply it to a shader which is then applied to a sphere</li> </ul> </div> </div> Tada, a seamless spherical texture with no distortions.</p> </div> This is what the actual texture then will look like:</p> Planar</strong>:</p> </div> Spherical</strong>:</p> </div> Source</h2> </div> Space Conflicts: Empires - Client Settings 2025-08-31T20:22:00+00:00 </div> Client settings are located at:</p> Linux</strong>: ~/.local/share/godot/app_userdata/Space Conflicts- Empires - Client/</code> Windows</strong>: %APPDATA%/godot/app_userdata/Space Conflicts- Empires - Client/</code></p> sce_client.json</h2> A typical config file looks like:</p> { "CHATTING_ENABLED": true, "PLAYER_ID": "1e078546-91c1-4330-ac69-87530bab6b59", "PLAYER_NAME": "ExuberantHornet", "THEME_ICONS_UI": 1, "THEME_IMPOSTOR": 0, "UNIQUE_PLAYER_ID": true } </code></pre> CHATTING_ENABLED</strong>: Values</em>: true</code>, false</code> Default</em>: true</code> Description</em>: Control whether a player wants to globally enable the chat feature if connected to a server. As the server side chat is entirely passive. Which means chat messages have to explicitly be fetched by the player and are not send by the server. This will disable any call or any chat related RPC function for this client.</p> PLAYER_ID</strong>: Values</em>: UUID4</code> Default</em>: Random Description</em>: The player id is used by servers to reference players. Since the clientid assigned to a layer upon connecting to a server is random it can not be used to reference players across reconnects or loading a saved game. THis also means if another player knows the PLAYER_ID</code> of any other player they can join a server as said other player. To prevent PLAYER_ID</code> abuse future client version will generate a unique per server PLAYER_ID</code>.</p> If the game is launched for the first time it will generate a random and unique PLAYER_ID</code>. This is not done through fingerprinting. This means deleting the sce_client.json file will reset the PLAYER_ID</code> to a new and random value.</p> Note</strong>: Player ids are never shared with other client as the dedicated server acts as a relay between clients. This means there is no peer-to-peer connection between clients and thus only the server knowns which currently connected client id belongs to which PLAYER_ID</code>.</p> PLAYER_NAME</strong>: Values</em>: Anything Default</em>: Random Description</em>: The players name as shared with other clients via a server. The name can be changed at any time and many players can also share the same name. Since players are identified based on their PLAYER_ID</code></p> THEME_ICONS_UI</strong>: Values</em>: 0</code>, 1</code> Default</em>: 1</code> Description</em>: The game supports multiple themed for UI icons as used in the game. Currently there are two available: schematic</code> and realistic</code>. This controls how any entity in game is represented in any overview or in-game window.</p> THEME_IMPOSTOR</strong>: Values</em>: 0</code>, 1</code> Default</em>: 0</code> Description</em>: An impostors is a 2D image of a 3D object used to save some performance in-game for far away entities. This settings controlls how these should appear either in the schematic</code> or realistic</code> theme.</p> </div> UNIQUE_PLAYER_ID</strong>: Values</em>: true</code>, false</code> Default</em>: true</code> Description</em>: This setting will be removed in future versions. Originally we planed on making it configurable if a player wants to share their PLAYER_ID</code> across all servers. However due to the PLAYER_ID</code> being exposed to server administrators and to prevent abuse of player ids we've decided to generate a unique player ids for each server a player joins. This toggle therefore was meant to make this behaviour configurable.</p> Source</h2> </div> Space Conflicts: Empires - Sever Settings 2025-08-31T13:58:00+00:00 </div> Server configuration files can be found at: ~/.local/share/godot/app_userdata/Space Conflicts- Empires - Dedicated Server/</code>.</p> sce_server_config.json:</strong> Contains basic server configurations. Save Games:</strong> Are located at save_games/</code> inside the same directory as sce_server_config.json</em></p> sce_server_config.json</h2> A typical server config file looks like:</p> { "chatting_enabled": true, "game_mode": 0, "master_token": "1224544341", "port": 5000, "save_game_dir": "save_1", "server_description": "Just an ordinary standart Space Conflicts: Empires game server.", "server_name": "Horse Palace" } </code></pre> chatting_enabled</strong> : Values</em> : true</code> / false</code> Default</em> : true</code> Description</em> : Server wide enable or disable of chat function. This settings might be useful for UK users to comply with the Online Safety Act. By disabling the chat users will not be able to communicate in-game and hence free server administrators to monitor their chat interactions.</p> If chatting is disabled on the server the server will not accept or respond to any chat related RPCs.</p> game_mode</strong> : Values</em> : 0</code>, 1</code> Default</em> : 0</code> Description</em> : Controls whether the server should run in lobby</code> (0) or endless</code> (1) mode.</p> Lobby</em> : Is a dedicated server mode to only allow players to join during the setup phase eg. players join a lobby and the game will start when everyone is ready. After the game has been launched no players will be able to join. Also if a player disconnects from a server either by accident or on purpose the game will be paused. Unless all remaining players choose to continue playing or save and quit the game.</p> Endless</em> : Is a mode which is not yet implemented but wil later on serve as a specialized MMO like always on mode. Where the server accepts new players any time. If a new player joins the game and has not yet been known by the server they will get assigned a new home world and start playing. Also in endless mode there will be a configurable "noob mode" which will put players in tiers based on their in-game point to allow / disallow strong players to combat weaker players. Only players in the same tier are allowed to combat each other. This "noob mode" will also be able to turn off entirely.</p> master_token</strong> : Values</em> : Anything Default</em> : Random Description</em> : Serves as a server side master password. Players which know this password can authenticate themselves as server administrator and get access to admin features.</p> Upon launching a dedicated server and no sce_server_config.json</em> was found it will generate a new random master token. This is to prevent servers to be available with well known default tokens.</p> port</strong> : Values</em> : 0</code> - 65535</code> Default</em> : 5000</code> Description</em> : Defines the network port a dedicated server is bound to.</p> Note:</strong> Not all port numbers are valid. Usually there are some system reserved ports in the range 0</code> - 1023</code> and it is not recommended to use any of these.</p> save_game_dir</strong> : Values</em> : Anything Default</em> : save_1</code> Description</em> : Defines the directory at save_games</code> where the server will store save game files to.</p> server_description</strong> : Values</em> : Anything Default</em> : Just an ordinary standart Space Conflicts: Empires game server.</code> Description</em> : Will later on server as a server description visible in a yet to be implemented server browser.</p> server_name</strong> : Values</em> : Anything Default</em> : Random Description</em> : Is the name of the server. Similar to server_description</em> it will server as a server name for a yet to be implemented server browser. Also this name is used for naming lobbies.</p> Source</h2> </div> Nvidia driver on Aeon and Kalpa 2025-08-31T11:46:00+00:00 </div> Kalpa and Aeon are Wayland only Linux Distribution. This means nVidia GPUs and drivers not supporting Wayland are not going to work! This applies to any GPU only supported by the 390 or older driver series or the Fermi (GTX 400/500)</em> and older micro architectures.</p> It is recommended to have at least a nVidia GPU supported by driver version 496.44 or newer. Older drivers might work but with limited user experience and is not recommended.</p> Attention:</strong> Follow every step carefully as the installation may otherwise end in an unbootable/broken system, with broken auto updates or missing display output. Also throughout this guide please reboot only if this has been explicitly stated.</p> Determine supported driver driver package</h2> It is important to determine the supported driver version first. The easiest way is by looking up nVidias driver download page</a>. Do not download the nVidia Installer</strong> from there as it will not work with Kalpa or Aeon.</p> If you know the micro architecture of your GPU the following should work with Kalpa or Aeon:</p> Kepler (GeForce 600, 700, 800M) with limited functionality</strong></li> Maxwell (GeForce 700, 800M, 900)</li> Pascal (GeForce 10 series, Quadro P, Tesla P4)</li> Turing (GeForce 16, 20)</li> Ampere (GeForce 30)</li> Ada Lovelace (GeForce 40)</li> Blackwell (GeForce 50)</li> </ul> The best experience you will have with Turing and newer as these GPUs can also make use of nVidias open Kernel Module.</p> If the GPU is supported by the 500 driver series the G06 driver package is required. For 400 series G05. Everything else is not supported.</p> Setup system</h2> Before we can begin with the driver installation it is important to do the following config changes first.</p> Setup zypper</h3> Open up a terminal and enter: sudo sed -i 's/# autoAgreeWithLicenses = no/autoAgreeWithLicenses = yes/' /etc/zypp/zypper.conf</code></li> </ul> This is important to not break Kalpa and Aeon's auto update as the nVidia driver packages requires the user to agree with the nVidia EULA. As the automated update is running in the background no user interaction is possible here.</p> Setup transactional-update</h3> Create a new snapshot: sudo transactional-update shell</code></li> Add a new file with echo "ZYPPER_AUTO_IMPORT_KEYS=1" > touch /usr/etc/transactional-update.conf.d/40-auto-import-keys.conf</code></li> Close the snapshot: exit</code></li> </ul> This is important as the nVidia repository signing key might change at any given time. If the system dose not import the key by itself the auto updated might break at any given time and/or the health checker might run havoc and cause the system to permanently reboot.</p> Add nVidia driver repository and install driver</h2> Still in Terminal run sudo transactional-update -c pkg in openSUSE-repos-MicroOS-NVIDIA</code>.</p> G06 with open source Kernel module</h3> Recommended for: Turing, Ampere, Ada Lovelace, Blackwell</p> Install the driver using:</p> sudo transactional-update -c shell zypper -n --gpg-auto-import-keys in --auto-agree-with-licenses openSUSE-repos-MicroOS-NVIDIA zypper -n --gpg-auto-import-keys in --auto-agree-with-licenses nvidia-open-driver-G06-signed-kmp-meta version=$(rpm -qa --queryformat '%{VERSION}\n' nvidia-open-driver-G06-signed-kmp-default | cut -d "_" -f1 | sort -u | tail -n 1) zypper -n --gpg-auto-import-keys in --auto-agree-with-licenses nvidia-compute-utils-G06 == $version nvidia-persistenced == $version nvidia-video-G06 == $version exit sudo transactional-update -c initrd </code></pre> Reboot. The driver should work right away.</p> G06 with closed source kernel module</h3> Recommended for: Maxwell and Pascal</p> Installing the driver can be done using:</p> sudo transactional-update -c -i pkg in nvidia-driver-G06-kmp-meta sudo transactional-update -c initrd </code></pre> The driver will not load yet if you have Secure Boot enabled. Continue with secure boot below after you have rebooted the system.</p> G05</h3> Recommended for: Kepler</p> Note:</strong> While these driver series has worked to some degree with Kalpa and Aeon in our tests they do not provided a very good user experience due to lack of modern Wayland support. If using these drivers expect issues which can not be fixed. Also the G05 driver series often times does not compile for the latest Linux Kernel and manual intervention may be required.</p> Installing the driver can be done using: sudo transactional-update -c pkg in nvidia-gfxG05-kmp-default x11-video-nvidiaG05 nvidia-glG05 nvidia-computeG05</code>.</p> For a successful driver installation we also need to configure a few additional things:</p> Append rd.driver.blacklist=nouveau</code> to sudo vim /etc/kernel/cmdline</code></li> Create a new file sudo touch /etc/modprobe.d/nvidia.conf</code> and enter: options nvidia-drm modeset=1</code></li> Then run sudo transactional-update -c initrd</code></li> </ul> The driver will not load yet if you have Secure Boot</strong> enabled. Continue with secure boot below after you have rebooted the system.</p> Secure boot</h1> For G06 with the open kernel module this step is not required as the open module is already signed by the systems own secure boot keys.</p> With the closed source driver module the MOK (machine owner keys) have to be manually enrolled in order for the driver to get loaded. To do so run:</p> G06 with closed source kernel module:</strong> sudo mokutil --import /usr/share/nvidia-pubkeys/MOK-nvidia-driver-G0<X>-<driver_version>-<kernel_flavor>.der</code> and provide an easy to type and remember password as we will need it at the next reboot.</p> G05:</strong> sudo mokutil --import /usr/share/nvidia-pubkeys/MOK-nvidia-gfxG0<X>-<driver_version>-<kernel_flavor>.der</code> and provide an easy to type and remember password as we will need it at the next reboot.</p> Afterwards reboot. The system should show a Perform MOK management</em> screen. Choose Entoll MOK</strong> followed by Continue</strong> and answer Enroll the keys(s)</em> with Yes</strong> then provide the password set while using mokuitls. If the enrollment failed it can be re-enrolled using the above commands again.</p> </div> Optimus</h2> For Laptop users which do have an integrated and a dedicated (presumably nVidia) GPU, also called Optimus Laptop, may want to read the following.</p> Offloading</h3> To offload an application or game to the dedicated nVidia GPU it is required prefix the launch command with a few environment variables to make them run on the nVidia GPU:</p> __GLX_VENDOR_LIBRARY_NAME=nvidia</li> __NV_PRIME_RENDER_OFFLOAD=1</li> __VK_LAYER_NV_optimus=NVIDIA_only</li> </ul> For Steam you can add the following as a game launch option for example: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only %command%</code></p> You can verify this by running nvidia-smi</code> from terminal and see if the requested application is listed in the Processes table at the bottom of the screen.</p> </div> Power management</h2> If the nVidia GPU is of the Pascal (GTX 10) or older</strong> micro architecture it is recommended to install additional software, as these GPUs stay powered on if not in use. To forcefully power them down or up install prime-select and bbswitch as follows:</p> sudo transactional-update pkg in bbswitch-kmp-default suse-prime</code> After the next reboot also enable the prime-select service as follows: sudo systemctl enable --now prime-select.service</code></p> To set which GPU should be used at boot time run: sudo prime-select boot intel|offload</code>. The intel</code> mode will also work for integrated AMD iGPUs.</p> To switch the mode on-demand you can run: sudo prime-select intel|offload</code> log out and in again. The nVidia GPU should now be powered on or off and the driver loaded or unloaded depending on which mode has been chosen.</p> Note: Only use intel</code> or offload</code> with out the pipe</strong> Note 2: The nvidia</code> mode does only work on X11 which is not supported on Kalpa and Aeon</strong></p> For a graphical user interface we recommend OptimusUI</a> which we've developed for this purpose.</p> Addional notes about driver support</h2> nVidia installer</strong>: Do not use the driver installer provided by nVidia it does not work with Kalpa and Aeon as it does not expect a Linux distribution to be immutable and will therefore write certain files into the wrong directories as well as DKMS will fail to generate the kernel module. 390 or older</strong>: These drivers will not work with Kalpa and Aeon 496.44 or newer</strong>: Recommended by KDE for Plasma 6 with Wayland 555.58 or newer</strong>: Is recommended for the best possible Wayland experience with the proprietary nVidia driver. As these driver series and newer contain a lot of improvements and tweaks to work best with Wayland.</p> Sources</h2> openSUSE Wiki about nvidia driver install</a></li> KDE Wayland nVidia</a></li> nVidia 555.58 release notes</a></li> </ul> Direct3D Wrappers 2025-08-31T00:20:00+00:00 As it is common that Direct3D is only supported on Microsoft Windows other operating systems need to rely on so called translation layers to render Direct3D content. This page serves as an overview about common translation layers which do work on Linux.</p> WineD3D</h2> One of the most prominent and oldest Direct3D wrappers is WineD3D which stands for Wine Direct3D. While Wine stands for Wine Is Not an Emulator. This is true for WineD3D as well. Instead of "emulating" a Direct3D device it does in fact understand Direct3D calls and then maps them to corresponding OpenGL calls.</p> WineD3D is part of Wine it self and works with Direct3D 1 up to 11. Also there is ongoing work to port the OpenGL based WineD3D to a Vulkan based WineD3D for Direct3D 1 up to 9.</p> DXVK</h2> Another very well know translation layer is the Vulkan based DXVK. Originally developed to play NieR Automata on Linux by Philip Rebohle it has become a part of Valves Wine fork Proton and powers modern Linux Gaming.</p> DXVK supports Direct3D 8 up to 11. While originally it only supported Direct3D 10 and 11.</p> D9VK:</strong> Now part of DXVK was D9VK but once independent as a Vulkan based Direct3D 9 to Vulkan translator</p> D8VK:</strong> Similar to D9VK and also now part of DXVK is D8VK for Direct3D 8 to Vulkan.</p> D7VK:</strong> Pretty much as like all the other D*VK's is this a Direct3D 7 to Vulkan mapper. D7VK is still in development but also the developer claimed it will never be compatible with all application using Direct3D 7 as the API was not very well defined.</p> See: https://github.com/WinterSnowfall/d7vk</a></p> DXVK-native:</strong> Is a fork of DXVK with the goal to be used without Wine. It is often used to help game developers porting their Direct3D games to Linux. Prominent users of DXVK-native are Portal 2, Left 4 Dead 2 and Half-Life 2 by Valve.</p> DXVK-nvapi:</strong> Is not a translation layer by itself but rather a re-implementation of the nVidia API (NVAPI) which allows games to query and use certain features of a nVidia GPU with the proprietary driver such as DLSS and PhysX.</p> VKD3D</h2> Developed by the Wine project as a Direct3D 12 to Vulkan mapper. Often confused with VKD3D-proton</strong>. Which itself is a fork of VKD3D developed by Valve and integrated with Proton.</p> VKD3D also relies on DXVK-nvapi to access additional features of nVidia GPUs.</p> eOn</h2> Is a proprietary Direct3D to OpenGL mapper developed by Virtual Programming and used in the Linux port of BioShock Infinite, The Witcher 2: Assassins of Kings, Saints Row 3 and a few others.</p> Tungsten</h2> Is a proprietary Direct3D to OpenGL mapper developed and used by Feral Interactive in their earlier Linux ports. Such as Tomb Raider (2013), Alien Isolation, Mad Max and others. Later on they moved on to Feral3D. Sometimes also called "IndirectX". But which name applies is not very well known.</p> Feral3D</h2> Is a proprietary Direct3D to Vulkan mapper developed and used by Feral Interactive in their later Linux ports before they stopped porting to Linux. Prominent games using Feral3D are Rise of the Tomb Raider, Shadow of the Tomb Raider as well as a public beta for Mad Max and Lords of the Rings: Shadow of Mordor.</p> ToGL</h2> Before using DXVK-native Valve used their own ToGL in their Source Engine 2 Linux games to map Direct3D to OpenGL.</p> Sources</h2> Virtual Programming Linux Ports</a></li> Holarse Wiki about eOn</a></li> GitHub DXVK</a></li> Wine Gitlab VKD3D</a></li> Github VKD3D-proton</a></li> Github Valve ToGL</a></li> Wine HQ Registry keys</a></li> Phoronix WineD3D Vulkan</a></li> </ul> GTK4 apps hang on nVidia or corrupted rendering on AMD and Intel 2025-08-30T20:26:00+00:00 </div> Note:</strong> This issue has been fixed with the nVidia driver 580.82.07</em> please update to this or a newer version.</p> With GTK4 the GTK-Developers added a new render backend which can either use OpenGL or Vulkan to draw windows on to the screen. However with the nvidia 580 driver series the default (vulkan</code>) can cause GTK4 / libadwaita application to hang upon closing. (Force quit)</p> Also on AMD and Intel GPUs using the open source driver stack there can be rendering artifacts too due to this.</p> Some older Intel iGPUS do have limitted Vulkan support which might cause the GUI toolkit to think it can use Vulkan on that devices while it can't. As an result there are blank windows or apps straig out crashing.</p> To fix these issues create a new file at: ~/.config/environment.d/envvars.conf</code> with GSK_RENDERER=ngl</code> as it's content.</p> Flatpak:</strong> If most applications run via flatpak this file will have no effect and thus this environment variable needs to be set as a flatpak override: flatpak override --user --env=GSK_RENDERER=ngl</code>.</p> Flatseal:</strong> Some can also use Flatseal to set this override. Navigate to All Applications / Global</code> scroll down until you read Variables</code> and enter GSK_RENDERER=ngl</code></p> For KDE users this override must be set either by using Flatseal or the command line. Plasmas own application permission screen does not allow for global overrides.</p> To revert this setting to it's default either remove these overrides / envvars.conf file or set it to GSK_RENDERER=vulkan</code> before launching an GTK4 application to test if the issue has been fixed.</p> Sources:</strong></p> Arch Linux Forums</a></li> nVidia Developer Forums - 580 release discussion</a></li> Fixed driver version - nVidia developer forums</a></li> openSUSE Forums - GTK4 native apps on Gnome show blank windows (Haswell graphics)</a></li> </ul> Change log</h2> 2025-12-03 Added Intel and AMD</li> Changed title and descritpion</li> Changed tags</li> Added openSUSE Forums as source</li> </ul> </li> </ul> Linux Distributions 2025-08-30T18:08:00+00:00 </div> As mentioned in one of our tutorial Videos some does usually not need a dedicated Linux distribution to run old or out-dated hardware in [current year]. However as also mentioned there are still some special cases where a Linux distribution with certain capabilities might be required. On this page we try to keep a list of such Linux systems supporting any or all of these "special requirements"</p> Legacy Boot</h2> These distributions can be installed on systems without an UEFI.</p> Tumbleweed</a></li> Kalpa</a></li> Linux Mint</a></li> </ul> 32bit install</h2> These distributions can be installed on 32bit hardware. By this we do not mean the ability to run 32bit software. But rather the entire distribution being 32bit.</p> Tumbleweed</a></li> </ul> 32bit execution support</h2> The following Linux distributions allow to run 32bit software natively. Without the use of flatpak or distrobox</p> Tumbleweed</a></li> Linux Mint</a></li> </ul> X11 support</h2> These distributions do allow for running them without Wayland. Which does not mean they do not support Wayland at all.</p> Tumbleweed</a></li> Linux Mint</a></li> </ul> Distributions running on x86_64_v1</h2> The following distributions do not require a 64bit capable system to have a certain x86_64 feature level in order to run.</p> Tumbleweed</a></li> Kalpa</a></li> Linux Mint</a></li> </ul> Quake 4 on Linux 2025-08-30T17:42:00+00:00 </div> Quake 4 is one of those games from id Software which does has a native Linux version but was never released under an open source license. Therefore no source ports do exist to play this game on Linux today. One way is to just use Wine or Proton to play it. If some does prefer the native version it can still be run on a modern Linux distribution with all the latest techs such as Wayland, Pipewire and even without 32bit support.</p> Install Quake 4</h2> In order to run the game on Linux you need the original game date from either the retail CDs or Steam.</p> Download the game and copy q4base</code> from the Windows version to any location where you want the Linux version to be installed.</li> Download the installer from here</a>. However on a modern 64bit Linux distribution this installer can not be executed as it does perform some system checks. To circumvent these checks run the installer as follows:</li> </ul> chmod +x ./quake4-linux-1.4.2.x86.run ./quake4-linux-1.4.2.x86.run --target quake4linux </code></pre> Then merge quake4linux/q4base</code> to the location with the previously copied q4base</code> form the Windows version.</li> Next also merge quake4linux/us/q4base</code> or quake4linux/germany/q4base</code> depending on your games langauge with the previously copied q4base</code></li> Copy all files from bin/Linux/x86/</code> next to q4base (not inside it)</li> Run quake4.x86</code></li> </ul> For systems without 32bit support we recommend running the game via Lutris</a> as a flatpak. Perform the setup as described above. Then add a new game to Lutris by choosing locally installed game and set it up to run quake4.x86 form the game directory.</p> Note:</strong> quake4smp.x86 does not work properly as it requires the provided libSDL-1.2.id.so.0 which creates a garbage window</p> Sources</h2> Linux Installer: https://lutris.net/files/games/quake-4/quake4-linux-1.4.2.x86.run</li> Quake 4 on Steam: https://store.steampowered.com/app/2210/Quake_4/</li> </ul> OptimusUI 2025-08-30T13:59:00+00:00 Optimus UI is a wrapper application written in python, libadwaita and GTK4 for prime-select. It's primary purpose is to provide one singular interface across many different linux distributions. Also it should be easy to install which is why it is shipped as a flatpak. This way users do not have to rely on their distribution maintainers to include a user interface to be used with prime-select.</p> </div> In the past we also maintained a Gnome Extension but these are prone to break with every Gnome update. Therefore to lower the maintenance burden we've come to the conclusion to provide a singular application. Also to not need to fight distribution specific dependency changes or to rely on a distribution to ship certain libraries themselves we also made it a flatpak.</p> </a> </div> Arbitrary permissions</h2> On flathub OptimusUI is marked as potentially unsafe</strong> which is true to some extend. Because OptimusUI has to access the hosts prime-select binary to trigger the switch of the GPU mode. For this it has to use flatpak-spawn --host</code> followed by either pkexec</code> or kdesu</code> to run prime-select</code> with superuser privileges</strong>. There currently is no other way to do this as flatpak does not allow for specifying a list of host binaries accessible to the sandbox.</p> While OptimusUI has the "power" to access anything on the host system we do not use this power outside the purpose of this application. You can also inspect the applications source code anytime here</a></p> Also OptimusUI uses this power to access /etc/os-release</code> of the host system. Because inside the flatpak sandbox this file will only give intel on the Flatpak runntime used. But depending on the host distributions the distribution provided prime-select has different capabilities. Therefore we need to check the actual distro to then determine which kind of prime-select is available and which features to expose in the user interface.</p> Limittations</h2> While being a flatpak application OptimuUI comes with a few limitations. For OptimusUI to work the host system requires prime-select</code>, bbswtich</code> and the nvidia kernel module</code> all which can not be shipped via flatpak. These are dependencies which need to be provided by the target distribution themselves.</p> Supported Prime tools</h2> Depending on the Linux distribution in use the actual package containing the prime-select</code> binary can be different. Currently OptimusUI has support for the following tools:</p> SUSEPrime</li> nvidia-prime</li> fedora-prime-select</li> nvidia-prime-select</li> </ul> Prime Features</h3> If looking the the applications source code OptimusUI internally validates the running distribution and the used prime tool to determine which operating modes are available and thus exposes or hides away certain elements in the user interface.</p> SET_BOOT</strong>: The prime tool can set the operation mode to be applied on boot. Therefore on every reboot of the system this mode is restored.</p> Only supported on SUSE and Debian based distributions</li> </ul> SET_OFFLOAD</strong>: Is a dedicated operating mode where both GPUs the iGPU and the dGPU are active and can be used simultaneously. Nvidia calls this PRIME Offloading</code>.</p> Only supported on SUSE and Debian based distributions</li> Works on Wayland and X11</li> </ul> SET_NVIDIA</strong>: Will make the nVidia (dGPU) the primary GPU and the integrated GPU will not be used.</p> Supported on all distributions with a supported prime tool.</li> Only works on X11</li> </ul> SET_INTEGRATED</strong>: Will make the iGPU the only active GPU and the nVidia GPU will be turned off if bbswitch is installed.</p> Works on all distributions with a supported prime tool</li> nVidia GPU will turn of on SUSE based distributions. If it also does on other distributions is unknown.</li> Works on Wayland and X11</li> </ul> GET_CURRENT</strong>: Will allow OptimusUI to determine the currently active operating mode eg. nvidia, integrated or offload.</p> Only works on SUSE and Debian based distributions</li> </ul> SERVICE</strong>: This prime feature is not yet implemented as only SUSE based distributions support this operation.</p> PRIME Offloading</h2> If the system is in Offload</code> mode some can run an application on the nvidia GPU using the following environment varibales: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only</code> followed by the application to be run.</p> Note:</strong> Some distributions ship with switcherooctl</code> which at least on Gnome based desktop environments allows to run an application on the dedicated GPU by right-click an application launcher and choose Run with dedicated / integrated GPU</code>.</p> For *.desktop files to specify which is their prefered GPU some can add PrefersNonDefaultGPU=true</code> to the [Desktop Entry]</code> section. This will cause Gnome (and other switcheroo aware desktops) to run an application on the GPU which is not the currently active one. Usualyl the "NonDeffaultGPU" is the dedicated one. However if a system is running in Offload</code> mode and the GPU driving the displays is already the dGPU then the "NonDefaultGPU" will be the iGPU.</p> This can be an issue on desktops with integrated GPUs in their CPU but the user might not had disabled it via the BIOS and thus the iGPU is also available.</p> Without flatpak</h2> While OptimusUI does some checks to determine if it is running inside or outside of flatpak this is not very well tested. But in theory should work. The reason for this is to allow for distributions to re-package the application without flaptak in mind. But distribution maintained packages are not supported by us. Therefore if you did not install OptimusUI from flathub and run into errors please make sure this does also apply to the flatpak release. Otherwise please file an issue to your distribution.</p> Test environments</h2> OptimusUI has been tested on the following system configurations:</p> MSI CX61 0OD</strong></p> OS: Aeon, Kalpa</li> Desktops: Gnome, KDE Plasma</li> dGPU: nVidia GT 730M</li> iGPU: Intel HD 4000</li> nVidia Drivers: 470.256.02, 470.239.06</li> Prime-Tool: SUSEPrime: 0.8.17, 0.8.18</li> </ul> </li> Linux Kernel: 6.xx</li> Package format: Flatpak</li> </ul> When is OptimusUI / prime-select usefull?</h2> GPU based on Turing (GTX 16 / RTX 20 series) or Newer nvidia driver 435 or newer: NO</li> nvidia driver older than 435: YES But the GPU will probably not work because earlier drivers might not have support for it anyway</li> </ul> </li> </ul> </li> GPU based on Pascal (GTX 10 series) or earlier: YES This will require nVidia driver 390 or newer</li> bbswitch is recommended to actually turn off the GPU if not in use as these and older GPUs lack the required power management features (e.g. GSP coprocessor)</li> </ul> </li> Open source nvidia drivers: NO</li> </ul> OptimusUI will evaluate most of these requirements on its own and notify the user. However, it does not validate the nvidia driver version as of now.</p> NOTICE: Depending on your distribution the package for prime-select might depend on further requirements not listed here</p> How does OptimusUI work</h2> OptimusUI will do a brief system survey by this it checks the following things:</p> If prime-select can be found in one of the following locations (escaping the sandbox using flatpak-spawn) following path: /usr/bin/prime-select</code></li> /usr/sbin/prime-select</code></li> /bin/prime-select</code></li> /sbin/prime-select</code></li> </ul> </li> </ul> Once a supported prime tool has be identified OptimusUI will then scan for compatible hardware with the pci vendor id 0x10DE</code> and device class 0x30000</code> (dekstop GPU) or 0x30200</code> (mobile GPU).</p> In the next step it will evaluate the device name using lspci -d 10DE:DEVICE_ID</code>.</p> Additionally OptimusUI will look for one of the following sudo tools pkexec</code> or kdesu</code> in order to show a graphical authentication dialog on the host system if prime-select</code> required superuser privileges.</p> Furthermore it does check the users host distribution by running flatpak-spawn --host cat /etc/os-release</code> and evaluate it's content.</p> Finally to use any prime-select feature it will escape the sandbox and run one of these commands depending on what the user clicked:</p> flatpak-spawn --host [pkexec/kdesu] (-c) prime-select (boot) [nvidia/intel/offload]</code></li> flatpak-spawn --host prime-select get-current</code></li> </ul> Sources</h2> Flathub: https://flathub.org/apps/de.z_ray.OptimusUI</li> Source Code: https://codeberg.org/ZRayEntertainment/optimus-ui</li> </ul>

Z-Ray Documentation

Facetracker FAQ

Does Facetracker support handtracking?</h2> No. Facetracker is only an OpenSeeFace wrapper application which does not have support for handtracking.</p>

Does Facetracker use GPU Acceleration?</h2> While the GTK4 interface itself is GPU accelerated this does not apply for the facetracker of OpenSeeFace. This one only runs on CPU.</p>

Installing Kalpa Desktop

Language and Keyboard</h3> As the first step, after the installer has been loaded, choose your preferred langauge and keyboard layout.</p>

System Role</h3> Afterwards the installer ask for the System Role. As Kalpa currently shared the same installer as the server orientated MicroOS there are several MicroOS roles. Choose openSUSE Kalpa (Plasma) [ALPHA]</strong></p>

NTP Configuration</h3> You can leave this screen as it and just advance with Next</strong>.</p>

KWallet</h3> If connecting to a WiFi network KDE will show the initial KWallet setup screen. Choose Classic, Blowfish encrypted file</em> type in an easy to remember passwort, or none.</p>

Silent Boot</h3> If you are not a fan of text scrolling over your display while booting the system we can suppress this screen as follows:</p> Open Konsole and enter:</p>

Hide boot loader</h3> In case you do not want to see the bootloader and wait for 5 seconds until the system boots you can hide this interface so it only comes up if required (pressing any arrow key or space while booting).</p> Open Konsole and enter:</p>

FAQ</h2>

E:D Market Connector on Linux and Steam Deck

Waydroid on Kalpa Desktop and Aeon Desktop

Install Longterm Kernel</h2> Throughout our testings we've noticed some instability using the -default Kernel using the binder kernel module as installed via anbox-modules. This can be Waydroid simply crashing at random or even cause the entire desktop to freeze.</p>

SecureBoot</h2> For SecureBoot enabled systems we also have to enroll the Machine Owner Key for the anbox-modules. As Kalpa has a root account it should prompt you right away with the MOK enroll screen. The default password on Kalpa is the one of the root</em> account.</p>

Install Need for Speed Underground, 2, Most Wanted and Carbon on Linux

Setup Bottles</h2> In case there is not Bottles environemtn to run these games with create a new one.</p>

Install the games</h2> If using disk images make sure Bottles has proper read access to /run/media/<USER_NAME></em>. You can use Flatseal or KDE's Build-in permission screen for this.</p>

Troubleshooting</h2> While most of the time these steps are the same for all 4 games there a few occasions where some of them require some special tweaks.</p>

Video</h2> </iframe> </div>

Long term support (LTS) Linux kernel on openSUSE Tumbleweed

Open Kerne Modul</h3> Tumbleweed:</strong> sudo zypper in nvidia-open-driver-G06-signed-kmp-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-open-driver-G06-signed-kmp-longterm</code></p>

G06:</h4> Tumbleweed:</strong> sudo zypper in nvidia-driver-G06-kmp-longterm</code></p> Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-driver-G06-kmp-longterm</code></p>

History</h2> 2025-11-19: Added warning about uninstalling -default Kernel</li> </ul> </li> </ul>

CUDA cuInit: Unknown error on Linux

Known affected systems configurations</h2> Linux Kernel: 6.14.6 or newer</li> Flatpak: 1.16.0 or newer</li> Podman: 5.4.2 or newer</li> nVidia driver 570.144 or newer</li>

Missing videos in Wine / Proton

Proton / Wine Troubleshooting

Win2Go Components

Win2Go Troubleshooting

vfat, ntfs or udf not supported</h2> Support for the vfat, ntfs and udf file systems is a hard requirement for Win2Go. If these are not met the application can not continue.</p> vfat: Is used to format the boot partition of Windows</li> ntfs: Is used for the main Windows partition (C:)</li>

Win2Go Unsupported features

Win2Go

32bit Software on 64bit Linux

Steam</h3> There is an unofficial Flaptak of Valves popular game front Steam available on Flathub. Simply download and install. It does contain all the required 32bit compatibility to run all your games and Steam right away with zero setup.</p>

Wine and Proton</h2> Wine and Proton are 64bit applications already. They use WOW64 (W</strong>indows-O</strong>n-W</strong>indows 64</strong>bit) to run 32bit and 16bit Windows applications on 64bit Linux already.</p>

Video</h2> </iframe> </div>

Facetracker with VSeeFace

Facetracker with VTube Studio

Reference</h2> DenchiSoft - Running-VTS-on-Linux</a></li> </ul>

Milestone: Alpha - Space Conflicts: Empires

KDE Plasma 6 tiling

Videos with alpha transparency

Source</h2> </div>

Spherical Textures

Source</h2> </div>

Space Conflicts: Empires - Client Settings

Source</h2> </div>

Space Conflicts: Empires - Sever Settings

Source</h2> </div>

Nvidia driver on Aeon and Kalpa

Setup system</h2> Before we can begin with the driver installation it is important to do the following config changes first.</p>

Setup transactional-update</h3> Create a new snapshot: sudo transactional-update shell</code></li> Add a new file with echo "ZYPPER_AUTO_IMPORT_KEYS=1" > touch /usr/etc/transactional-update.conf.d/40-auto-import-keys.conf</code></li>

Add nVidia driver repository and install driver</h2> Still in Terminal run sudo transactional-update -c pkg in openSUSE-repos-MicroOS-NVIDIA</code>.</p>

Optimus</h2> For Laptop users which do have an integrated and a dedicated (presumably nVidia) GPU, also called Optimus Laptop, may want to read the following.</p>

Direct3D Wrappers

ToGL</h2> Before using DXVK-native Valve used their own ToGL in their Source Engine 2 Linux games to map Direct3D to OpenGL.</p>

GTK4 apps hang on nVidia or corrupted rendering on AMD and Intel

Change log</h2> 2025-12-03 Added Intel and AMD</li> Changed title and descritpion</li> Changed tags</li> Added openSUSE Forums as source</li> </ul> </li> </ul>

Linux Distributions

Legacy Boot</h2> These distributions can be installed on systems without an UEFI.</p>

32bit install</h2> These distributions can be installed on 32bit hardware. By this we do not mean the ability to run 32bit software. But rather the entire distribution being 32bit.</p>

32bit execution support</h2> The following Linux distributions allow to run 32bit software natively. Without the use of flatpak or distrobox</p>

X11 support</h2> These distributions do allow for running them without Wayland. Which does not mean they do not support Wayland at all.</p>

Distributions running on x86_64_v1</h2> The following distributions do not require a 64bit capable system to have a certain x86_64 feature level in order to run.</p>

Quake 4 on Linux

Install Quake 4</h2> In order to run the game on Linux you need the original game date from either the retail CDs or Steam.</p>

Does Facetracker support handtracking?</h2>
No. Facetracker is only an OpenSeeFace wrapper application which does not have support for handtracking.</p>

Does Facetracker use GPU Acceleration?</h2>
While the GTK4 interface itself is GPU accelerated this does not apply for the facetracker of OpenSeeFace. This one only runs on CPU.</p>

NTP Configuration</h3>
You can leave this screen as it and just advance with Next</strong>.</p>

Troubleshooting</h2>
While most of the time these steps are the same for all 4 games there a few occasions where some of them require some special tweaks.</p>

`Video</h2> </iframe> </div>`

Open Kerne Modul</h3>
Tumbleweed:</strong> `sudo zypper in nvidia-open-driver-G06-signed-kmp-longterm</code></p>`
`Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-open-driver-G06-signed-kmp-longterm</code></p>`

G06:</h4>
Tumbleweed:</strong> `sudo zypper in nvidia-driver-G06-kmp-longterm</code></p>`
`Aeon and Kalpa:</strong> sudo transactional-update pkg in nvidia-driver-G06-kmp-longterm</code></p>`

`History</h2> 2025-11-19: Added warning about uninstalling -default Kernel</li> </ul> </li> </ul>`

Wine and Proton</h2>
Wine and Proton are 64bit applications already. They use WOW64 (W</strong>indows-O</strong>n-W</strong>indows 64</strong>bit) to run 32bit and 16bit Windows applications on 64bit Linux already.</p>

Video</h2>
</iframe> </div>

Reference</h2>

DenchiSoft - Running-VTS-on-Linux</a></li> </ul>

Source</h2>
</div>

Source</h2>
</div>

`Source</h2> </div>`

`Source</h2> </div>`

Setup system</h2>
Before we can begin with the driver installation it is important to do the following config changes first.</p>

Add nVidia driver repository and install driver</h2>
Still in Terminal run `sudo transactional-update -c pkg in openSUSE-repos-MicroOS-NVIDIA</code>.</p>`

Optimus</h2>
For Laptop users which do have an integrated and a dedicated (presumably nVidia) GPU, also called Optimus Laptop, may want to read the following.</p>

ToGL</h2>
Before using DXVK-native Valve used their own ToGL in their Source Engine 2 Linux games to map Direct3D to OpenGL.</p>

Change log</h2>

2025-12-03

Added Intel and AMD</li>
Changed title and descritpion</li>
Changed tags</li>
Added openSUSE Forums as source</li> </ul> </li> </ul>

Distributions running on x86_64_v1</h2>
The following distributions do not require a 64bit capable system to have a certain x86_64 feature level in order to run.</p>

Tumbleweed</a></li>
Kalpa</a></li>
Linux Mint</a></li> </ul>