zyli
-
Posts
77 -
Joined
-
Last visited
-
Days Won
2
Posts posted by zyli
-
-
Today's build (2025-03-23) – 28, nightly build, ver. 186, f3948fb9db.
Map: Elephantine, 1 + 3.
The files 'interestinglog.html' and 'mainlog.html' reached a size of 6.0 GiB (each 6!).
I have never had such large files (so many errors).QuoteEngine exited successfully on 2025-03-23 at 21:19:09 with 1227 message(s), 13740 error(s) and 47247927 warning(s)
Since the error (Petra) occurred, the game slowed down significantly (to about 3 fps) and it stayed that way until the very end.
Best regards.
-
Quote
- you should make a deb file
It is already in Debian Sid:
https://tracker.debian.org/pkg/0ad
https://incoming.debian.org/debian-buildd/pool/main/0/0ad/
https://incoming.debian.org/debian-buildd/pool/main/0/0ad-data/
In Debian Bokworm will not be available:
Quote0ad (0.27.0-2) unstable; urgency=medium
* Tighten build-dep on cargo/rustc >= 1.66.0, required for building mozjs.
Unfortunately this makes it difficult to backport to stable.If you want to have 0ad 0.27.0 in Debian Bookworm, you have to compile it yourself using 'rustup' - tested - it works:
Regards
-
I understand that:
0ad-0.27.0-rc3 = L"release-a27, 8c69bb026d"
Because in the archive '0ad-0.27.0-rc3-unix-build.tar.xz' I found the above number in the file:
'/0ad-0.27.0/build/build_version/build_version.txt'
And also the latest file:
'/0ad-0.27.0/source/renderer/backend/gl/Device.cpp'
-
Debian Trixie + Nvidia + proprietary drivers
nightly-build - Revision 143 U source/renderer/backend/gl/Device.cpp grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt "build_version": "release-a27, 8c69bb026d", "build_version": "2.30.11", "build_version": 20100,I see that OpenGL ARB has been fixed.
It works fine for me.Regards.
PS.
Debian Trixie Live + 'nouveau' driver
Also works correctly, i.e.:
OpenGl ARB
and
Open GL +GPU Skinning-
1
-
-
After compiling on Debian Trixie + proprietary NVidia driver in case of 'OpenGL ARB' it is the same.
There is probably no need to run Trixie Live with 'nouveau'?grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt "build_version": "release-a27, 8f8d08b9f3", "build_version": "2.30.11", "build_version": 20100, -
Debian Trixie Live + driver 'nouveau' + 0.27.0-RC2 + OpenGL ARB
PS.
After pressing the 'Suppress' key twice, the game starts in a window.'Alt+ Enter' switches to full screen.
After selecting the game - 'Start game' - the game loads and suddenly - 0ad disappears.
-
After unchecking (disabling) 'GPU skinning' the strange shadows disappeared.
-
I don't have the above compilation on Debian 12.9 anymore - because it was on Live.
But I can recreate "strange longitudinal shadows" from the compilation performed on Debian Testing.
In my opinion, the cause of this is the duo: "nouveau driver + OpenGL".
How can I recreate it?
You need a PC with an NVidia card - I have a GTX1660Ti.
1. Run Debian Testing Live on it.
2. Connect the disk with the 0.27.0-RC2 compilation on Debian Testing.
3. Install missing packages:
apt install libboost-filesystem1.83.0 libenet7 libfmt10 libgloox18 libminiupnpc184. Go to the game directory:' /binaries/system'
5. Check and run:./test ./pyrogenesis
6. Check if it is as advanced graphics, renderer backend: "OpenGL"
7. Play.In my case I have:
cat /run/live/medium/.disk/info Auto-generated Debian GNU/Linux Live testing xfce 2025-01-20T02:15:25Z cat /etc/debian_version trixie/sid $inxi -G Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] driver: nouveau v: kernel Display: x11 server: X.Org v: 21.1.15 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau resolution: 1920x1080~60Hz API: EGL v: 1.5 drivers: nouveau,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.2.8-1 renderer: NV168 API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings x11: xdriinfo, xdpyinfo, xprop, xrandr cat /build/build_version/build_version.txt L"release-a27, 73b2eed323"Screenshots and logs attached.
Best regards.
PS.
Playing using the 'nouveau' driver is quite cumbersome and that's why every player will install proprietary Nvidia drivers, where this problem does not occur.I think the above shadows are a kind of curiosity rather than a bigger bug.
-
@Meister, @Nadporost – thanks for pointing me to 'rustup'.
https://www.rust-lang.org/tools/install
Thanks to this I managed to compile 0ad 0.27.0-RC2 on Debian 12.9.
This is not in line with Debian's ironclad rules, but what wouldn't you do for a few moments of pleasure?As usual I did it on "Live".
cat /run/live/medium/.disk/info Official Debian GNU/Linux Live 12.9.0 xfce 2025-01-11T10:25:55Z cat /etc/debian_version 12.9 apt policy rustc cargo rustc: Installed: (none) Candidate: 1.63.0+dfsg1-2 Version table: 1.63.0+dfsg1-2 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages cargo: Installed: (none) Candidate: 0.66.0+ds1-1 Version table: 0.66.0+ds1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 PackagesSince I will be using "rustup" I will not install 'rustc' and 'cargo' from the Debian repository!
If the Debian 'rustc' and 'cargo' were on the system I think they should be uninstalled first.Now the commands.
First 'rustup'.mkdir rust cd rust curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shI confirm 'standard installation' – Enter.
I receive, among other things, the following information:QuoteRust is installed now. Great!
To get started you may need to restart your current shell.
This is usually done by running one of the following (note the leading DOT):
. "$HOME/.cargo/env"I exit the terminal: exit.
I open the terminal again and type:
. "$HOME/.cargo/env" rustc --version rustc 1.84.0 (9fc6b4312 2025-01-07) cargo --version cargo 1.84.0 (66221abde 2024-11-19)I'm checking if I have the required dependencies.
Note!
I've crossed out 'cargo' and 'rustc', I've also removed 'subversion'.
I've added: 'llvm'.dpkg -l build-essential cmake libboost-dev libboost-system-dev libboost-filesystem-dev libcurl4-gnutls-dev libenet-dev libfmt-dev libfreetype-dev m4 libgloox-dev libicu-dev libminiupnpc-dev libnvtt-dev libogg-dev libopenal-dev libpng-dev libsdl2-dev libsodium-dev libvorbis-dev libwxgtk3.2-dev libxml2-dev llvm python3 zlib1g-devIf something is missing – you have to install it.
Now compilation – commands in telegraphic short:
Download, verify, unpack:mkdir 0.27.0-rc2 cd 0.27.0-rc2/ wget https://releases.wildfiregames.com/rc/0ad-0.27.0-rc2-unix-build.tar.gz wget https://releases.wildfiregames.com/rc/0ad-0.27.0-rc2-unix-data.tar.gz wget https://releases.wildfiregames.com/rc/0ad-0.27.0-rc2-unix-build.tar.gz.sha1sum wget https://releases.wildfiregames.com/rc/0ad-0.27.0-rc2-unix-data.tar.gz.sha1sum sha1sum -c 0ad-0.27.0-rc2-unix-build.tar.gz.sha1sum sha1sum -c 0ad-0.27.0-rc2-unix-data.tar.gz.sha1sum tar xpf 0ad-0.27.0-rc2-unix-build.tar.gz tar xpf 0ad-0.27.0-rc2-unix-data.tar.gz cd 0ad-0.27.0I gave up on checking the minisign (https://trac.wildfiregames.com/wiki/VerifyingYourDownloads).
Instead of 'tar.gz' you can download smaller 'tar.xz' files.
Compilation commands:cd libraries/ ./build-source-libs.sh cd ../build/workspaces/ ./update-workspaces.sh cd gcc/ makeAfter './build-source-libs.sh' is finished, we should see: 'Your build was successful!'.
Then it's good.
We can add the '-j N' option to the above commands, where 'N' is the result of the 'nproc' command - the number of processor cores.
If for some reason we repeat the 'make' command, we first issue the 'make clean' command.Now the test
cd ../../../binaries/system/ ./testWe should see:
'Running cxxtest tests (417 tests)...OK!'And running:
./pyrogenesisAfter launch, version control:
grep build_version ~/.config/0ad/logs/userreport_hwdetect.txt "build_version": "release-a27, 73b2eed323", "build_version": "2.26.5", "build_version": 20100, cat ../../build/build_version/build_version.txt L"release-a27, 73b2eed323"On Debian Live, in the case of the NVidia card, we only have the 'nouveau' driver.
In the advanced graphics settings, we change the default 'OpenGL' to 'Vulkan', save, exit the game and start it again.
If we do not do this (we stay on OpenGL), we will see strange longitudinal "shadows".
In my case, the game did not start on the outdated 'OpenGL ARB' - I had to change 'rendererbackend' to vulkan in the '~/.config/0ad/config/user.cfg' file.Regards
-
1
-
-
@ Meister
You're getting irritated for nothing.
I suppose you didn't read this link very carefully:
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian
Then, maybe you would read my sentence as:
QuoteIf you broke your system, don't expect help regarding 0ad.
Back to the point.
I downloaded Bunsenlabs from:
https://www.bunsenlabs.org/installation.html
I launched it and what do I see?
root@debian:/home/user# cat /run/live/medium/.disk/info Debian GNU/Linux 12 "Boron" - Snapshot amd64 LIVE/INSTALL Binary 20240123-08:09 user@debian:~$ uname -a Linux debian 6.1.0-17-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64 GNU/Linux user@debian:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm user@debian:~$ cat /etc/debian_version 12.4 user@debian:~$ apt policy rustc rustc: Installed: (none) Candidate: 1.63.0+dfsg1-2 Version table: 1.63.0+dfsg1-2 500 500 https://deb.debian.org/debian bookworm/main amd64 Packages user@debian:~$ cat /etc/apt/sources.list deb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware #deb-src https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware deb https://deb.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware #deb-src https://deb.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware deb https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware #deb-src https://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware deb [trusted=yes] file:/run/live/medium bookworm main contrib non-free non-free-firmware user@debian:~$ cat /etc/apt/sources.list.d/bunsen.list deb https://pkg.bunsenlabs.org/debian boron mainWhere do you see 'rustc' in ver 1.84?
You probably installed ver. 1.84 by force from sid.Therefore you have Frankenstein Debian.
See link:
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian
And therefore ... etc.
By the way.
I know that the road to hell is paved with good advice (such a proverb),
but instead of installing some exotic distribution, wouldn't it be easier to install Debian with default OpenBox like in this Bunslabs?Best regards.
-
@Meister
First of all: what system do you have?
cat /etc/debian_version lsb_release -a apt policy rustcThere is no 'rustc' in Debian Bookworm in ver. 1.84:
https://packages.debian.org/search?searchon=names&keywords=rustc
Unless you have a so-called Frankestein Debian:
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian
Then, sorry, but don't expect help from anyone.
When compiling 0.27.0-rc2 under Debian Bookworm 12.9, as I wrote above, you will see:
0:02.40 checking rustc version... 1.63.0 0:02.42 checking cargo version... 1.65.0 0:02.45 ERROR: Rust compiler 1.63.0 is too old.Best regards
-
I checked if it is possible to compile 0ad-0.27.0-rc2 on Live Debian Bookworm 12.9.
Short answer: you can't, because 'rustc' is too old.
If someone wants to play 0ad-0.27.0-rc2, they have to upgrade Bookworm -> Trixie.
QuoteAdded on 2025-01-27
Unless...
You uninstall Debian's 'rustc' and 'cargo' and use 'rustup', then see:Details.
After installing dependencies (without 'subversion', but with 'llvm') and issuing the command './build-source-libs.sh' I found out that:
0:02.40 checking rustc version... 1.63.0 0:02.42 checking cargo version... 1.65.0 0:02.45 ERROR: Rust compiler 1.63.0 is too old. 0:02.45 To compile Rust language sources please install at least 0:02.45 version 1.66.0 of the 'rustc' toolchain (or, if using nightly, 0:02.45 at least one version newer than 1.66.0) and make sure it is 0:02.45 first in your path. 0:02.45 You can verify this by typing 'rustc --version'. 0:02.45 If you have the 'rustup' tool installed you can upgrade 0:02.45 to the latest release by typing 'rustup update'. The 0:02.45 installer is available from https://rustup.rs/ *** Fix above errors and then restart with "./mach build" ERROR: SpiderMonkey build failedThe system has:
$ apt policy rustc rustc: Installed: 1.63.0+dfsg1-2 Candidate: 1.63.0+dfsg1-2There is no newer version in backports.
If anyone wants to know how to compile 0ad, the README.md file contained in the 0ad-0.27.0-rc2-unix-build.tar.gz archive directs them to:
https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructionsIn my opinion, in the 'Linux Debian Ubuntu' subitem (https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructions#debian-ubuntu) you should;
1.
Remove: Debian 12 (bookworm)
Enter: Debian 13 (trixie)2.
In the 'sudo apt install' code
Remove: 'subversion'3.
In the 'sudo apt install' code
Add: 'llvm'Best regards.
-
I checked if the 0ad-0.27.0-rc2 build works correctly on Live Debian Trixie.
$ cat /run/live/medium/.disk/info Auto-generated Debian GNU/Linux Live testing xfce 2025-01-20T02:15:25ZIt compiled correctly, but two comments.
1.
The 'llvm' package is not specified in the dependencies.It is not on Live Trixie - you have to install it (# apt install llvm).
Otherwise we will see:
0:03.83 ERROR: Cannot find llvm-objdump *** Fix above errors and then restart with "./mach build" ERROR: SpiderMonkey build failed2.
In my opinion, the 'subversion' package is unnecessary for RC compilation.It is useful for svn compilation.
Best regards.
PS.
If I find time – I will try compiling on Live Debian 12.9 – but the 'rustc' version there is probably too low.The computer has an NVidia card, but Trixie uses the 'nouveau' driver and because of that, strange shadows appear in the game.
Of course, there will be no problems on the NVidia proprietary driver.PS. No. 2
After switching graphics to Vulkan and restarting the game, the strange shadows disappeared.
The game is playable - of course it is slower than on the Nvidia company drivers. -
I am attaching replay files from the directory '~/.local/share/0ad/replays/0.27.0/2025-01-18_0001'
-
Debian Trixie, 0.0.27 svn 173100c5c3.
Elephantine map, very large.
Everything seems fine to me, but in 'mainlog.html' I found:
"WARNING: PlayerID 2 | Petra: Raid 14 has an inaccessible target foundation|structures/gaul/dock indices 10 1".
Regards.-
1
-
-
https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructions#dependencies
Dependencies
Python 3 (required for cxxtest and non-system SpiderMonkey)
-
Yesterday, Debian Experimental made Python 3.13 the default version.
https://tracker.debian.org/pkg/python3-defaults
Quote[2024-12-25] Accepted python3-defaults 3.13.1-1~exp2 (source) into experimental (Stefano Rivera)
[2024-12-25] Accepted python3-defaults 3.13.1-1~exp1 (source) into experimental (Stefano Rivera)Since Python 3.12 was a problem when compiling 0ad, I decided to check how 0ad handles version 3.13.
Debian Trixie with Python 3.13 installed from the Experimental branch as default.
$ python3 --version Python 3.13.1Compilation (svn update, cd libraries/, ./build-source-libs.sh and so on) went fine.
The game starts without problems.I updated ver. 109 (L"main, dba968") to ver. 117 (L"release-a27, b08cf")
Christmas greetings.
-
2
-
-
Thank you for your answer.
Here's what I did:
1.
I installed Debian Trixie on a USB flash drive (USB 3.0) just like on a hard drive (with its own UEFI partition and additionally with grub-pc so that it can be run on older computers without UEFI).
Now I have: rustc ver. 1.83.0, python 3.12.6, libopenal* ver. 1.24.1.2.
I copied my previous directory from 0ad nightly 'svn_2024/0ad/trunk/' to the above-mentioned Debian Trixie drive.
I made sure that the directories I placed in had exactly the same names.
Once I unnecessarily changed the name 'svn_2024' to something else and 0ad wouldn't build - the absolute path was remembered somewhere.3.
I issued the commands:cd trunk/ svn update cd libraries/ nproc # I got: 20 ./build-source-libs.sh -j20 cd ../build/workspaces/ ./update-workspaces.sh -j20 cd gcc make clean make -j204.
Now check:cd ../../../binaries/system/ ./test # I got: Running cxxtest tests (416 tests)...OK! ./pyrogenesis # It works fine! cat ~/svn_2024_october/0ad/trunk/build/build_version/build_version.txt L"main, 5f1f8" (yesterday, today 17 Dec: L"main, dba968")5.
Of course, there were some surprises.
I struggled with, among others: with the problem:QuoteERROR: Cannot find llvm-objdump
ERROR: SpiderMonkey build failedIt helped to install the package: llvm.
6.
I think that on the page: https://gitea.wildfiregames.com/0ad/0ad/wiki/BuildInstructions
in the "Dependencies - Debian, Ubuntu" section for Debian 13 Trixie in the sentence starting with:
"sudo apt install"it would be good to add the following packages:
python-is-python3
rustfmt
llvmAdding the 'ccache' package wouldn't hurt either.
7.
When I executed './clean-source-libs.sh' it gave me a warning: './clean-source-libs.sh: 13: git: not found'.But I think that for 'svn update' the 'git' package is not needed.
8.
After starting './pyrogenesis' it displays:[W][01203.830396] pw.conf | [ conf.c: 1214 try_load_conf()] can't load config client.conf: No such file or directory
[E][01203.830423] pw.conf | [ conf.c: 1243 pw_conf_load_conf_for_context()] can't load config client.conf: No such file or directoryBut it probably has no visible effect.
9.
You can't download the 0ad-spirv mod using Settings – Mod selection, which was once needed for Vulkan to work.So I copied the '0ad-spirv-0.27.22-b8sl.zip' file I had, enabled it in the settings and everything works.
0ad + Vulkan on the 'nouveau' driver (sic!).
The game is playable, but Debian files and game files on a pendrive instead of a hard drive do their thing.
I noticed that when there is no '0ad-spirv' mod, after exiting the game a warning window appears - I'm attaching the 'crash' file.
That would be it - maybe someone will find it useful.Best regards.
-
Debian 12.8 Bookworm
Today (2024-12-16) I tried to compile 0ad with nightly-build (commands: 'svn update' etc.)I got the message:
QuoteUpdated to version 108.
In the '0ad/trunk/libraries/' directory I had to give executable permissions to *.sh files, because the update downloaded newer files without these permissions:
chmod +x build-source-libs.sh source/cxxtest-4.4/build.sh source/fcollada/build.sh source/nvtt/build.sh source/premake-core/build.sh source/spidermonkey/build.sh source/spirv-reflect/build.sh
But that's a minor thing.
Being in the 'libraries/' directory I issued the command './build-source-libs.sh'
During "Building SpiderMonkey..." I received the information:
QuoteERROR: Rust compiler 1.63.0 is too old.
And then:
QuoteTo compile Rust language sources please install at least version 1.66.0 of the 'rustc' toolchain (or, if using nightly, at least one version newer than 1.66.0) and make sure it is first in your path.
Finally:
QuoteERROR: SpiderMonkey build failed
In stable Debian 12.8 there is:
rustc --version rustc 1.63.0Can't the requirements be lowered to version 1.63, which would allow building a 0ad nightly build in Debian Bookworm?
I know that Debian has been waiting for quite a long time to update rustc.
Debian Testing already has the current version 1.83, but the new Debian Stable is still a long way off (half a year?).
The previous 0ad build, i.e. 99, made by me, worked fine.Regards.
-
https://tracker.debian.org/pkg/0ad
[2024-11-28] Accepted 0ad 0.0.26-8 (source) into unstable (Vincent Cheng)
Changelog:
0ad (0.0.26-8) unstable; urgency=medium
[ Antoine Le Gonidec ]
* Honour DEB_BUILD_OPTIONS when setting the maximum number of jobs.
(Closes: #1000235)
* Avoid a crash on launch with openal 1.24.0 (Closes: #1087990)[ Vincent Cheng ]
* Fix FTBFS when attempting to build twice in a row. (Closes: #1043705)
* Update Standards version to 4.7.0, no changes needed.-- Vincent Cheng <vcheng@debian.org> Thu, 28 Nov 2024 14:26:39 -0800
-
@bigsmit19
You're not the only one with this problem.In my opinion, it follows that there are two types of players:
1. Let's call them 'builders' - they plan, build, develop the economy and at the same time develop the army,
2. Let's call them 'rowdy' - at the beginning they focus on producing soldiers and at all costs send them immediately to the opponent.The first one has no chance against the second one (and this is how Petra plays) - unless there is some obstacle, e.g. the sea.
That's why I suggest you try your hand at naval maps (random).
For example, the Migration map, a very large map, four players (human + 3 computer players).
There are four islands (each for one player) and a continent.
In order for the computer player to attack you, he must first develop the economy - just like you, because he must build warships.
Even if he attacks you later, you will defeat him, because you will already be at a certain level of development.
I suggest playing as Carthaginians and sending a crew to the continent as soon as possible in a merchant ship to set up a base somewhere in the interior, because the resources on the island will soon run out.It is best if you play on the outermost island - you land in the corner of the map, build a port and a trade route, etc.
Once you get the hang of it, you will win every time on the most difficult level.
A more interesting (but also more difficult) map is Elephantine (very large, four players).
Because on the central island (Elephantine) you can take over a wonder defended by Gaia warriors.
As soon as you start building your own wonder, send heavy cavalry (approx. 80) to the central island to take over the Gaia wonder.
When you have two wonders, no one will threaten you.
First, you have to defend yourself against one opponent from the same coast or form an alliance with him (neutrality).
And taking a third wonder from an opponent is a real joy.Good luck.
-
So where did 'neofetch' get this data: "Kernel: 6.5.0-5-amd64"?
The current kernel in Trixie is: 6.11.5
https://packages.debian.org/trixie/linux-image-amd64In my opinion, in the file '/etc/apt/sources.list':
1.
The last two lines ('proposed-updates' and 'bookworm-backports') are unnecessary.
2.
Instead of 'ftp.it.debian.org/debian' I would use: 'http://deb.debian.org/debian/'.
3.
Instead of 'ftp.it.debian.org/debian/ trixie-security' I would use: 'deb http://security.debian.org/debian-security/ trixie-security'Best regards.
-
1
-
-
Sorry, but...
Debian Trixie with kernel 6.5.0-5 was in December 2023.
Are other packages that old too?
Best regards
-
Nothing disappears without a reason.
At that time '0ad' did not compile with python 3.12.
Therefore, the solution was to take '0ad' from 'mantic'.
But time passes and now there is no 'mantic' repository, because 'plucky' was released.
'0ad' is already present in 'plucky'.
https://packages.ubuntu.com/plucky/0ad
Compare the required dependencies, in particular: 'libboost-filesystem1.83.0' and 'libicu74'.
In 'noble' they are probably appropriate.
Then download the '0ad' package ( http://cz.archive.ubuntu.com/ubuntu/pool/universe/0/0ad/0ad_0.0.26-6ubuntu1_amd64.deb ) and install manually (dpkg -i file.deb).Installing with flatpak is not recommended:
https://wildfiregames.com/forum/topic/100249-alpha-26-doesnt-start-ubuntu-2204/?do=findComment&comment=585183Best regards.
Game 0 A.D. keep stuttering on Linux Debian
in Help & Feedback
Posted · Edited by zyli
1.
Zram?
In my opinion, this invention should be gotten rid of.
It may be the cause of delays.
The Linux kernel has everything it needs.
Now, memories are fast - why waste time on additional compression and decompression?
This whole zram is an illusion - if someone has too little RAM, it is better to add physical memory.
If anything - 'tmpfs' is more necessary.
2.
Compiling 0ad is not difficult.
I recommend compiling ver. 0.27.1 rc: https://releases.wildfiregames.com/rc/
But on Debian Bookworm (12.11) you will not compile this version, because the requirements for 'rust' have been raised (Bookworm has ver. 1.63, and a minimum of 1.66 is required).
There is a way to do this: https://wildfiregames.com/forum/topic/127464-debian-bookworm-129-rustup-successful-compilation-of-0270-rc2/#comment-592272
If you are afraid that the compilation will clutter your system with various unnecessary packages, you can always compile on Debian Live https://cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/
You have to remember that directories on Live are created in RAM, and compiling 0ad requires a lot of space, so you have to attach external memory and create a compilation directory on it.
But be careful - this memory must have a Linux file system (e.g. ext4), because fat32, exfat do not support symlinks and compilation will fail.
After compilation is complete, we move the 'binaries' directory with the 'data' and 'system' subdirectories to the target location.
The remaining compilation directories are unnecessary.
Best regards