historic_bruno

There is still no info on how to reproduce this. Which building were you placing, and where on the map, was it in fog of war or a visible spot?

Yes, we need to know which OS you are using. Can you attach the logs from the game's log folder? At least system_info.txt, and interestinglog.html would be useful, also crashlogs if you have them (on Windows). You can zip these files before attaching here if they are too large.

I believe we already collect a small amount of profiling data for users who have reporting enabled, but we don't do anything with it yet. It would be better to have a benchmark mode for the game that tries lots of different settings on specific maps, and outputs data we actually use http://trac.wildfiregames.com/ticket/837

If you check Windows task manager, are there multiple instances of pyrogenesis.exe running? Did the game crash or stop working before this? Do you have antivirus software running?

Was this fixed?

Ah, I didn't check the forum for a few days, so I missed this, but glad to see it's taken care of My unconfirmed suspicion was that it's a bug in Apple's version of libc++, only affecting debug builds

I think you might do better asking on Linux Mint forums how to cleanly install/uninstall the packages, as that is specific to each distro, and I have never used Mint or the PPAs.

The errors don't have anything to do with drivers or graphics card. I notice in your first screenshot, it shows the 0ad.dev PPA and you mention installing it, but that is a development snapshot of the game and not intended for most users, as it explains here. It is probably broken due to recent changes in mod structure, very likely the package maintainer doesn't even know about them yet. I would recommend sticking with the non-development A16 version of the game (0ad) unless you want to encounter these kinds of bugs Can you confirm if the A16 package from May (0ad not 0ad.dev) works for you? Not really, most of what we do isn't OS specific, so it benefits Windows, Linux and OS X users equally. When something does break, we have enough users that generally we hear about it fairly quickly and can address them

Seems like it doesn't have the data package installed, or it's the wrong version?

It's not the highest priority bug for A17 at this point (compared to serious crashes). I'm familiar with the autostart code and have some ideas of what might have broken, so I will take a look at it.

In that case, it's a (fairly serious) bug in the engine and nothing inherently wrong with the path. But considering our default installer path hasn't changed in years and it works for many users, it's strange to suddenly have so many reports of this crash. I think it's something far more subtle. We need to add some debugging output in the engine for this case.

I'm all for audio cues for most GUI events, as long as there is a way to turn them off (e.g. a GUI volume control, though for more annoying/repetitive sounds, individual settings might be good).

It's a bug that should be fixed before A17 (#2753), along with a few others.

No, that was a suggested workaround and a way to test if the problem was autostart-specific. If you confirm it is indeed autostart (like, with a proper bug report instead of a rambling forum post), then we know where to look to fix it. Personally, I don't have time to setup tests for this and without narrowing it down further, no time to debug it.

Indeed it's a known problem. I don't have a Retina display to test, but the problem should be greatly reduced by the upgrade to SDL2, which could happen as soon the next release, A17.

Have you tried without autostart, going through normal game setup? Autostart init is weird, buggy and full of hacks, it wouldn't surprise me if it had some issues like this. That said, this should be fixed, the AIs definitely need accurate players data.

I did get a pyrogenesis binary and it works after a fashion get the Mod selection screen select 0 AD then start then black With this output in the terminal I have seen the libpng warning before with the same black screen as a result so my issue seems X-windows related will rebuild with the debug flags set and post the full back trace. Enjoy the Choice The libpng warning is just that, and should be completely harmless. There's a workaround for the mod selection problems (see #2753), choose to save configuration and then close and reopen the game, you won't get the mod selection screen.

In SVN and for A17, Enet is no longer bundled with the game. It's available as a package for just about any Linux distro though, and the build instructions have been updated to require it.

I wonder if the game crashed silently but continued to run in the background (pyrogenesis.exe), it can do that if it enters a debugging loop, I believe. That would lock the used files and prevent uninstallation, while running two instances of the game at once (on Windows) would certainly cause errors and crashes. It might very well be the cause of the mysterious VFS errors.

It's easier to look at a diff/patch. If you're using SVN, you should be able to generate a patch of the file(s) you change. I don't know your OS, but on Windows w/ TortoiseSVN, just right-click the folder or file and choose TortoiseSVN > Create patch - you can then copy/paste the diff. On *nix, you would want something like "svn diff" to accomplish the same.

What is "the NSIS fault"? Please post the exact error(s) you get. Typically, installer errors are due to a corrupted/incomplete download, so you should delete the downloaded file and redownload it. Which version of Windows are you running?

They are organized by process ID, and then numbered by session. I'm not sure what happens if you get the same process ID again in a separate run of the game.

Since you're on Linux, you should run the game in gdb as described here, then reproduce the crash to get a useful call stack. Without more information, we can't do much to help. At a minimum, you should tell us which OS you're using (system_info.txt will list this and more), and it would be helpful if you can attach the saved game file that causes the crash (see GameDataPaths, just rename the .0adsave to .zip before attaching)

I assume you're building from SVN? First, make sure the SVN checkout completed with no errors (you can SVN update until it finishes without error). Then make sure you're following these instructions for Windows.

It might be nice to mention this on our Linux download page: http://play0ad.com/download/linux/#Debian and the same for other distros as applicable. If it's not something that's obvious to users of the OS, and it sounds like it's not.