The Callisto Protocol Developer Blames ‘Clerical Error’ For Dodgy Patch
Mike Sanders / 1 year ago
I daresay that it hasn’t escaped your attention that the PC release of The Callisto Protocol has gotten off to a pretty rough start. Admittedly, many of the initial complaints were regarding a huge stuttering bug which, in fairness to the developer, was (apparently) resolved pretty quickly (just circa 24 hours after its release). – Since that point, however, much of the criticism has largely transitioned to the overwhelming opinion that the PC version of the game has an overall rushed and unoptimized feeling to it.
Why? Well, predominantly because even quite potent setups (which are well in excess of the recommended hardware) were struggling to hold a solid consistent level of performance from the title. – Is The Callisto Protocol poorly optimised though? Well, following a report via IGN, the answer is now categorically yes as even the developers behind the title have confirmed that it isn’t running anywhere near as well as it should.
Rather than any particular kind of ‘unfinished’ aspect on their part, however, they have, somewhat bizarrely, cited that the poor performance of The Callisto Protocol may actually be due to a “clerical error” regarding that aforementioned patch.
The Callisto Protocol – Bad Because Someone Made a Mistake?
According to Striking Distance Studios CEO Glen Schofield, while attempting to get a patch out as quickly as possible (for the aforementioned stutter bug), the person/s at the company charged with this work accidentally accessed the wrong files. Well, more specifically, the wrong build of the game. As such, while both the PC and even console versions have seen the stuttering bug fixed, this has brought the overall stability of the title into the toilet (and yes, crashing has been an exceptionally common complaint on all versions since the last update).
While no specific details have been cited, it sounds to me that rather than accessing the finished ‘gold’ version of The Callisto Protocol, the rush to get this bug resolved saw these developers access the data from one of the beta or pre-release versions. Hence, why the ‘patch’ fixes one pretty huge problem, but seemingly tanks the overall stability.
So, yes, a little embarrassing for sure. I have to admit though that the overall honesty and openness shown by the developer here is more than a little refreshing. This disclosure has, in fact, made me substantially shift my overall opinion toward this title. Mistakes happen, and at least Striking Distance Studios seems (somewhat) happy to own this one, and, of course, look to fix it (correctly this time) in the very near future.
What do you think? – Let us know in the comments!