-
Posts
505 -
Joined
-
Days Won
9
Posts posted by andy5995
-
-
On 14/01/2023 at 12:59 AM, hyperion said:
--with-system-mozjs is currently broken, already reported.
Try again in a day or two, also you will need sm-91.13
@hyperionsm? What library is that and where are the sources? I can't find it available in Manjaro or the AUR.
-
10 minutes ago, vladislavbelov said:
Maybe it's unavailable from AppImage? Is it possible to run vulkaninfo from AppImage envrionment?
On both systems I was running 0ad from an AppImage. On the desktop it worked.
@Jammyjamjammanhad a similar problem. His graphics card has an AMD chipset. He was able to use Vulkan with the Refresh2025 program I mentioned. But it didn't work with the 0ad AppImage. He may report here later himself with his details.
-
7 hours ago, fabio said:
Do you have installed mesa-vulkan-drivers package?
I don't see that package is available for Manjaro. I have vulkan-intel installed on my Laptop, nvidia-dkms on my desktop.
@vladislavbelovI was on my laptop when I gave you those logs yesterday. On my desktop, Vulkan with the 0ad AppImage worked.
Laptop:
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller])
Desktop:
01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) (prog-if 00 [VGA controller])
The distro on both systems is Manjaro. I didn't have to install anything extra yet.
Same output on both systems when I run:
Quote$ vulkaninfo | grep VK_KHR_surface
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1I ran Refresh 2025_Linux (Binary will attempt to run in Vulkan), on my Laptop and it worked (images attached)
Quote../mesa-22.3.1/src/intel/isl/isl.c:2235: FINISHME: ../mesa-22.3.1/src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available.
For the config, I set the res to 1920x1080 and quality to Ultra.
-
I rebuilt after adding 'LOGWARNING("%s", SDL_GetError());' and this was the new message in the console:
WARNING: Installed Vulkan doesn't implement the VK_KHR_surface extension
That was built in Ubuntu bionic with the available libvulkan-dev package from the bionic repo.
-
I got this from running the AppImage I made. More detailed logs attached.
QuoteFILES| Main log written to '/home/andya/.config/0ad/logs/mainlog.html'
FILES| Interesting log written to '/home/andya/.config/0ad/logs/interestinglog.html'
TIMER| CONFIG_Init: 3.40999 ms
Sound: AlcInit success, using OpenAL Soft
ERROR: Unable to create device for Vulkan backend, switching to GL.
FILES| UserReport written to '/home/andya/.config/0ad/logs/userreport_hwdetect.txt' -
17 minutes ago, hyperion said:
Edit: you might want to raise a concern: https://code.wildfiregames.com/rP27329
Done.
-
6 minutes ago, hyperion said:
version 4.0.0 is to old, guess some commit to 0ad increased the minimum requirement.
Thanks. I checked and saw that core.h wasn't even included in the 4.0.0 upstream version of fmtlib.
-
11 minutes ago, andy5995 said:
Chatting with @Stan`helped me figure out the problem
core.h isn't in the bionic libfmt-dev package (though it must have been at some point because I'm using the same build environment as I was using for the a26 appimage)
I filed a bug report
-
On 14/01/2023 at 11:44 AM, andy5995 said:
On Ubuntu bionic, the build fails. These are the packages I'm installing
https://github.com/0ad-matters/0ad-appimage/blob/trunk/Dockerfile
Chatting with @Stan`helped me figure out the problem
core.h isn't in the bionic libfmt-dev package (though it must have been at some point because I'm using the same build environment as I was using for the a26 appimage)
https://packages.ubuntu.com/bionic/amd64/libfmt-dev/filelist
It's in the corresponding Debian buster package though
https://packages.debian.org/buster/amd64/libfmt-dev/filelist
-
On Ubuntu bionic, the build fails. These are the packages I'm installing
https://github.com/0ad-matters/0ad-appimage/blob/trunk/Dockerfile
QuotePostprocManager.cpp
In file included from ../../../source/renderer/InstancingModelRenderer.cpp:28:
../../../source/ps/containers/StaticVector.h:24:10: fatal error: fmt/core.h: No such file or directory
#include <fmt/core.h>
^~~~~~~~~~~~
compilation terminated.
In file included from ../../../source/renderer/HWLightingModelRenderer.cpp:30:
../../../source/ps/containers/StaticVector.h:24:10: fatal error: fmt/core.h: No such file or directory
#include <fmt/core.h>
^~~~~~~~~~~~
compilation terminated.
graphics.make:438: recipe for target 'obj/graphics_Release/HWLightingModelRenderer.o' failed
make[1]: *** [obj/graphics_Release/HWLightingModelRenderer.o] Error 1
make[1]: *** Waiting for unfinished jobs....
graphics.make:441: recipe for target 'obj/graphics_Release/InstancingModelRenderer.o' failed
make[1]: *** [obj/graphics_Release/InstancingModelRenderer.o] Error 1
Makefile:126: recipe for target 'graphics' failed
make: *** [graphics] Error 2 -
I'll see if I can get an AppImage for a dev build available within a few days. https://github.com/0ad-matters/0ad-appimage/pull/18
-
This is the first time I tried compiling with system mozjs. On Manjaro LInux, I've installed the js78 package.
js78 --version
reports 78.15.0
In the 0ad workspaces directory, I ran
./update-workspaces.sh --with-system-mozjs -j5
It completed:
Quote...
Generated ../workspaces/gcc/ActorEditor.make...
Generated ../workspaces/gcc/Collada.make...
Generated ../workspaces/gcc/cxxtestroot.make...
Generated ../workspaces/gcc/test.make...
Done (1636ms).But when I ran
make -C gcc -j5
I got a failure very quickly:
Quotemake: Entering directory '/home/andy/src/0ad-svn/build/workspaces/gcc'
==== Building mocks_real (release) ====
Creating obj/mocks_real_Release
mocks_real.cpp
Linking mocks_real
==== Building network (release) ====
Creating obj/network_Release
precompiled.h
In file included from ../../../source/network/NetMessages.h:27,
from ../../../source/network/NetMessage.h:26,
from ../../../source/pch/network/precompiled.h:26:
../../../source/scriptinterface/ScriptTypes.h:77:2: error: #error Your compiler is trying to use an incorrect major version of the SpiderMonkey library. The only version that works is the one in the libraries/spidermonkey/ directory, and it will not work with a typical system-installed version. Make sure you have got all the right files and include paths.
77 | #error Your compiler is trying to use an incorrect major version of the \
| ^~~~~
../../../source/scriptinterface/ScriptTypes.h:85:2: error: #error Your compiler is trying to use an untested minor version of the SpiderMonkey library. If you are a package maintainer, please make sure to check very carefully that this version does not change the behaviour of the code executed by SpiderMonkey. Different parts of the game (e.g. the multiplayer mode) rely on deterministic behaviour of the JavaScript engine. A simple way for testing this would be playing a network game with one player using the old version and one player using the new version. Another way for testing is running replays and comparing the final hash (check trac.wildfiregames.com/wiki/Debugging#Replaymode). For more information check this link: trac.wildfiregames.com/wiki/Debugging#Outofsync
85 | #error Your compiler is trying to use an untested minor version of the \
| ^~~~~
make[1]: *** [network.make:138: obj/network_Release/precompiled.h.gch] Error 1
make: *** [Makefile:79: network] Error 2
make: Leaving directory '/home/andy/src/0ad-svn/build/workspaces/gcc' -
Could someone please confirm this bug so it doesn't get incorrectly closed again:
-
3 hours ago, andy5995 said:
Actually I just tried reproducing this again but I am not able to. @Freagarachhow about you?
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=22.0.0Using 0ad-0.0.26-alpha-2210110407-x86_64.AppImage
Also tried with an a26 self-build, which actually links to the SDL2 library installed on Manjaro. I still can't reproduce the issues mentioned above.
-
Actually I just tried reproducing this again but I am not able to. @Freagarachhow about you?
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=22.0.0Using 0ad-0.0.26-alpha-2210110407-x86_64.AppImage
-
-
13 hours ago, Ceres said:
Could you please elaborate a bit more about what this means and how one could use it/ contribute? Thank you!
@CeresThe README is at https://github.com/0ad-matters/gh-action-build-pyromod and a thread here with extra info
- 2
- 1
-
@norjayFor that test, I setup 3 AI vs 3 AI and then set the game speed to 20x. In other tests, yes, sometimes I make all the AI players opponents.
-
From my initial test, it seems kind of cluttered, with too many bottlenecks. Note in the mini-map, the AI doesn't even try to build (or they can't build) in a significant portion of the map. Though I definitely like the concept and general uniqueness of this map @norjay
-
On 23/11/2022 at 7:06 AM, Outis said:
I understand about historical battles but even for non-historical scenarios like Caribbean Island and Northern Islands? It would be good to have the freedom to chose by default rather than modifying the maps in Atlas.
@Outis Already done, as of v0.26.5
https://github.com/0ad-matters/community-maps-2/releases/tag/v0.26.5
Those 2 you mentioned are included in the "6" I mentioned in the release notes.
-
13 hours ago, Stan` said:
That's interesting, it looks okay, but a bit inferior to the current actors we have for waterfalls.
I agree that it's inferior, but it hasn't been tweaked yet. The samples are just from an initial experiment. I don't really know how much it can be improved.
Also.. I didn't know there were already existing waterfall actors... that's good to know!
- 1
-
I've added this to the Community Maps mod and it will be included with v0.26.5. Thanks @Yavin
- 1
-
On 09/11/2022 at 7:09 PM, wowgetoffyourcellphone said:
We just have to make an executive decision and choose a number of levels. I think lowlands/midlands/highlands is more than enough abstraction levels.
I agree that three levels should be perfectly adequate.
Seems like once the other details are worked out, this should be implemented on 2 or 3 maps before the next release, then changed as the feedback comes pouring in or bugs are discovered.
Gotta figure out the heights yet for each of those levels though.
- 1
-
Errors when Compiling with system mozjs on Manjaro 22
in Bug reports
Posted
Ok. I had js91 installed. I tried recompiling but got the same errors @Stan`mentioned above.