zulu9812
The Newbie Nightmare
I should point out that I'm running an Intel Core2Duo 8400 with 8GB of RAM and Win7 x64 - and I still get MAF errors with this mod on Gigantic maps.
any new info on MAF crash?
- Thread starter DrwHem
- Start date
FriskyBuddha
Chieftain
- Joined
- Sep 19, 2006
- Messages
- 93
I switched to windows 7 64 bit and have NO, i repeat NOOOOO, MAF crashes.
I can load, I can regenerate map, everything!
I suggest the upgrade to 64, especially if you already have 4 gig of RAM, b/c 32 bit can only read up to 4 gigs
Hope it helps!
I can load, I can regenerate map, everything!
I suggest the upgrade to 64, especially if you already have 4 gig of RAM, b/c 32 bit can only read up to 4 gigs
Hope it helps!
Use Win 7 64 bit, even if you have just 2 gigs of RAM. I just installed it dual booting with 32 bit and did some tests. Reloading the same two saves yielded following results (of course the saves were from games i couldnt even play any more on 32bit cause it MAF-ed after max 2 turns):
32 bit: MAF after reloading the save game just 1 time
64 bit: got bored after reloading it 10 times
And it definetly isnt just because the other is a "new" OS, cause its eating way more memory while idling in Windows. The important thing is to set the pagefile to at least 3 gigs (constant, non-windows-managed), if you dont do that you'll MAF just as often as with the 32 bit Win 7.
Actually this solution is quite trivial, as under 64 bit you can assign 10 gigs of virtual memory, it sure will be slower than 10 gigs of RAM, but at least you can play games you couldnt before. Also im pretty sure that with using just 2 gigs of ram udner win 7 64 will get you some MAF-s sooner or later aswell, but it seems that cant be avoided, even with 12 gigs of physical memory
32 bit: MAF after reloading the save game just 1 time
64 bit: got bored after reloading it 10 times
And it definetly isnt just because the other is a "new" OS, cause its eating way more memory while idling in Windows. The important thing is to set the pagefile to at least 3 gigs (constant, non-windows-managed), if you dont do that you'll MAF just as often as with the 32 bit Win 7.
Actually this solution is quite trivial, as under 64 bit you can assign 10 gigs of virtual memory, it sure will be slower than 10 gigs of RAM, but at least you can play games you couldnt before. Also im pretty sure that with using just 2 gigs of ram udner win 7 64 will get you some MAF-s sooner or later aswell, but it seems that cant be avoided, even with 12 gigs of physical memory
dudeSDCA
Prince
All,
This topic has been beaten to death on a number of forums. Here's a quick run-down of the facts:
- the /3gb and /userva switches can help for 32-bit windows (version XP, Vista, and 7; although Vista and 7 just need their version of the /userva, which I think it /setuserva); you need to have 4gb RAM or more for these to have a solid effect
- All the memory tricks only address MAF (memory allocation failures) -- these are NOT the only causes of CTDs. Many CTDs come from errors with the mod or components (e.g., something inadvertently divides by 0, or there's a return from a function that's not supported).
- No matter what you do, Civ is a 32-bit process. What does that mean? That means even with all the RAM and virtual memory in the world, the CIV program cannot exceed the application's max memory addressable size (which is between 2-4gb depending on 32 or 64-bit windows, boot options, etc.). I have a Core i7 at 3.8ghz, 12gb RAM, Radeon 3870 win7x64 machine -- while watching the process manager the minute Civ exceeds about 4GB, I get a MAF.
- So what's the solution? You have to make decisions on how you want to use the limited application memory you have. So you can opt for Gigantic map, but you need to either limit the number of civs, or not plan to play a long game (the more buildings you build, the more memory Civ needs; the more civs you have, the more memory it needs; the bigger the map, the more cities, and therefore the more memory you need, and so on...)
- Last -- try out Afforess's mode, a new dawn. I've found it has amazing speed increases and seems to do a better job managing memory. If you're limited in memory, or want to play a huge map with lots of civs, just install the lite option so you get the optimizations without a lot of extra buildings...
This topic has been beaten to death on a number of forums. Here's a quick run-down of the facts:
- the /3gb and /userva switches can help for 32-bit windows (version XP, Vista, and 7; although Vista and 7 just need their version of the /userva, which I think it /setuserva); you need to have 4gb RAM or more for these to have a solid effect
- All the memory tricks only address MAF (memory allocation failures) -- these are NOT the only causes of CTDs. Many CTDs come from errors with the mod or components (e.g., something inadvertently divides by 0, or there's a return from a function that's not supported).
- No matter what you do, Civ is a 32-bit process. What does that mean? That means even with all the RAM and virtual memory in the world, the CIV program cannot exceed the application's max memory addressable size (which is between 2-4gb depending on 32 or 64-bit windows, boot options, etc.). I have a Core i7 at 3.8ghz, 12gb RAM, Radeon 3870 win7x64 machine -- while watching the process manager the minute Civ exceeds about 4GB, I get a MAF.
- So what's the solution? You have to make decisions on how you want to use the limited application memory you have. So you can opt for Gigantic map, but you need to either limit the number of civs, or not plan to play a long game (the more buildings you build, the more memory Civ needs; the more civs you have, the more memory it needs; the bigger the map, the more cities, and therefore the more memory you need, and so on...)
- Last -- try out Afforess's mode, a new dawn. I've found it has amazing speed increases and seems to do a better job managing memory. If you're limited in memory, or want to play a huge map with lots of civs, just install the lite option so you get the optimizations without a lot of extra buildings...
