All Activity
- Past hour
-
GTA 6 Story joined the community
- Today
-
Atlas-Tools, a package combining Mercator and post-Atlas
Asher replied to Grautvornix's topic in Scenario Design/Map making
Just looked it up, and it looks like if you add -y to the pyinstaller command, it will automatically replace the files in the output folder -
@lilypoppy We will be getting there! Did you run it with the old spec files (delivered with the 0.25.0 package) or with the new ones? Anyway here is a complete update. Please replace the existing scripts in your atlas-tools root folder (where Mercator.py resides) with the attached ones (build.sh script plus the two spec files). Your logs showed also another issue: there are warnings that libxcb-cursor.so.0 is missing. Qt 6 does not open a window on an X11 desktop without it, so the built programs would not have started. So I'd suggest before runing the script you can try this: sudo apt install libxcb-cursor0 Hope it works now! Best regards, Grautvornix Post-Atlas.spec build.sh Mercator.spec
-
@Asher I deleted build folder and install sudo apt install python3-venv binutils libpython3.12 atlas-tools build script build script version 1.4.0 =============================================== Collecting libs... Requirement already satisfied: pip in ./.build-venv/lib/python3.12/site-packages (26.3) Requirement already satisfied: pyinstaller in ./.build-venv/lib/python3.12/site-packages (6.22.3) Requirement already satisfied: pyqt6 in ./.build-venv/lib/python3.12/site-packages (6.12.1) Requirement already satisfied: scipy in ./.build-venv/lib/python3.12/site-packages (1.18.1) Requirement already satisfied: Pillow in ./.build-venv/lib/python3.12/site-packages (13.0.0) Requirement already satisfied: pyqtgraph in ./.build-venv/lib/python3.12/site-packages (0.14.0) Requirement already satisfied: PyOpenGL in ./.build-venv/lib/python3.12/site-packages (3.1.10) Requirement already satisfied: altgraph in ./.build-venv/lib/python3.12/site-packages (from pyinstaller) (0.17.5) Requirement already satisfied: packaging>=22.0 in ./.build-venv/lib/python3.12/site-packages (from pyinstaller) (26.3) Requirement already satisfied: pyinstaller-hooks-contrib>=2026.7 in ./.build-venv/lib/python3.12/site-packages (from pyinstaller) (2026.10) Requirement already satisfied: setuptools>=42.0.0 in ./.build-venv/lib/python3.12/site-packages (from pyinstaller) (84.2.1) Requirement already satisfied: PyQt6-sip<14,>=13.13 in ./.build-venv/lib/python3.12/site-packages (from pyqt6) (13.13.1) Requirement already satisfied: PyQt6-Qt6<6.13.0,>=6.12.0 in ./.build-venv/lib/python3.12/site-packages (from pyqt6) (6.12.0) Requirement already satisfied: numpy<2.8,>=2.0.0 in ./.build-venv/lib/python3.12/site-packages (from scipy) (2.5.5) Requirement already satisfied: colorama in ./.build-venv/lib/python3.12/site-packages (from pyqtgraph) (0.4.6) =============================================== Building Mercator... 69 INFO: PyInstaller: 6.22.3, contrib hooks: 2026.10 69 INFO: Python: 3.12.3 71 INFO: Platform: Linux-7.0.0-43-generic-x86_64-with-glibc2.39 71 INFO: Python environment: /home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv 75 INFO: Module search paths (PYTHONPATH): ['/home/felix/Téléchargements/atlas-tools-0.25.0', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages', '/home/felix/Téléchargements/atlas-tools-0.25.0'] 422 INFO: Appending 'datas' from .spec 424 INFO: checking Analysis 424 INFO: Building Analysis because Analysis-00.toc is non existent 424 INFO: Looking for Python shared library... 440 WARNING: Unrecognised line of output 'Cache généré par : ldconfig (Ubuntu GLIBC 2.39-0ubuntu8.12) stable release version 2.39' from ldconfig 441 INFO: Using Python shared library: /lib/x86_64-linux-gnu/libpython3.12.so.1.0 441 INFO: Running Analysis Analysis-00.toc 441 INFO: Target bytecode optimization level: 0 441 INFO: Initializing module dependency graph... 441 INFO: Initializing module graph hook caches... 455 INFO: Analyzing modules for base_library.zip ... 1360 INFO: Processing standard module hook 'hook-heapq.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 1478 INFO: Processing standard module hook 'hook-encodings.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 3110 INFO: Processing standard module hook 'hook-math.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 3396 INFO: Processing standard module hook 'hook-pickle.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 5373 INFO: Caching module dependency graph... 5428 INFO: Analyzing /home/felix/Téléchargements/atlas-tools-0.25.0/Mercator.py 6442 INFO: Processing standard module hook 'hook-PyQt6.QtWidgets.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 6585 INFO: Processing standard module hook 'hook-PyQt6.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 7236 INFO: Processing standard module hook 'hook-PyQt6.QtCore.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 8074 INFO: Processing standard module hook 'hook-PyQt6.QtGui.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 8853 INFO: Processing standard module hook 'hook-_ctypes.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 9071 INFO: Processing standard module hook 'hook-xml.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 9098 INFO: Processing standard module hook 'hook-xml.etree.cElementTree.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 9408 INFO: Processing standard module hook 'hook-PyQt6.QtNetwork.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 9654 INFO: Processing standard module hook 'hook-PIL.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 9787 INFO: Processing standard module hook 'hook-PIL.Image.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 10049 INFO: Processing standard module hook 'hook-numpy.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 10416 INFO: Processing pre-safe-import-module hook 'hook-typing_extensions.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/pre_safe_import_module' 10417 INFO: SetuptoolsInfo: initializing cached setuptools info... 11198 INFO: Processing standard module hook 'hook-platform.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 11396 INFO: Processing standard module hook 'hook-sysconfig.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 11614 INFO: Processing standard module hook 'hook-webbrowser.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 12926 INFO: Processing standard module hook 'hook-difflib.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 13173 INFO: Processing standard module hook 'hook-multiprocessing.util.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 15190 INFO: Processing standard module hook 'hook-PIL.ImageFilter.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 16680 INFO: Processing standard module hook 'hook-pyqtgraph.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/_pyinstaller_hooks_contrib/stdhooks' 290 INFO: No OpenGL_accelerate module loaded: No module named 'OpenGL_accelerate' 430 WARNING: Failed to collect submodules for 'pyqtgraph.jupyter' because importing 'pyqtgraph.jupyter' raised: ModuleNotFoundError: No module named 'jupyter_rfb' 17597 INFO: hook-pyqtgraph: selected 'PyQt6' as Qt bindings because hook for 'PyQt6' has been run before. 17673 INFO: Processing standard module hook 'hook-PyQt6.uic.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 17923 INFO: Processing standard module hook 'hook-PyQt6.QtSvg.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 17999 INFO: Processing standard module hook 'hook-PyQt6.QtOpenGLWidgets.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 18086 INFO: Processing standard module hook 'hook-PyQt6.QtTest.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 18546 INFO: Processing standard module hook 'hook-scipy.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 19595 INFO: Processing standard module hook 'hook-scipy.special._ufuncs.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 19758 INFO: Processing standard module hook 'hook-scipy.linalg.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 21052 INFO: Processing standard module hook 'hook-scipy.special._ellip_harm_2.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 21838 INFO: Processing standard module hook 'hook-xml.dom.domreg.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 23435 INFO: Processing standard module hook 'hook-OpenGL.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/_pyinstaller_hooks_contrib/stdhooks' 45 INFO: No OpenGL_accelerate module loaded: No module named 'OpenGL_accelerate' 27020 INFO: Processing standard module hook 'hook-scipy.spatial._ckdtree.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 27848 INFO: Processing standard module hook 'hook-scipy.spatial.transform.rotation.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 28510 INFO: Processing module hooks (post-graph stage)... 28921 WARNING: Hidden import "scipy.special._cdflib" not found! 29293 INFO: Processing standard module hook 'hook-PyQt6.QtOpenGL.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 29440 INFO: Processing standard module hook 'hook-PyQt6.QtDBus.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 29981 INFO: Processing standard module hook 'hook-PIL.SpiderImagePlugin.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 30976 INFO: Performing binary vs. data reclassification (323 entries) 31196 INFO: Looking for ctypes DLLs 31621 INFO: Analyzing run-time hooks ... 31629 INFO: Including run-time hook 'pyi_rth_inspect.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/rthooks' 31633 INFO: Including run-time hook 'pyi_rth_pkgutil.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/rthooks' 31635 INFO: Including run-time hook 'pyi_rth_multiprocessing.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/rthooks' 31638 INFO: Including run-time hook 'pyi_rth_pyqtgraph_multiprocess.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/_pyinstaller_hooks_contrib/rthooks' 31640 INFO: Including run-time hook 'pyi_rth_pyqt6.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/rthooks' 31643 INFO: Processing pre-find-module-path hook 'hook-_pyi_rth_utils.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks/pre_find_module_path' 31645 INFO: Processing standard module hook 'hook-_pyi_rth_utils.py' from '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/hooks' 31690 INFO: Creating base_library.zip... 31720 INFO: Looking for dynamic libraries 35066 WARNING: Library not found: could not resolve 'libxcb-cursor.so.0', dependency of '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyQt6/Qt6/plugins/xcbglintegrations/libqxcb-glx-integration.so'. 35066 WARNING: Library not found: could not resolve 'libxcb-cursor.so.0', dependency of '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyQt6/Qt6/plugins/xcbglintegrations/libqxcb-egl-integration.so'. 35066 WARNING: Library not found: could not resolve 'libxcb-cursor.so.0', dependency of '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyQt6/Qt6/plugins/platforms/libqxcb.so'. 35066 WARNING: Library not found: could not resolve 'libxcb-cursor.so.0', dependency of '/home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyQt6/Qt6/lib/libQt6XcbQpa.so.6'. 35131 INFO: Warnings written to /home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator/warn-Mercator.txt 35248 INFO: Graph cross-reference written to /home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator/xref-Mercator.html 35305 INFO: checking PYZ 35305 INFO: Building PYZ because PYZ-00.toc is non existent 35305 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz 36549 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz completed successfully. 36578 WARNING: Ignoring icon; supported only on Windows and macOS! 36589 INFO: checking PKG 36589 INFO: Building PKG because PKG-00.toc is non existent 36589 INFO: Building PKG (CArchive) Mercator.pkg 36609 INFO: Building PKG (CArchive) Mercator.pkg completed successfully. 36610 INFO: Bootloader /home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/bootloader/Linux-64bit-intel/run 36610 INFO: checking EXE 36610 INFO: Building EXE because EXE-00.toc is non existent 36610 INFO: Building EXE from EXE-00.toc ERROR: The output directory "/home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator" is not empty. Please remove all its contents or use the -y option (remove output directory without confirmation).
-
Atlas-Tools, a package combining Mercator and post-Atlas
Asher replied to Grautvornix's topic in Scenario Design/Map making
Maybe try deleting the build folder itself? -
I've added a bunch of products, including normal and spec map. Walnuts and almonds are from here: https://opengameart.org/content/free-materials-pack-37-redux (licence CC-BY) Everything else is CC0, the olives are done entirely by me. Also, here are some dancing pears :D Extremely useful for this purpose, blender lets you make objects fall in place using rigid body baking: Textures: Sure, just need a nice 3d object to bake from.
-
@Asher Thanks ! @Grautvornix this version is better but I have this : 39875 INFO: Graph cross-reference written to /home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator/xref-Mercator.html 39925 INFO: checking PYZ 39925 INFO: Building PYZ because PYZ-00.toc is non existent 39925 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz 41085 INFO: Building PYZ (ZlibArchive) /home/felix/Téléchargements/atlas-tools-0.25.0/build/PYZ-00.pyz completed successfully. 41115 WARNING: Ignoring icon; supported only on Windows and macOS! 41126 INFO: checking PKG 41126 INFO: Building PKG because PKG-00.toc is non existent 41126 INFO: Building PKG (CArchive) Mercator.pkg 41144 INFO: Building PKG (CArchive) Mercator.pkg completed successfully. 41145 INFO: Bootloader /home/felix/Téléchargements/atlas-tools-0.25.0/.build-venv/lib/python3.12/site-packages/PyInstaller/bootloader/Linux-64bit-intel/run 41145 INFO: checking EXE 41145 INFO: Building EXE because EXE-00.toc is non existent 41145 INFO: Building EXE from EXE-00.toc ERROR: The output directory "/home/felix/Téléchargements/atlas-tools-0.25.0/build/Mercator" is not empty. Please remove all its contents or use the -y option (remove output directory without confirmation).
-
Atlas-Tools, a package combining Mercator and post-Atlas
Asher replied to Grautvornix's topic in Scenario Design/Map making
This is the problem @lilypoppy. I was getting this on linux too, I think I used --break-system-packages or something. This is how ai summarized it: -
Atlas-Tools, a package combining Mercator and post-Atlas
Asher replied to Grautvornix's topic in Scenario Design/Map making
The reason is pyinstaller makes the executable for whatever os you are using. I think I saw somewhere in the terminal output that it was converting exe to something so mac could use it -
Here is the new build script and also new spec files (bug identified: On Linux the program is a file called Mercator, with no .exe, and PyInstaller writes it into its work folder, where the spec had already made a folder of that name. Both specs now work in build/<name>/, which is PyInstaller’s own layout. I do not know why this did not stop @Asher’s macOS build, since macOS has no .exe either. Will update all spec-files, both build scripts and deliver a new release 0.26.0 very soon (will be available from the initial post on this thread). For @lilypoppy and all Ubuntu or Debian users, the whole preparation of the build should be this one line: sudo apt install python3-venv binutils libpython3.12 Attached are the new build.sh and the two new pyinstaller spec files. Things to know: The tool also needs the usual desktop libraries added (glib, OpenGL, xkbcommon and so on). A normal Linux desktop has them; a bare server would not. The Linux builds are large: about 269 MB each, against roughly 98 MB on Windows. The icon (icon.ico) is ignored on Linux; PyInstaller only supports it on Windows and macOS. The new release will 0.26 contain this: [fix] The new build scripts (build.sh and build.bat as well as mercator.spec and post-atlas.spec) and a slightly revised icon [new] It integrates the findings tab from post-atlas into mercator so to allow fixing any findings already in the tool itself without having to switch between tools anymore when creating a new map. This option is still there, however. The additional workflow and overall GUI is not yet as simple and as clear as I would like it to be. Will continue working on it. Post-Atlas.spec build.sh Mercator.spec
- Yesterday
-
@lilypoppy Oops! Sorry for the trouble! there are actually two faults, both in build.sh, not in the specs: The cause. Debian and Ubuntu refuse pip install into the system Python (PEP 668). So nothing was installed, pyinstaller did not exist, and no build ran. The misleading end. The script carried on after every failure and printed “Success!”. Working on a better script! Will come out shortly.
-
@Grautvornix @Asher Hi, the test doesn't seem to have worked: the build failed with externally-managed-environment (PEP 668) and pyinstaller: command not found, even though the script still printed "Success!". :~/Téléchargements/atlas-tools-0.25.0$ bash build.sh atlas-tools build script build script version 1.2.0 =============================================== Collecting libs... error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.12/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. =============================================== Building Mercator... build.sh: ligne 13: pyinstaller : commande introuvable Done =============================================== Building Post-Atlas... build.sh: ligne 17: pyinstaller : commande introuvable Done =============================================== Success! The executables can be found under the dist folder
-
Hi @pixel24, There are quite a few features and some differ depending on the version you got. The closest to a summary of features is the "GUI Builder/Configuration Assistant" (gear icon near mini-map when playing) which walk you to the different options, and most of the mod's feature are options there.
-
Hi, @pixel24. I'm not sure if there is a changelog but you can scroll a bit it's thread and look for @Atrik's post with the news of every release. Or maybe he knows where to find them all in one place
-
Hi@all, I just installed ModernGUI in 0ad (0.28 / Siduction Linux). Is there a summary of its features anywhere? with best
-
Hello @Asher @Grautvornix, here is a summary of the Embassy phases and diplomatic release controls: Embassy Phases & Diplomatic Release Controls: Phase Requirements: The Embassy can be built starting in Phase II (Town Phase), while "Sponsor a Colony" (reviving a completely defeated ally) requires reaching Phase III (City Phase). "Grant Land & Infrastructure" Key: Allows the host to transfer ownership of a secondary Civic Center (or outpost) and its surrounding territory/buildings directly to the sheltered ally. "Release on Host's Land" Key: Frees the sheltered ally's units while keeping them confined strictly inside the host's fortified borders so they can safely rebuild under protection. "Release Permanently" Key: Grants full independence, allowing the restored ally to leave the host's territory and operate freely across the map.
-
I agree with the fanatics part. Reducing armor (since they are naked) and health makes total sense. However i wont reduce the damage personnally but i would lower the pierce armor to 1. It makes sense to have them have super-fast high DPS units but with no survivability.
-
arsalanhaider9191 joined the community
- Last week
-
Atlas-Tools, a package combining Mercator and post-Atlas
Asher replied to Grautvornix's topic in Scenario Design/Map making
Here are pre-built app bundles for macos: macos.zip -
Akhenatom joined the community
-
The discussion was never about its latter attested haimaz cognates not meaning some kind of settlement (are you getting confused with the þurpa discussion?), but if that was the case in Proto-Germanic times. That's why I agree with the quotes you bring up, but they are completely irrelevant to the point in question. By "early" and "late" I obviously meant in reference to the Germanic-Celtic split, bringing up the "late medieval" period is quite the misrepresentation. Your source (Brink) does address what you keep ignoring regarding Celtic by saying "in Old Celtic languages we find a related formation that demonstrates another interesting theme, namely the meaning 'love'", and as you quote, concludes his chapter with: This is exactly my point (yet again you are brushing off the actual conclusions of your own sources). He refers to one's home (one's "area and place"), this doesn't necessarily point to a type of settlement, and at no point he claims that in Proto-Germanic times it referred to anything outside one's own (as seems to happen in Gothic and later, but it's completely different in Proto-Celtic and later). I completely agree, since this is my exact argument regarding þurpa. I'm glad you brought up this point, since it's the one I was going to follow up with. Two characteristics are important to name a Phase: its "multiple dwelling" quality, and its development stage. Regarding Proto-Germanic haimaz, your source doesn't claim anything beyond that it referred to one's home, even if that could have indirectly referred (only to) one's own settlement, and we both agree it can be of any size. Regarding Proto-Germanic þurpa, I've already proven its "multiple dwelling" quality using your own sources, and we both agree that it's small. Simply put: no. Urban development is the actual point of Phase names, and you know it, that's why you are pre-emptively trying to dismiss this obvious conclusion supporting what I say (as you've tried to do before). You have reached, in good part by yourself, the conclusion that þurpa is more appropriate than haimaz for Phase I, according to each of both important characteristics mentioned (being multiple dwellings, but a few).
-
Augustico joined the community
-
It was supposed to also include the worldmap data for selecting the digital elevaiton area for terrain building from scratch. It also removes (now, after bug fixing) teh not needed part of the libraries so the exe goes down from 142 MB to 98 MB for mercator and for post-Atlas from 116 to 97 MB. For me the startup process of the exe files with the "onefile" option is still way too long. This is due to the need to unpack everything during each startup. I will instead now change that to "onedir" i.e. an exe plus a folder with runtime libs. These must stay next to each other at all times.
-
Ancient Greek pottery
Nicolaus_von_Kues replied to nifa's topic in Eyecandy, custom projects and misc.
-
I believe I have defended my position several times regarding my suggestion. Cognates derived from “haimaz” that mean “village” or “settlement” have the advantage of being supported by the Gothic language, which is the attested language chronologically closest to Proto-Germanic. There are also clear examples of their use to mean “villages” and “hamlets” in Old English, Old High German and Old Frankish. Finally, place names ending in -heim, -hem, -ham, etc., are among the oldest Germanic place names, representing one of the earliest chronological layers of naming. But since my arguments have already been lost amid the recent debates, I will present a fresh set of arguments. To do so, I will begin by quoting at length from a scholar I already mentioned, Stefan Brink. In 1995, he wrote a chapter titled “Home: The Term and the Concept from a Linguistic and Settlement-Historical Viewpoint.” While it is not an exhaustive compilation of all the evidence, since it focuses on his extensive knowledge of the Scandinavian and Anglo-Saxon worlds, it serves as a very solid foundation from which to begin. 1. A collective meaning is part of the inherited Germanic evidence The modern meaning of home should not be projected backwards as though it exhausted the historical semantic range of “haimaz”. As Brink points out, ancient related Germanic words could refer not only to an individual dwelling or a farm, but also to an estate, a group of dwellings, or a village. This makes “haimaz” a plausible term for a primitive residential community rather than simply a private home. In this introductory excerpt from his article, he provides a few examples and makes it clear that the meaning of a collective dwelling is entirely valid: 2. Gothic and Lithuanian provide direct and ancient evidence of the meaning of the word “village” The Gothic evidence is especially important because it is considerably earlier than most of the surviving West and North Germanic material. Wulfila’s use of haims to translate Greek kōmē, “village” or “hamlet”, demonstrates that the collective settlement meaning was already established in a fourth-century Germanic language. The opposition between plural haimos, “countryside”, and polis, “town”, also places the word within a clearly rural settlement system. Stefan Brink considers these meanings derived from Gothic to be consistent and convincing. He even notes the similarities with two loanwords found in Lithuanian that have virtually the same meaning as in Gothic, conveying both the sense of a village and that of the countryside: 3. The toponymic evidence confirms that the word could designate an inhabited community The place-name evidence independently supports the collective use found in Gothic and Old English. Names in -ham are interpreted not only as references to farms or estates, but also to hamlets, villages and the territories occupied by particular communities. Formations such as Amersham and Gillingham show that the element could identify the settlement or district associated with a person and their followers, rather than merely that person’s individual home: 4. Specialists generally reconstruct an original meaning centred on settlement The Scandinavian material is particularly valuable because it preserves both the territorial and residential dimensions of the word. Despite continued debate over the precise scale of the referent, Brink observes that most scholars regard “settlement” as the original meaning of -he(i)m. The underlying concept is therefore not simply a house, but the place where a person or community has settled: 5. The settlement use is demonstrably ancient The collective or territorial interpretation cannot be dismissed as a late medieval development. Brink identifies a group of very old Scandinavian -he(i)m names that were probably formed around the beginning of the Common Era, including one securely dated to approximately AD 200. This places the use of haimaz and its descendants as settlement names within the chronological horizon relevant to early Germanic societies: 6. The word could include both the habitation and its surrounding resources Brink ultimately argues that the traditional opposition between “habitation” and “settlement district” is too rigid. His proposed meaning, “settlement or settlements with an area of resources”, accounts for both an individual farm and a wider community or territory. This is highly relevant to an early Germanic “village”, which need not have consisted of tightly clustered buildings but could instead have been a socially coherent settlement together with its fields, pastures, woodland and other resources, exactly what we have in the game: 7. The semantic core is an inhabited territory, not merely a building Brink’s conclusion brings the different strands of evidence together. The essential meaning of haimaz and its cognates was the place and surrounding area where a person or group lived. Depending on scale and context, this could be a farm, settlement, village, community territory, or settlement district. This semantic flexibility does not weaken haimaz as a phase name. On the contrary, it makes it particularly well suited to an early form of village whose identity rested on shared habitation, territory and belonging rather than on urban density. This concludes the excerpts from the chapter written by Stefan Brink. I will also highlight some other points that have already been mentioned. Here an excerpt of the description from the Deutsches Ortsnamenbuch (2017) about -heim place-names: I will also add two excerpts I already posted from the digital portal for place-name research in Switzerland: Another excerpt, this time from the German National Atlas: Taken together, these sources point to the same conclusion. Place names derived from haimaz belong to one of the oldest settlement-naming traditions of the Germanic world and are consistently associated with villages, hamlets, estates, and inhabited communities rather than isolated dwellings. In the Old High German sphere, -heim names are generally regarded as belonging to the earliest layers of settlement nomenclature, appearing at least during the Migration Period and possibly even earlier. The continuity of this evidence across Germany, Switzerland, and the wider Germanic-speaking world strongly supports the interpretation of haimaz as a term connected with settlement and community from a very early date. Similarly, Richard Jones, David N. Parsons, and Paul Cullen take the same position regarding England: place names related to the word “ham” date back to the earliest period: Albert Hugh Smith himself believed that place names derived from “ham” were part of the oldest layer of place names in England: Finally, there is also Old Frankish, which provides fairly strong evidence that words derived from haim often had a collective meaning. In addition to the fact that many linguists suspect this is the origin of the French word “hameau”, there is also ample evidence derived from an analysis of legal texts from the Frankish Empire. Maurits Gysseling’s analysis of the Germanic vocabulary preserved in the Lex Salica provides substantial evidence from the Frankish linguistic area. His reconstruction of haima- and his analyses of anði-haim-ja- and haima-þeuða- consistently support a collective sense equivalent to “village”. In several independent contexts, haima- clearly refers to an organized rural community rather than merely to a private household. This makes the collective meaning part of the Frankish evidence itself, not a later interpretation inferred solely from place names. To summarize, the strength of the argument does not rest on a single piece of evidence, but on the convergence of multiple independent lines of evidence, all pointing in the same direction: Taken together, the Gothic, Old English, Frankish, Baltic, Germanic, toponymic, and settlement-historical evidence converges on the same conclusion: haimaz was not simply a word used exclusively to refer to a house or a private residence. Across both language and place-name evidence, it consistently appears as a term that could denote a settlement, village, inhabited territory, or organized community. Moreover, the forms derived from it belong to some of the oldest naming traditions in the Germanic world, making haimaz not only linguistically defensible, but arguably one of the best-attested and most historically appropriate choices available.
-
Thanks for putting this survey together, @Atrik! Today we had the chance to play a 4v4 TG. The general impression was that cavalry was way too slow. I would try reducing it to 7.5/8%, half of what it is now, or 10% at most. If not, maybe get rid of acceleration (but i guess that would be a bigger change ) As for the other changes, it's difficult to draw any conclusions from just one match. I played as the Gauls and tried going for fanatics. My impression was that they were still strong (which is nice for the champion unit). However, perhaps the damage reduction is a bit too much, and we could try 10% instead. Regarding armor and HP, I think these changes are positive and might be the way to prevent fanatics from being permanently banned. I hope we can keep testing more games
-
Asher started following Does everyone need the same mod to play an online game?
-
If the mod has ignorecompatibilitychecks=true in mod.json, than nobody else needs it
-
ThePoshBarbarian started following Balance poll for R29
-
1; accidentally voted as IDK, meant to vote yes 2, 3, and 4; yes to all, especially naked fanatics. They're probably the most powerful from the list. Immortals I'm less inclined to agree but then again when I play persians, which is rare already, i just amass a ton of axemen, spearmen, and archers. Not that that makes it an easy win. 5; Voted no, kind of feels a bit cheesy? Like IDK why, just a bit worried. 6; Yes, already too expensive for what it is, and it doesn't have any way to shoot arrows when garrisoned and doesn't expand territory. Will have to see whether the price is reduced enough though. 7; No; I agree with the change to aura range, but not to resistance changes. 8; Yes; axemen should always cost slightly less metal than a sword counterpart. 9; Overall yes, but disagree on the range reduction; Leave range as is, decrease bonus damage from 3 to 2, cost change is good. 10; Yes; foundations are too easy to destroy. 11; Yes; Cavalry does feel too fast, though maybe just a 10% instead of 15%? Could try and balance it on a civ by civ basis, though that would require more work. Eg, good cav civs have less of a nerf, like persians or gauls. Less cavalry centric civs like rome/sparta have a larger nerf. Mostly to try and give them a bit more flavour between different civs. 12; Yes; Champion cav can be way too strong (glares at persians), a nerf to their health would make them less overpowered (in general, not just persians). 13; Yes; Just brings wall towers more in line with how walls work in general. 14; Hesitant yes; I haven't played too much with catafalques, but when I have, especially when you have a high number of them, some of them can make things snowball quickly. 15; Indifferent yes; Isn't that more of a bug fix?
-
Latest Topics
