Vipeax

It wasn't in the previous round.

A fair amount of users has received the following message in the past few hours/days (duration depends on the cause): Now there are multiple reasons for this message and due to the number of different threads, emails and PMs regarding this I will try to give you a summary on what's causing it and what you should do. The first and oldest cause of this, was during the change in the database system, which required a newer version of the server-side application of the Hive. This update toke place a while ago (to be exact when female skins were added) and the message is essentially a reference to that update, as it's the first time a character would stop loading and the cause was that the returned character values were not compatible with the old version. The returned message itself never changed as it essentially means a character's data can't be parsed into a working character state, which is what happens when a character is being loaded in by the server and sent to your client. These days this message is therefor a bit false and may very well be changed into something more informative. These days it can be caused by the following: Character corruption Server not being whitelisted/firewall False data being returned Hive being down Character corruption The most recent cause for this was the adding of melee weapons. As many may have noticed the workaround to add melee weapons still requires it to have "ammo". The bug that appeared during it's first release was that characters would stock a gigantic amount of hatchets/crowbars into their inventory, which caused the character's data to become too big to actually load in. Most of these have been filtered out fairly quickly, but some people are still having this problem as of today. These are easy to fix, but are only fixable by us, so if you are in this situation it's important to notify us regarding this issue. Server not being whitelisted/firewall In this situation a server never actually receives any data from the Hive, which again makes it impossible to parse any of a character's data, resulting in the incorrect-version message. This can be caused by the server not being whitelisted (anymore?), a firewall blocking the TCP traffic or the Microsoft Visual C++ 2008 Redistributable Package (32-bit/x86) not being installed, which causes the Hive Extension to never be loaded at all. The solutions for this are therefor simple: You've setup a server without actually going through the right steps of hosting a DayZ server, so make sure you contact anyone of the server admin team. A firewall is blocking the traffic, in other words you have some kind of firewall blocking port 3306 (which can be both ways). You need to install the Microsoft Visual C++ 2008 Redistributable Package (x86) package on the server, which can be found here: http://www.microsoft.com/en-us/download/details.aspx?id=29. False data being returned False data being returned is what became the most common with the release of the ARMA X Anniverersary edition. With the direct cause being the following change: Due to the PlayerID currently being handled as an integer (set of numbers, see google for more info if you care) the more recent beta builds/anniversary edition are requesting the information with PlayerIDs that can't be found, as the sent data is not matching the type it's looking for. Hive being down This is fairly easy to recognize, as everyone stops being able to connect. It's also the issue we try to prevent at all costs. Recognizing the issue and the solution(s) Now that you should have a decent idea of what could be going on I will give a brief summary on how to detect which of these is the issue and how to deal with them. The first step you should take is either checking the forums or the IRC channel to see if a lot of other people are having this issue. If so it's most likely the Hive being down entirely, which is something you can't fix, but we will immediately respond and try to fix this as fast as we can, to be exact this happened just a moment ago, after a database change to prepare the Hive for 1.7.2, which should have been fixed now. If this is not the case the next (till 1.7.2) most common cause will be that you are running a recent build, which has the new string-based Player ID. You can find your player ID easily by going to the main menu of ARMA 2 -> Profiles -> Edit -> the ID that appears at the bottom of the tiny window that opened up. If this contains anything but numbers (say 123456ABC) it means you are running a version that we don't support yet, but it's an issue that has a high priority and will be fixed very soon. If also this is not the case (your player ID clearly existed out of only numbers, say 123456) you are either joining a broken server (see point 2) or your character is corrupted (see point 1). To determine which one of the 2 it is, try joining a few servers that are clearly working (>= 40 people playing) and if you keep getting that error, your character is corrupted. To solve this I will need your Player ID so that I can fix your character. So if your character is corrupted you can either post it here (or PM it to me, but having them here is more likely to get it fixed sooner). All other causes are unrelated to your specific situation and thus I can't fix them at this very moment for you. For the people who simply patched to a newer beta version of ARMA2, try reversing your update by going back to a version that doesn't support the newer Player ID system. For other issues, see the above. We are sorry for those affected by these issues and please be aware that we are doing our very best to get everyone playing again. Edit: TR!PLE has found a fix for people with the ARMA2 X-edition, showing it is indeed possible to just drop down in (beta) patches: Do not use SixUpdater! Clean Arma2 X installation update to ArmA2 CO 1.60 official (707MB) update to Arma2 93965 beta Install DayZ 1.7.1.5 alpha (14 files go here -> .../Arma2/@DayZ/Addons) Start Arma2oa with the beta shortcut Check "beta" and "@DayZ" ingame Play on servers saying DayZ 1.7.1.5 and beta 93965

