Tags: Beyond Divinity; Larian Studios
There's another <a href="http://rpgvault.ign.com/articles/505/505220p1.html">peek of the week</a> thingy about <A href="http://www.riftrunner.com">Beyond Divinity</a> over at <a href="http://rpgvault.ign.com/">RPGVault</a>. It basically covers the post release problems they're having with their copy protection scheme which involves encrypting the game data. Here's a clip:
<br>
<br>
<blockquote>Which is where things started going wrong. Pretty confident about it all, we started up the tool that would encrypt our patched .exe, and soon enough, the copy protection program told us all was clear. But when we tried to run the patch on the master data, the .exe crashed. After some cursing and trying to re-encrypt (which takes ages - well, at least half an hour) some of our programmers started becoming white (I got red instead). It started dawning on us that the data that was encrypted on the CDs was not the same data that was labelled as being the master data. This effectively meant that we couldn't create a new patch unless we redistributed the entire data - which would mean a 600 MB patch...</blockquote>
<br>
<br>
Sounds like a novel idea for a copy protection scheme, with only that slight little problem of 600MB patches.
<br>
<br>
Spotted at: <A HREF="http://www.larian.com">Larian's website</A>
There's another <a href="http://rpgvault.ign.com/articles/505/505220p1.html">peek of the week</a> thingy about <A href="http://www.riftrunner.com">Beyond Divinity</a> over at <a href="http://rpgvault.ign.com/">RPGVault</a>. It basically covers the post release problems they're having with their copy protection scheme which involves encrypting the game data. Here's a clip:
<br>
<br>
<blockquote>Which is where things started going wrong. Pretty confident about it all, we started up the tool that would encrypt our patched .exe, and soon enough, the copy protection program told us all was clear. But when we tried to run the patch on the master data, the .exe crashed. After some cursing and trying to re-encrypt (which takes ages - well, at least half an hour) some of our programmers started becoming white (I got red instead). It started dawning on us that the data that was encrypted on the CDs was not the same data that was labelled as being the master data. This effectively meant that we couldn't create a new patch unless we redistributed the entire data - which would mean a 600 MB patch...</blockquote>
<br>
<br>
Sounds like a novel idea for a copy protection scheme, with only that slight little problem of 600MB patches.
<br>
<br>
Spotted at: <A HREF="http://www.larian.com">Larian's website</A>
