Zomboid Error 4
Lien Kocurek
Seems like this specific error is mentioned in the log:
-violation-in-module-atio6axx-dll/
The error seems to be driver related with your AMD driver. In which case I would recommend reinstalling your AMD driver and making sure you have the latest version from the AMD website.
I would need both the console.txt and this err pid file, since one contains the driver versions and the other contains the errors. At the moment the error looks to be the exact same. So the above mentioned links would still apply most likely.
Hi all. I bought "Project Zomboid" off of Desura, but it won't launch. So I am trying a different route, I installed the package from the AUR and changed the PKGBUILD so it would download the latest version of the game. It installed fine but now if I try start it through the menu it won't start, so I tried invoking the projectzomboid.sh script and get this message:
I did actually but it then doesn't load. I found there is a file called "projectzomboid" and I renamed it projectzomboid.backup and then I found the game will launch, but I can't get to the menu, however I assume maybe it is just slow because of my computer specs.
I am guessing this is because I downloaded it directly from the Desura download page and then used that for the Package Build from the AUR. Desura games seem to download to the /opt directory. However using the AUR the game is installed elsewhere, so maybe this file has something to do with it?
Odd, it finally loads but it looks like it might be a hardware issue as I can't seem to select anything on the menu. I think it's because this computer is not up to snuff to handle it. Will try again on my other laptop (which has better specs) tomorrow and see how it goes.
It looks to me like there is a bug in the game. If it is a bug, I am sorry to say that there really is nothing that you can do other that wait for a new version to come out. Installing an older version (like the unmodified version in the AUR) might work.
I have no experience with running a project zomboid server, so I am not sure what to look for, but all I could find by googling regarding this error code 5 seems to have been resolved by forwarding the correct ports.
However, this error can even occur when the client and host seemingly have all the required mods installed and up to date. In this case, you will need to do some troubleshooting to determine the actual cause of the error. To help you with that, this guide will show you all the possible causes of this error and what you can do to solve them.
Instead of manually updating your Project Zomboid mods one by one through Steam, it is much better to force-update them all together. This will save you effort and ensure that every single mod is up to date. Moreover, the best part is that it can be accomplished by following a few simple steps.
When you reconnect to the server, the game will automatically install all the mods that are running on it. In this way, you will automatically update all your mods to their latest versions.
After you restart your dedicated server, take a look at your console. It will show that it has verified all the server mods in comparison to the workshop. Additionally, if it finds any outdated mods, it will update them to the latest version available in the workshop.
An easy way to ensure that your Lua folder is not corrupted is to delete it from the directory and then verify the integrity of game files on Steam. This will reinstall the Lua folder and verify all its files.
The Lua Checksum verifies that the client and server host both have the same mods installed on their systems. So if the server host disabled this option, clients would be able to bypass this check and connect to the server without any issues.
But an important thing to keep in mind is that if this error is being caused by incompatible mods (rather than missing/outdated mods), disabling this verification check may cause gameplay errors in your server.
If none of the above solutions have worked for you, or if disabling the DoLuaCheckSum option worked, but is causing gameplay errors, the cause of the error is most likely incompatible mods.
The number of mods you should disable at a time depends on how many you have installed on the server. If you have only a few mods installed, you can simply disable one mod at a time and then run the server and check for issues.
The security programs on your system may be flagging your mod files as suspicious and preventing them from working entirely. Because of this, the server may believe that your mod files are completely missing because the game is being blocked from accessing them.
To resolve this issue, you can simply create an exception for Project Zomboid and Steam in your Antivirus and Firewall settings. This will ensure that the security programs on your system do not interfere with the game files at all.
There could be some corruption deep within your game files that are preventing your game from working properly. Performing a complete reinstall of the game will ensure that none of your game files are corrupted or missing.
As Project Zomboid is still an early access title, errors and bugs can often become a part of life when playing. This is further compounded by the installation of mods from separate creators who all have different development styles and preferred update schedules. We try our absolute best to keep the server online and running error-free, but sometimes you may run into problems requiring a bit of troubleshooting.
Due to a bug in Hydrocraft, items like dollies and forklifts cannot be removed from trunks once they are placed there. You can reach out to #support to have an admin fix it. This may take time, so remember to be patient.
Very occasionally certain items like the can turn off after a restart. This is due to the way PZ works and there isn't really a way to fix it. It's thankfully rare after a number of updates and easy to fix, just flip the switch or right-click on a lamp to turn it back on.
Project Zomboid is a popular zombie survival game developed by British and Canadian independent developer, The Indie Stone. In the game, players must survive a zombie apocalypse by scavenging for food and supplies, building shelter, and fighting off hordes of the undead.
Sometimes, simply restarting the system can help resolve the Project Zomboid failed to download map from the server error. Restarting your computer will clear any temporary files and can help reset any errors that may be preventing you from downloading the map.
CoreRCON is an implementation of the RCON protocol on .NET Core. It currently supports connecting to a server, sending commands and receiving their output, multi-packat responses, and receiving logs from logaddress.
Finally, pass an array (or list of params) of IPEndPoints to express which servers you would like to receive logs from. This is because any server can send your server logs if they know which port you are listening on, as it's just UDP.
"Could not install package 'CoreRCON X.X.X'. You are trying to install this package into a project that targets '.NETFramework,Version=vy.y.y', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."
If you are seeing an error similar to this, try changing your project's targeted .NET Framework version [#11]. If you are using Visual Studio 2015, the minimum resolvable framework version is 4.7. Visual Studio 2017 has improved support for .NET Core packages, allowing CoreRCON to resolve for versions as low as 4.6.1.
@jghodd I'm sorry but this package already didn't supported i686, the arch array contains only x86_64 architecture. there's nothing to fix here, apart removing some unused lines in the PKGBUILD which were used in the past for i686 builds
@muflone - i give up on building this for a 32-bit platform. i've tried everything, even a clean chroot build, adding back the libdav1d.so.5 library, removing -fcf-protection from CFLAGS, adding -fPIC to CFLAGS, using gcc10. no matter what, i keep getting the same error:
this package won't build. i've tried a variety of approaches, the closest being a clean chroot build which produced the same error documented by @questionable below. some input from the maintainer is kinda needed here.
c80f0f1006