Since when are only clients venerable to hooks (or even memory reading)? You could apply the same logic on the server-side to grab information from memory to draw a visual representation of all player activity on your server, no need for the source as the server has less anti-cheat to worry about too... The big argument on closed source stopping "hacking" is wrong. The subject referenced here as hackers, is people using the standard scripting API to spawn items and the alike. There is nothing of a hack in there, apart from a possible bypass to circumvent BattlEye, which in some cases doesn't even deserve the term 'hack' either. Making the game closed source won't stop hacking at all, as the parts that should be called 'hacking' are being done in ARMA2/DayZ right now to allow the use of scripts in the first place (which covers like 95 to 99% of the cheats out there). On the other hand, while a semi decent reverser will easily find all the required info for most of the populair hacking features, open source makes network exploits, full knowledge of classes and structs 100 times easier. Some numbers in memory really don't make sense till you see the actual source of that class, and suddenly these unexplainable random numbers become golden. ;)

Grr. :( ;)

Humanity persists through death, but it increases by simply not killing people who have a positive humanity (blood bags speed it up more, but just living in the woods will get you out of it in a decent amount of time too).

The same, though I play on the US server while being Dutch.

http://dayzmod.com/forum/index.php?/topic/25099-out-of-bounds-itemvehicles-cleanup-2012-07-06/#entry246070 Been considering for a while to just have the Hive hate on anything that goes beyond the borders, but so far haven't implemented it. Will bring it into the convo again.

You should try World of Tanks.... ;)

I remember a time with Sawyer saying none would use it when I said we should release it as a component on the internet.... Well done :).

Just trying to catch the actual cause as it's odd how none of us had this issue, which makes me think that the people having the loading issues have a common situation that is beyond just 'running 1.7.2.4' as then everyone should have it. As to that I think it's important to try and catch the root of this issue. I'd appreciate it if people with issues can try to fill in this form so there is some info to go by. For example: Current Versions: ARMA2: 1.62.95389 DayZ: 1.7.2.4 To be found at the bottom right of the main menu screen: Start-up Method: ARMA 2 Launcher ("-mod=E:\Bohemia Interactive\ArmA 2;Expansion;ca;Expansion\beta;Expansion\beta\Expansion;@dayz" "-name=Robert" -nosplash -winxp -noPause -world=empty -maxMem=2047 -cpuCount=4 -maxVRAM=2047) Possible other options: Shortcut, Batch file, SixUpdater, DayZCommander, other custom launcher etc. Please list them and preferably with any start-up/command-line info that you can share. Source of files: Torrent (http://dayzmod.com/DayZ-1.7.2.4.torrent) Possible other options: Website, mirror, SixUpdater, CDN, dropbox, friend etc. File sizes of the PBOs in the @DayZ folder: Try to make it detailed so that it's possible to find the common factor. Thanks!

Hey everyone, many of the changes in 1.7.2.4 include changes in the way the game communicates with the Hive. These changes require every server to be running the latest version of both the mod & the Hive component, run with BattlEye enabled, as well as a recent beta build (>= 95389). To make sure every server is in sync with the recent developments, we are required to disable older versions of the Hive extension from being functional in the near future, which, at this point, is estimated to occure in about 36 hours from the creation of this thread (subject to change). Tomorrow morning there will be a final wording regarding this subject. The re-introduction of Helicopters is directly affiliated to this change and thus they will not be functional till previous versions of both DayZ as well as the Hive component have deflated, as the changes of the recent patch are mandatory to make them functional. Further testing also showed a small bug in the Hive component, for which we will be releasing a second update for on the server side (0.7.2), which has been made available in the regular distrubtion areas for hosters. Changelog: * [FIXED] Vehicles with ID's above 1 million didn't synchronize. * [FIXED] First object in the database not being loaded. Again I'd like to remind all hosters that running a build that is >= 95389 is required, BattlEye has to be enabled for your server to be fully functional and it is very import that you update your Hive component to the latest version within the next 36 hours.

Fair game is a bit of an excessive way of wording it. You don't get banned for picking up items, but promoting it is another subject...

A bit of a weird thread to compare 2 products, of which you know very little to nothing. The only fact you can go by is that they will have changed a fair bunch (I'd expect quite a lot, be it big or small changes) from what they learned from DayZ as a mod, so the players that liked DayZ are likely to enjoy WarZ too, unless they'd manage to screw up big time, but they have the advantage of having learned from both the positives as well as the negatives DayZ has, resulting in a huge advantage to tweaking a final product (on the other hand the "WoW copies" didn't seem to do that aspect right). At the moment the poll looks like this: The top 2 options are based on nothing, the latter 2 make a lot of sense.

Do me a favor and filter by my name, if you can join these quickly it's the server you are playing on that causes it.

Should be fixed now, but please post the ticket ID as well.

Desync only occures like that to the passengers, your pilot actually failed on the flying part... FPS lag? Could be, but him flipping over is him doing it as he streams HIS location and angle to the server, not the other way around.

No, bullets, grenades, cans to the head and all that not damaging you isn't fixing trust, it's making it PvE.

See if you can get your hoster to send me his server files, it's easy to check and impossible to debug with half the people (mostly who own the server physically) saying it works fine and the other half says it doesn't.

Sounds like 0.7.1 vs 0.7.2...

Way to DDoS a server.

Oh oh.

Server-side option ;).

Your issue:

Maybe it just wasn't that easy this time? They are 100% loaded in if your server restarted (with 0.7.2).