Scratchpad Games Forums - General Raspberry Pi Content

New Setup

Tue, 21 Jul 2026 16:13:21 +0100

I have had a lot of issues with some updates recently but I've managed to resolve most of them..

If you are using your Pi for the 1st time remember you need to run the setup script at least one time. It will install all the libs needed throughout the book. It will be attached to all Pi projects but here is the most updated version.

Code:
#!/usr/bin/env bash

#

# Dev environment setup � safe to re-run.

# Re-running updates the git repos to their latest version and refreshes apt packages.

# --- helper: clone a repo if it's missing, otherwise update it to the latest version ---

clone_or_update() {

    url="$1"

    dir="$2"

    if [ -d "$dir/.git" ]; then

        echo "Updating $dir (pulling latest)"

        git -C "$dir" pull --ff-only

    else

        echo "Cloning $dir"

        git clone "$url" "$dir"

    fi

}

echo installing

echo installing cmake

cd "$HOME"

sudo apt update                 # refresh the package index so re-runs get the latest apt versions

sudo apt install cmake -y

echo

# stb

echo installing STB

clone_or_update https://github.com/nothings/stb.git "$HOME/stb"

echo STB install done

# GLM

echo installing GLM

clone_or_update https://github.com/g-truc/glm.git "$HOME/glm"

echo GLM Install done

echo "Installing Jeremiah Audio"

clone_or_update https://github.com/3dgep/Audio.git "$HOME/Audio"

cd "$HOME/Audio"

rm -rf build                    # start clean so Debug AND Release rebuild correctly every run

mkdir -p build

cd build

# ---- Debug ----

cmake -DCMAKE_BUILD_TYPE=Debug ../

cmake --build .

mkdir -p ../lib/Debug

mv ../lib/*.a ../lib/Debug/

echo "debug audio files added"

# ---- Release ----

cmake -DCMAKE_BUILD_TYPE=Release ../

cmake --build .

mkdir -p ../lib/Release

mv ../lib/*.a ../lib/Release/

echo "release audio files added"

cd "$HOME"

# Bullet installation:

sudo apt install libbullet-dev -y

echo Bullet installed.

# XrandR

echo installing XrandR for Resolution changes

sudo apt install libxrandr-dev -y

echo Xrandr installed

echo installing libopenAL and sound libs, these are largely replaced now, but kept for compatibility

sudo apt install libopenal-dev -y

sudo apt install pulseaudio -y

sudo apt install libalut-dev -y

sudo apt install libogg-dev -y

sudo apt install libvorbis-dev -y

sudo apt install vorbis-tools -y

echo we have installed OpenAL and companion audio 

echo get latest mesa libs

sudo apt install libgles2-mesa-dev -y

echo libmesa is Done

# Install FreeType

echo Installing freetype...

sudo apt install libfreetype6 libfreetype6-dev -y

echo FreeType installed

echo installing Assimp

cd "$HOME"

sudo apt install libassimp-dev -y

echo Assimp installed

echo installing VLC

sudo apt install libvlc-dev -y

echo VLC Installed

echo enhancing GPU debug output NOTE- not all will install

sudo apt install libglx-mesa0-dbgsym libglapi-mesa-dbgsym libgl1-mesa-dri-dbgsym -y

echo Done!

echo

echo Scroll up to make sure there were no errors, warnings are ok

echo Take note of the errors and check the web/support sites for fixes

read -s -p "Press Enter when you're ready!"

echo ...

setup.zip (Size: 1.26 KB / Downloads: 0)

My PC won't connect to my Pi using a network cable

Tue, 30 Dec 2025 16:39:20 +0000

As I am resetting a lot of my equipment, this old issue cropped up again for me. It happens every so often for some, not all, of my students too.
It's basically due to both your PC and Pi attempting to get an IP address from a DHCP server that doesn't exist in a direct connection, so neither can establish a proper network link.

There are 3 solutions to this:

1st If you can, buy a small network switch. When both machines are connected via a switch which has access to your network, they can find your network's DHCP server. This is my personally preferred method, especially when I have a few different machines I want to target - a switch avoids lots of messy unplugging/plugging.

2nd Connect both your PC and Pi via ethernet to your network router. That way both machines get IPs from your router's DHCP server.

3rd A little less elegant but effective: set both devices to static IPs on their own private network. This is fiddly because you need to type commands into the Pi's terminal, but it works well.
On the Pi, carefully enter these two commands:

sudo nmcli con add type ethernet ifname eth0 con-name wired-static ipv4.addresses 192.168.2.1/24 ipv4.method manual autoconnect yes
sudo nmcli con up wired-static

This assigns 192.168.2.1 to your Pi. Now set your PC's ethernet to a static IP in the same range:

Win + X → Network Connections
Right-click Ethernet → Properties
Double-click Internet Protocol Version 4 (TCP/IPv4) (< Select "Use the following IP address":

IP address: 192.168.2.2
Subnet mask: 255.255.255.0
Gateway: leave blank
DNS: leave blank

Click OK

Now your wired connection should work!
You can also enable WiFi on both devices for internet access - they'll route traffic appropriately.
While you can use raspberrypi.local (or whatever your Pi's hostname is) to connect, using the IP address 192.168.2.1 directly is faster and guarantees you're using the wired connection.

Hopefully you won't have a problem - it's only a small number of setups that have this issue, but this solution should fix it.

Actually there is a 4th option, just make sure both systems are on the same WiFi network.. WiFi these days is impressively fast, but... wired is quite significanly faster and you will feel that difference if you are doing a lot of debugging or sending data back and forward.

Current OS issues

Sat, 22 Nov 2025 20:36:30 +0000

Trixie on Pi

Trixie uses Wayland as default but it will emulate X11, as a result projects all seem to work fine, but may stretch window sizes from the standard 1024x768 to full screen.. Its not a major issue, you can still set X11 in the raspi-config tool via the terminal.