Exception Code: 0xC0000005 Exception Address: 0x0054162C
-
ChosenUndead No that is entirely wrong. The phrase "works on my machine" is genuinely a possibility, because I'm a victim of the opposite where all the developers on our team who attempted could not replicate the issue that likely only happens on my computer. The steps to reproduce the error were 100% consistent, but only on my specific computer with its specific firmware, hardware, and software combination. However we did eventually figure out that the issue was caused by a Plutonium patch that was made sometime in the last 2 years, though which specific patch we don't actually know yet. Basically it is entirely possible for issues to exist that may only affect a small portion of users even if those users don't use the software in unusual ways or their setups are completely fine. Though it is always possible that even if only a small amount of the userbase is affected by symptoms of the erroneous code, it could simply have other effects which you may not notice unless it presents itself as a crash or other unexpected behavior.
While we would definitely like to detect all possible bugs before an update reaches prod, it is simply impossible for a team of our size, budget, and free time to actually reliably test enough different combinations of software, hardware, and firmware to have a chance of catching bugs like the one this topic is about.
Will the bug be fixed soon? Probably not unless we are able to learn of a semi-reliable way of replicating the issue under the debugger or learn commonalities between different user's crashes.
Will the bug be fixed eventually? I like to think we have a fairly good track record for eventually fixing bugs that are unintentionally introduced in our updates, so while it may take some time we should be able to fix this particular crash like many before it.JezuzLizard Well first of all thank you for the clapback. Anyways if its any help for this particular issue i belive it was introduced in one of the latest updates (probably in r3855/r3869, r3903 or r3963) as i was able to play plutonium just fine with the exact same setup just a few months ago unless i just wasnt affected by the bug until now.
Another intestesting fact is that i booted up up an ancient bootdrive of mine which admiteddly is fairy fucked when it comes to being bloated but i experienced the exact same issue on that one as i did on my clean bootdrive, both of which had plutonium running just fine before. The only real link between my 2 bootdrives are everyday programs like firefox, discord etc and my GPU drivers, which is bad news because it doesnt seem to be a conflict with any software i recently installed. I also tested older GPU drivers that are known good with plutonium (since i played pluto with them before) but the issue still persisted. Other things ive tried where turning off stuff like Resizable bar which i thought might have a chance to mess with older games like BO2 but still no change :/. Compatability mode for t6mp was also a wash but thats to be expected.
I did also try BO2 zombies and that worked fine for the like 2 rounds i played on a populated server so its probably MP only unless the crash trigger didnt happen during my 5 min of playtime but happens almost instantly when joining a server in MP. I guess the next step would be to create an entirely new bootdrive with a fresh copy of windows so that the particular software combination might be figured out but i also might not have the energy for that for now.
This really is a frustratingly elusive bug. Anyways if you guys need someone to make a dump or something similar with a debugger i would be happy to help.
-
Elbaan So I'm very confused by your initial statement of "Tested Black Ops II Zombies and it works fine there", which is then followed by a console log with an error message that should NEVER happen in bold text. The only way that error can realistically occur is if the core fastfiles clientside or serverside are not identical to the other. More specifically it would be the file in each map's primary fastfile called mp/configstrings/configstrings_<mapname>.csv is not the same when loading that map when joining the server on both the client and server.
In this case your files are incorrect and you are not using the official Steam files as I tested joining the same exact server you triggered the error for and did not get the error. From what I can tell this is not related to what language you are playing the game in, as unlike the German version of Black Op 1 the executable is not modified nor are core fastfiles different from the other languages.
JezuzLizard Please read the Original Thread message, there was never a pirated version on my pc ever
"In this case your files are incorrect and you are not using the official Steam files as I tested joining the same exact server you triggered the error for and did not get the error."
Bo2 Zombies works, doesn't matter what errors I get in bo2 zombies , works so idc, let us keep this post about bo2 multiplayer
The game works fine without plutonium like all other games that I play these days
"While we would definitely like to detect all possible bugs before an update reaches prod, it is simply impossible for a team of our size, budget, and free time to actually reliably test enough different combinations of software, hardware, and firmware to have a chance of catching bugs like the one this topic is about."
How about proper logging where the error occurs? like this bug is now open since 2 months and all the time its "next update will fix the issue" and yet the error occurs, like I'm a software dev myself and this is not how you are supposed to work if you don't test nor even know why the issue occur
Just stop wasting time with forum post and give the people that have the issue a debug version where they can properly identify, why is this so god damn hard?
-
Elbaan So I'm very confused by your initial statement of "Tested Black Ops II Zombies and it works fine there", which is then followed by a console log with an error message that should NEVER happen in bold text. The only way that error can realistically occur is if the core fastfiles clientside or serverside are not identical to the other. More specifically it would be the file in each map's primary fastfile called mp/configstrings/configstrings_<mapname>.csv is not the same when loading that map when joining the server on both the client and server.
In this case your files are incorrect and you are not using the official Steam files as I tested joining the same exact server you triggered the error for and did not get the error. From what I can tell this is not related to what language you are playing the game in, as unlike the German version of Black Op 1 the executable is not modified nor are core fastfiles different from the other languages.
JezuzLizard I know you prolly don't care to hear this coming from me. But I hugely appreciate all the time and effort y'all put into this project. Like this guy said hes a software dev himself xD shiiiiiiitt id like to see him accomplish 1/500th of what yall have made for use
-
JezuzLizard Please read the Original Thread message, there was never a pirated version on my pc ever
"In this case your files are incorrect and you are not using the official Steam files as I tested joining the same exact server you triggered the error for and did not get the error."
Bo2 Zombies works, doesn't matter what errors I get in bo2 zombies , works so idc, let us keep this post about bo2 multiplayer
The game works fine without plutonium like all other games that I play these days
"While we would definitely like to detect all possible bugs before an update reaches prod, it is simply impossible for a team of our size, budget, and free time to actually reliably test enough different combinations of software, hardware, and firmware to have a chance of catching bugs like the one this topic is about."
How about proper logging where the error occurs? like this bug is now open since 2 months and all the time its "next update will fix the issue" and yet the error occurs, like I'm a software dev myself and this is not how you are supposed to work if you don't test nor even know why the issue occur
Just stop wasting time with forum post and give the people that have the issue a debug version where they can properly identify, why is this so god damn hard?
Elbaan We cannot just share a debug build of Plutonium. Because in order for it to be usable for debugging this issue we would have to remove the anti-cheat, and anti-tamper, and also allow the build to connect to regular servers online. This basically means that if this build is distributed to others there would be a build that anyone could use to cheat with completely invalidating the anti-cheat that was developed.
-
__EFK__ thx for sharing your information
-
Elbaan We cannot just share a debug build of Plutonium. Because in order for it to be usable for debugging this issue we would have to remove the anti-cheat, and anti-tamper, and also allow the build to connect to regular servers online. This basically means that if this build is distributed to others there would be a build that anyone could use to cheat with completely invalidating the anti-cheat that was developed.
JezuzLizard the Debug Version could also be just from a stable branch with more logging included, we don't ask for a build that allows more manipulation
-
In other news, free for all matches seems to work better i was able to join and play a whole match but it crashes after the map restarted.
-
I’ve found a reliable way to reproduce the problem, and my clue was my discoveries in this post.
To reiterate from the linked post, players outside of the range of the player’s
com_maxclientsdvar value appear invisible to the player. The crash seems to occur when an invisible player is killed, but not when visible players are killed. The following video shows the steps I’ve followed to reproduce the crash with bots on a locally hosted server: https://youtu.be/8UffSeXjC8Q
Crashdump files link: https://mega.nz/folder/IxMwjQrT#j-lUr0ojV4GEiV-eDEHruA -
__EFK__ your video doesn’t mention why the players appear invisible or why the functions can’t be read in the first place. I recall seeing one of the staff in Discord mentioning that the crash occurs when a corpse spawns. So, I’d imagine the information from your posts and your video are things the devs are already aware of, they just don’t know why it happens in the first place.
-
undefined NotCracked referenced this topic on
-
Faeotic on discord found a workaround that acutally works:
"Goto the main menu of the affected game and hit p. Set your party limit to 1 then the max. This should allow you to join servers without crashing"
p => Set it to 1 => close then p => set it to 18 => join any server and it works
