![]() Critics must acknowledge and respect the varied play practices of various kinds of players in exploring what any given videogame means. Following from this, I develop a framework which considers the role of the player as part of the game system, whose attitude will influence their relationship with the videogame. The analysis of various approaches to videogames, from ludology to unit operations and simulation, places each approach alongside each other to compare and contrast what is gained and lost by adhering to each perspective. ![]() For those of us insane enough to have a Megaproject in mind that requires a full 16x16 embark, it would certainly be nice to be able to play the game to the full capabilities that it proclaims to have.This thesis is a critical examination of videogame theory and of videogames. With all modern processors capable of running 64 bit or 32 bit mode, and a vast majority of pre-packaged systems going 64 bit, I would like to re-request that future versions be compiled for both x86 and 圆4. System specs are not at play here (quadcore i7, 24 gigs of ram, win 7 圆4), it's the simple fact that 32 bit programs can only use a maximum of 2 gigs of ram (without being linked to LargeAddressAware, or on 32bit systems) or 4 gigs of ram on 64 bit systems with Large Address Aware linked. This means I wouldn't be able to actually *play* for very long before hitting the LAA limit of 4 gigs. Running the LAA tool to force Large Address Aware allows a 16x16 embark of 198 z-levels (that's a total of almost 117 million tiles) and upon finally drawing the map after embark was taking up 3.6 gigs of RAM. anything over 10x10 cannot be embarked upon, as soon as it hits about 2 gigs of ram it just crashes. Just to add an update, in 34.11, with no mods and no changes to any settings from download state, this limitation still exists. It certainly worked for Skyrim before Bethesda went and set the flag themselves.Ī program like the CFF Explorer, or the Skyrim/Fallout 3 LAA tools or whatever should be able to do the job. ![]() Should make no difference on a 32-Bit system since it'd take registry changes for windows to actually react to that, but for 64-Bit windows it should then proceed to allow DF up to 4GB of memory. Toady clearly didn't set it, but also didn't do anything to keep the game from hard crashing when it reaches that limit, so it might do fine unless he uses the spare bit in the pointers as a flag. Have you tried setting the LAA Flag on the Dwarf Fortress exe to see if it still behaves and -does- allocate more than 2GB of RAM? I currently do not have a system available to properly test this on myself (my main computer is borked, going to take a while to replace), but for users running DF on 64-Bit windows and 4GB or more of RAM: Still some sort of fail-switch to shut the game down gently if the memory allocation limit is reached would be a nice addition, especially if it came with a warning screen that "By the bye, you're trying to embark on a too large area as I cannot reserve enough memory for it." Making a separate 64-bit version would be sweet and I'd gladly pay good money for it, but I can imagine that the shuffle wouldn't be too straightforward for Toady. Tried it once more to be sure but then df didn't even give me an error. ![]() ![]() I'm running a 64-bit windows 7 with a quad-core and 8 gigs of ram, but as DF hits the 2 gb line it crashes with the following error:Īdditional Information 2:ĕ3ab78575e4e4ce741bf82bee235390bĪdditional Information 4:ēb1c7dab8afb70c763830f7ffc3fdc79 When embarking, crashes when memory use reaches 2GB.Ĭrash upon accepting/saving a generated world when old-version saves are present Crash during huge, lengthy world gen (out-of-memory) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |