Jump to content

Stan`

0 A.D. Project Leader
  • Posts

    17.967
  • Joined

  • Last visited

  • Days Won

    578

Everything posted by Stan`

  1. That's caused by arch linux forcing you to use an experimental package called sdl2 compat
  2. The thing GPU skinning is supposed to improve performance since you do more things on the GPU that's less load on the CPU. cc @vladislavbelov
  3. What version of windows 10 do you have ? Are you out if disk space. We changed nothing between rc1 and 3
  4. Do you get an error running the installer?
  5. You could install wayland but the actual problem is that arch is forcing you to use SDL3 while you should use SDL2 for 0 A.D.
  6. After further investigation by @Itms it might be more complicated than this. No ETA yet. Do note however that the next release won't support Windows 7
  7. What do you want exactly ? You can download it off youtube if you want. By the way we now have a xiaohongshu account. I could use some help.
  8. Our tests yesterday indicate it might have to do with a library update we performed. We will know more today. Sorry about the inconvenience.
  9. Just use print() error() and warn() If it's an object or array do warn(uneval(obj));
  10. Do you have all the latest windows updates and the microsoft visual c++ 2017 redistributables ?
  11. Do you have either gpu skinning or resolution scaling enabled in the options ?
  12. Do you use Arch Linux? If so this is a known bug of them trying to use SDL3 instead of SDL2 through sdl compat. You might use the workaround described at https://gitea.wildfiregames.com/0ad/0ad/issues/7569
  13. No git tag in SVN where all the shaders are...
  14. On macOS they are hidden folders so it will be hard to access them via the UI. You can however open a terminal and use a command like so open /Users/{YOUR USERNAME}/Library/Application\ Support/0ad/
  15. Can you disable GPU Skinning ?
  16. It's hard to say. There shouldn't be any roadblocks this time, so it might be fast. They have just been notified today though.
  17. Hello @KeepThinkin Can you give us more information about your mac and the version you are playing ? See ReportingErrors and GameDataPaths. Hopefully interestinglog.html will contain some useful logs to us.
  18. https://github.com/flathub/com.play0ad.zeroad/issues/130
  19. @Samulis made 24 of the 26 that were added in A26
  20. It's an issue with compute shaders. It might be hard to reproduce since we now disabled them for nouveau and GL
  21. When it breaks™. Basically each new version you need to check if the file was changed. You can go on Gitea to see the last modification dates and see what changed by looking at the commit message. Each release has two pages. A list of major changes and a small porting guide. https://gitea.wildfiregames.com/0ad/0ad/wiki/Alpha27 You can help by enriching the later https://gitea.wildfiregames.com/0ad/0ad/wiki/PortA26ToA27 Every errors are logged in a file called interestinglog.html See this page for where to find it https://gitea.wildfiregames.com/0ad/0ad/wiki/GameDataPaths This file is wiped on each game start.
  22. That's why using >= is bad because each new version might break everything
×
×
  • Create New...