This is just me, but I got a nice Chestburster model instead of the Skulks and a fullgrown Alien Drone instead of Fades. It looks very cool and so far I haven't had any problems, but if the servers I frequent start having file_consistency 1 or whatever, I'll switch back.
I believe it just checks for the exact size of the file, making it basically defaults only. I jsut dropped a thread in the suggestions box about adding a more lienient file conistancy checker, like CS's, into NS 1.1. Go support it <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
kind of related, but i've gotten a few consistency error's recently...i don't change the models. They seem to be corupting themselfs or somthing. It's even happened between mapchanges, anyidea what could cause this?
I was also thinking of making all mdl files readonly, do you think this would cause problems?
REinstall NS first, jsut to make sure it's not something as simple as doing that. IF that doesn't work, do a reinstall on HL, and if that doesn't work, donwload norton, and if that doesn't work, reformat, and if that doesn't work, God has something against you <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo-->
But in all seriousness, jsut do the regular reinstalls and it should work.
coilAmateur pirate. Professional monkey. All pance.Join Date: 2002-04-12Member: 424Members, NS1 Playtester, Contributor
Occasional inexplicable file-consistancy errors can sometimes be resolved by installing the 1.04 server patch. Not sure why, but it may fix your problem.
<i><a href='http://www.faqs.org/rfcs/rfc1321.html' target='_blank'>The MD5 algorithm</a> takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. The MD5 algorithm is intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private (secret) key under a public-key cryptosystem such as RSA.</i>
In other words it's a reliable way of verifying data integrity.
Before you reinstall NS, get the server patch. That is the problem if you are getting file consistency problems. If the server turns on file consistency, you have to have the server patch to be able to play there.
hmm lets just say the chance u can create a model that won't be rejected by consistany servers is pretty low <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif'><!--endemo-->
Comments
basicaly getting around it is sorta imposible to do in any normal sense (it takes other things)
and if a server uses fileconsistancy, find another server (Use all seeing eye to make a filter that filters out that option ;D)
I was also thinking of making all mdl files readonly, do you think this would cause problems?
But in all seriousness, jsut do the regular reinstalls and it should work.
<i><a href='http://www.faqs.org/rfcs/rfc1321.html' target='_blank'>The MD5 algorithm</a> takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. The MD5 algorithm is intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private (secret) key under a public-key cryptosystem such as RSA.</i>
In other words it's a reliable way of verifying data integrity.
For example, with the MD5 algorithm, the probability that two files have the same MD5 checksum is...
1 / 16^32
= 2.9387358770557187699218413430556 x 10^-39
No comment.