Nathan has updated the memory problems in the windows version of 2.47, which were causing Blender to crash whenever memory requirements are high. The updated version is now available for download.
"The original release files were accidently built without LARGEADDRESSAWARE support. They have now been updated on September, 19th 2008. Click here for the checksums of the new binaries."
You can find the download here on blender.org.
20 Comments
Good. :) Thanks, Nathan! Good work.
-b
http://artislight.deviantart.com/art/Vigil-98645384
not that i use windows much for blender(OSX here), but thanks for the release of the fix... cant wait for some of those new tasty bits added to the trunk to be released in an official build...
*Nathan has updated the memory problems in the windows version of 2.47*
Woohoo! I was wondering when the memory problems would be brought up to today's demands in the competitive field of memory problems! I was actually considering a move to 3DS Max, since their memory problems are more full featured, according to an article in last month's Memory Problems Today magazine!
(LOL I need sleep)
I hope the dev team is aware that, unless the Windows running the program has the /3GB switch in the Boot.ini config file, the program will still only use 2Gb so, whatever the problem may be here, it will still happen.
For the record, the default XP setup does _NOT_ have /3GB set, nor is it advisable to have it (because it limits the OS to only ever use 1Gb).
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
2.495 ?
thanks Nathan,
LARGEADDRESSAWARE !
I think i had learn something new today!
Google it and reading about it now.
@Miguel Melo, thanks for the link.
How is (Nathan)?
Thanks a lot !
I had used a non official LAA build, but it didn't render material offset...
I was wondering if this feature would be included in v2.50...
and that's it, The dev Team has done it !
I haven't seen an issue (so far) with Blender,but I'm running it on 64-bit Vista.
Anyone know if I need this version?
Take care with the /3GB parameter in your boot.ini.
Use it only if you really need more than 2GB in blender.
One border side effect is that your registry system is limited to 12.5MB(on WXP). So if you have many devices you can have strange problems...
A patch exist but only for Windows Server.
Some instability could also happen (network slow down...) so tweak as closest as your needs with parameter /3GB /USERVA=2900. (In this case you can reserve 2.9GB instead 3Gb, the 100MB is free for the system)
very interesting information about the 2gb or 3gb options in WindowsXP. Thanks everyone for the info!
The .zipped Version is _exactly_ the same as the one I got a month ago (even the archive file itself is identical), except it has just been renamed to ...-law.zip. (I don't have the previous installer version to compare these)
Since I don't assume that just renaming will magically result in different memory behaviour, can someone check this ? Or should I assume that the zipped version from a month ago already had the fixes applied ?
Confirmed - zips are the same and WITHOUT LAA flag.
Exe-installer blender-2.47-windows-law.exe HAS LAA flag in blender.exe and blenderplayer.exe so everyone with problem above 2Gig can download it ( http://download.blender.org/release/Blender2.47/ ) and extract with 7zip if don't like exe-installer - until zip come correct.
Hooray, LARGEADDRESSAWARE. Back to work...
WOOHOO!!!
Finally.
Just when I was getting severe problems as well.
Does anyone know if this will fix the issues with the fluid sim? I have a massive scale flood animation that continually uses up all my memory then crashes.
Will this patch fix those issues? Or at least help?
Thanks Nathan! You rock!
hope this come patch in future release.
Great tip Miguel Melo.
You won't beleive how happy I am to hear about this. I was starting to get really irritated about the consistent crashes as I worked with some of my more complicated projects.
NathanKP - Inkweaver Review
particles kept on overunning the buffer for me (eg: it ran out of memory) and crashing.
hopefully this fixes it? :D
cool, thanks coders!
I think you forgot to put some of the standard scripts into the release. Is that possible? I miss smart unwrap etc..
whoops, i just saw that it might be my mistake, since i extracted the files from the exe directly, which might have caused the error. sorry for the confusion. forget what i said