STEAMOS - updating DotNet from 8 to 10 for the update

[StarryNotes]

I hope this is the right category - I've tried to follow like six tutorials on installing Dotnet 10 via script and while it updated the DOTNET_ROOT, it didn't actually update which version my deck is using and I have no idea why - attached is the dotnet --info output.

I have already added the necessary lines to the bashrc and restarted my deck.

[isupor]

I'm having the same issue, did you ever find a solution? If not, the flatpack for VS works despite me not having dotnet10 for whatever reason.

[Diff]

26 minutes ago, isupor said:

I'm having the same issue, did you ever find a solution? If not, the flatpack for VS works despite me not having dotnet10 for whatever reason.

Flatpak's probably the easiest solution. It works because Flatpaks bundle everything they need inside (more or less).

[Dilan Rona]

I still got dotnet 8 as the default on my system, added dotnet 10 directly to the vintage story folder, and added an environment variable that points to the location

export DOTNET_ROOT=./dotnet # Manually set dotnet 10 variables
export PATH=$PATH:./dotnet

Then the scrip start vintage story just fine.

[Dark Thoughts]

20 hours ago, isupor said:

I'm having the same issue, did you ever find a solution? If not, the flatpack for VS works despite me not having dotnet10 for whatever reason.

Flatpaks are, for better or worse, sandboxed applications that inherently ship with all their necessary dependencies inside of the package.

[Teh Pizza Lady]

45 minutes ago, Dark Thoughts said:

Flatpaks are, for better or worse, sandboxed applications that inherently ship with all their necessary dependencies inside of the package.

this.

Minecraft used to ship with it's own copy of Java for the same reason... just in case you didn't have Java.

[MirthOfManus]

I have had some success downloading DOTNET 10 as the root user which then the rest of the system used. I can't remember exactly what I did for the environment variable but it ended up working. I am unfortunately not incredibly familiar with steamos version of Linux but I will update this reply if I can recreate what I did.

[Diff]

32 minutes ago, MirthOfManus said:

I have had some success downloading DOTNET 10 as the root user which then the rest of the system used. I can't remember exactly what I did for the environment variable but it ended up working. I am unfortunately not incredibly familiar with steamos version of Linux but I will update this reply if I can recreate what I did.

Did that solution survive OS updates?

[Dilan Rona]

Yes it did.

Its a local install in the vintage story folder itself. And as long as the environment variable is right, and pointing at the correct location, it will work.

Edited 15 hours ago by Dilan Rona

[Diff]

Then I'm confused, if it was installed locally to the folder why install as the root user?

[Dilan Rona]

Cause I'm still on fedora 40 on this laptop, and cant install dotnet 10 globally. Besides for what I need to do, dotnet 8 is actually fine globally.

[Diff]

Oh wait you're not MirthOfManus, my bad. MirthOfManus said they installed it globally as the root user on SteamOS, I was asking about that because SteamOS often wipes changes to the root partition on OS updates.

Edited 5 hours ago by Diff

[Dilan Rona]

Will still work on SteamOS with the local install. He has to make sure the environment variables are in place for the game to run.

#!/bin/bash

# Get the absolute directory path of where the script is located
SCRIPT_DIR="$(dirname "$(realpath "${BASH_SOURCE[0]}")")"

# Required for the game to load its own fonts (must be absolute path)
export FONTCONFIG_FILE="$SCRIPT_DIR"/fonts.conf

# Change directory to where the game executable should also be
cd "$SCRIPT_DIR"

# try to use the more powerful/dedicated GPU if available - set this if by default it uses your integrated graphics card
# export DRI_PRIME=1

# Manually set dotnet 10 variables
export DOTNET_ROOT=./dotnet
export PATH=$PATH:./dotnet

# Run the game, pass along all arguments given to the script
./Vintagestory "$@"

Thats my entire script for Vintage Story 1.22.7. And the way I got mine setup, I got 1.20.12, 1.21, and 1.22 installed. 1.20 being my megabuild map (that depends on dotnet 8 for the plugins).

[Dilan Rona]

On 9/10/2026 at 2:53 AM, Diff said:

Flatpak's probably the easiest solution. It works because Flatpaks bundle everything they need inside (more or less).

Not exactly a fan of flatpacks. Updates I do manually.

[Teh Pizza Lady]

2 hours ago, Dilan Rona said:

Not exactly a fan of flatpacks. Updates I do manually.

Why is that? Just curious. I always thought they were great because they just work!  I see them as self-contained venvs which are pretty much necessary for running Python applications since some of them might use different packages than others.