.:`=-~rANdOm~`-=:. Game Servers
Support (Read Only) => Help => Topic started by: Travelsonic on June 22, 2011, 05:21:20 PM
-
Ok, so nowadays instead of playing on my Windows XP desktop, I play on my OS X equipped Macbook Pro.
The only problem is, when it comes to downloading new maps from the server, it is a 25-75 crapshoot as to whether or not it will be the 25% where the map downloads successfully, or the 75% where GMod throws "Could not CRC map" and disconnects me from the server.
Never happened on my XP computer, ever.
Why the fuck is this continually going on, and what can fix it?
-
my best guess would be to delete all the downloaded maps and try again
or also try to download them somewhere elsewhere
-
I play on my OS X equipped Macbook Pro.
There's your problem.
-
or also try to download them somewhere elsewhere
That's gonna get really annoying - it only happens on ZS and occasionally on Flood, hasn't yet on TTT.
-
That's gonna get really annoying - it only happens on ZS and occasionally on Flood, hasn't yet on TTT.
Garry was the one who added in compatibility for Mac I think. And since he breaks something important every update, it's no surprise that something for Mac has screwed up.
-
Garry was the one who added in compatibility for Mac I think. And since he breaks something important every update, it's no surprise that something for Mac has screwed up.
Indeed.
Though through all of the update issues for GMod, I'm left wondering how he manages to fuck something up every time he updates it.
-
Indeed.
Though through all of the update issues for GMod, I'm left wondering how he manages to fuck something up every time he updates it.
And it's funny, because it's usually a small, lua vector code thing that when changed, it happens to fuck up a whole swep pack/tool/game start-up session.
-
And it's funny, because it's usually a small, lua vector code thing that when changed, it happens to fuck up a whole swep pack/tool/game start-up session.
I wouldn't be surprised if he fell victim to the issue of making code, functions, et cetera dependent on other functions/code in such a way where a small change fucks it all up. There is a term for that I learned in one of my CompSci courses that slips my mind, but definitely something you'd want to avoid in favor of code designed to be as modular as possible.
[I am speculating, but from what you described, that sounds like one //possibility// as to why the cascade of issues occurs]
-
When you change one thing, another seems to break itself somehow
It's just the way coding works
>.<
-
When you change one thing, another seems to break itself somehow
It's just the way coding works
>.<
Code is not modular enough, or overly dependent on other functions remaining unchanged.