Thu, Nov 28, 1:54 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 28 11:20 am)



Subject: Reality 3 + Poser Pro 2012 32 Bit = good or bad?


Meshbox ( ) posted Tue, 23 April 2013 at 1:52 AM · edited Mon, 25 November 2024 at 5:43 PM

I normally would conclude that 64 bit versions are a better option, but is trying to run the combo under 32 bit just a pipe dream?

Best regards,

chikako
Meshbox Design | 3D Models You Want





hornet3d ( ) posted Tue, 23 April 2013 at 4:48 AM

Quote - I normally would conclude that 64 bit versions are a better option, but is trying to run the combo under 32 bit just a pipe dream?

 

As there is a 32bit version I doubt it is a pipe dream and from the threads here and at RDNA there are people using it with 32bit.  The biggest benefit of 64bit programs, for Windows at least, is that it does not have the limitation of the amount of memory it can address that 32 bit has.  On Windows 7 the starter and home versions, I think, are limited to 16gig while Premium and Ultimate can address 192Gig.  So even the cheaper versions can address far more than 32bit.  How hard Luxrender uses memory I am not sure but, the use on my machine has not been high so far but then my scenes have been fairly simple as I try and understand what Luxrender is capable of.

I am sure someone will add their experiences of Reality in a 32bit environment to this thread with  but if they do have it working well I can highly recommend the use of the Reality +Luxrender combination.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.


LaurieA ( ) posted Tue, 23 April 2013 at 9:36 AM · edited Tue, 23 April 2013 at 9:38 AM

You'll never be able to access anymore than 3gb of ram and that may make it take too long to be worth your while. You will have to decide if you really want to wait that long for a render :). I have a quad core and six gigs of ram on a 64 bit system and it takes a good long time for Luxrender to finish a render. I don't mind it tho....overnight is usually more than sufficient in most cases ;).

Laurie



WandW ( ) posted Tue, 23 April 2013 at 10:14 AM

I have a simple 1387x862 scene cranking away in LUX and it's using 840-900 MB of RAM...

----------------------------------------------------------------------------------------

The Wisdom of bagginsbill:

"Oh - the manual says that? I have never read the manual - this must be why."
“I could buy better software, but then I'd have to be an artist and what's the point of that?"
"The [R'osity Forum Search] 'Default' label should actually say 'Don't Find What I'm Looking For'".
bagginsbill's Free Stuff... https://web.archive.org/web/20201010171535/https://sites.google.com/site/bagginsbill/Home


bagoas ( ) posted Tue, 23 April 2013 at 12:06 PM

For me it works. Pro 2012, Reality 3 and Lux, all on an Athlon 64X2 running WinXP Pro 32 bits. Not a miracle of speed, but stable and good enough to see where results it goes as far as light and tone are concerned. Then if it looks good I close lux, and transfer to another (Unix) machine on which I have not Poser/reality of course, but 64 bit Lux and much much more capacity.  


vitachick ( ) posted Wed, 24 April 2013 at 5:02 AM

I run Win XP myself. Yes a bit slower but it gets the job done..

Win10  Poser 2014/Poser 11 Daz3D


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.