Discuss Fantasy football-style board games - GW's Blood Bowl, Impact!'s Elfball, Privateer Press' Grind, Heresy's Deathball, etc. THIS IS NOT AN NFL FANTASY FOOTBALL SITE!
Ok, its not seeing Darkson being beaten by his own dice every game however after my 12 hr dayshift its home food & beer then a quick game with my Nurgle team to relax. jobs a good un!!
would i prefer tabletop? of course, however anything that promotes the game and maybe brings in new players (Im sure Ive seen several people post here that they will be playing tourneys after trying the game) has got to be a good thing.
glowworm wrote:Ok, its not seeing Darkson being beaten by his own dice every game
I'll try and find you a replay of my last OCC league game...
Reason:''
Currently an ex-Blood Bowl coach, most likely to be found dying to Armoured Skeletons in the frozen ruins of Felstad, or bleeding into the arena sands of Rome or burning rubber for Mars' entertainment.
I just picked up the Legendary Edition and I can't even play it...for some reason the game "hitches" about every second and I can watch two frames draw, then it stops, then does it again, then stops...even on the menu screens, I can individually watch every single option sliiiiiiide from the left and it takes about thirty seconds.
Anyone have any idea what's up with this?
Reason:''
Anything I say is totally opinion and (knowing my luck) probably completely wrong. Keep this in mind.
2.0.0.4 and 2.0.0.5 are all "bugged" with a memory leak (2.0.0.6 patch supposedly due this week), which is causing all sorts of issues, especially on lower RAM machines.
Reason:''
Currently an ex-Blood Bowl coach, most likely to be found dying to Armoured Skeletons in the frozen ruins of Felstad, or bleeding into the arena sands of Rome or burning rubber for Mars' entertainment.
And I have 4 gigs of RAM, so I'm hardly a "low-RAM" machine. And hell, it's not even enough time for a memory leak to occur...it's on the main-bloody-menu.
Reason:''
Anything I say is totally opinion and (knowing my luck) probably completely wrong. Keep this in mind.
@ Dragoonkin - what OS are you running, and what anti-virus do you use?
Reason:''
Currently an ex-Blood Bowl coach, most likely to be found dying to Armoured Skeletons in the frozen ruins of Felstad, or bleeding into the arena sands of Rome or burning rubber for Mars' entertainment.
If I hear one more non-programmer cite "memory leaks" as an issue I think I'll scream. Don't bother doing it deliberately, though - you won't be able to hear me from there, I suspect.
VoodooMike wrote:If I hear one more non-programmer cite "memory leaks" as an issue I think I'll scream. Don't bother doing it deliberately, though - you won't be able to hear me from there, I suspect.
VoodooMike wrote:If I hear one more non-programmer cite "memory leaks" as an issue I think I'll scream. Don't bother doing it deliberately, though - you won't be able to hear me from there, I suspect.
Sweet jesus this! >_<
What the dingus does it mean? Did they just make it up? My partner is a harware engineer (yeah I know not the highest authority) but they had no idea what you were talking about!
Your computer's operating system acts as something of a gatekeeper when it comes to your computer's resources and what the software gets to do with them. When a program needs memory to store... anything... it tells the OS that it needs some memory (its more specific than "some" obviously) and the OS earmarks a chunk of memory that big for the program and tells it how to access that memory. This prevents two programs from using the same piece of memory accidentally... in fact, windows throws up walls and guards and guns around the memory.. sort'v.
Anyway, this is all based on the idea that the program will be polite and say "ok, thanks, I'm done with it now" so that the OS can assign that memory elsewhere when it is needed for something else. A memory "leak" is when the software rudely neglects to inform the OS that it is done with the memory and thus that memory is still protected against re-use, but is not BEING used by anybody.
In the past this was a problem that would make your whole session worse over time. If a program had a memory leak the memory would be lost even once you closed the program... being lost until you rebooted. That's not the case anymore - now the leaks are only an issue if you run a leaky program for a long time... long enough for it to slowly leak away all your computer's available memory (which, on modern computers, is a metric f*ck-ton). OSs like Windows will automagically free up pretty much all the leaked memory once the program closes.
BBLE's issue is NOT a memory leak, but on the official forums the pack of non-programmers there have simply decided by consensus that that's what it is. Think of this like being a doctor and listening to a group of highschool girls discussing a friend of theirs having swollen glands and them deciding that it is obviously Lupus.
Pmcc did so many totally shitty things during the 2.0.0.4 patch (which carry over into 2.0.0.5).. the most notably absent of which being a fix for RNG prediction. The half-assed obfuscation stuff is causing really sloppy performance degradation that is totally unneccesary - many people have detailed firm solutions that require no such CPU intensive garbage. Add to that the fact that BBLE now deep-scans your other processes as though it were an antivirus program (only its not protecting you - its attempting to make sure you aren't running any programs that cyanide and focus disapprove of) without asking your permission to do so (unlike punkbuster which does NOT do deep scanning as far as I'm aware, but still informs you it will be monitoring some aspects of your computer).
however after my 12 hr dayshift its home food & beer then a quick game with my Nurgle team to relax. jobs a good un!!
