xperia64

/*
   Copyright (C) 2000  Daniel Ryde

   This library is free software; you can redistribute it and/or
   modify it under the terms of the GNU Lesser General Public
   License as published by the Free Software Foundation; either
   version 2.1 of the License, or (at your option) any later version.

   This library is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of

xperia64

#!/usr/bin/env python3

import sys
import os

with open(sys.argv[1], mode='rb') as seeddb:
    seedbyte = seeddb.read()[16:]

try:
    os.mkdir("seed")

xperia64

Just because this was poorly documented, I'm writing how I configured Cxbx-Reloaded to run on the Steam Deck:

• Cxbx-Reloaded CI-8ac5d14 (Thu, Oct 13, 2022 1:39 PM)
• Cxbx-Reloaded CI-a5f4b3b (Fri, May 14, 2021 12:45 PM)
  • They broke shadows in JSRF after this, and helpfully locked the corresponding issue even though it still 100% happens to this day so yeah. At least they didn't close it I guess.
  • https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/releases/download/CI-a5f4b3b/CxbxReloaded-Release-VS2019.zip
• Proton-GE 7-41

1. Add Cxbx-Reloaded as a non-steam game and configure it to use Proton-GE.
2. Use protontricks (I used the flatpak version) to install: a. d3dcompiler_42

xperia64

AMD's GPU drivers on Windows have some bad behavior when the card is not active or the primary display on boot. Specifically:

1. Certain EXE names are hooked in the kernel driver, and they won't even begin running for 10-15+ seconds after you open them
2. ULPS (Ultra Low Power State) is buggy when Windows is running with the driver loaded, but no displays are enabled on the GPU

Regarding 1:

• Applications named Steam.exe, Origin.exe, or uPlay.exe among others get hooked by the kernel driver, presumably for some sort of game integration that I don't quite understand
• I get the feeling this is potentially very outdated cruft, given that uPlay.exe is hooked (which no longer exists), while UbisoftConnect.exe is not
• When your AMD card doesn't own the Windows primary display, this hooking delays launch of EXEs with these names for whatever reason
• I have not found a complete list of these EXEs in the kernel driver binary; I'm thinking they may be hashed? There's another list in the binary in

xperia64

#!/bin/bash
# Largely adapted from https://www.reddit.com/r/SteamDeck/comments/xgslv9/howto_installing_pacman_packages_in_userspace/

if [ -z "$1" ] || [ -z "$2" ]; then
    echo "Usage: $0 <chrootdir> <command>"
    echo ""
    echo "Possible commands:"
    echo "  init           - initialize an empty directory as a chroot"
    echo "  pacman [args]  - use the host pacman to manage packages within the chroot"
    echo "  chroot         - calls arch-chroot on the chroot"