Thu, Nov 14, 10:55 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 14 10:48 am)



Subject: P6 SR1 updater is available now


  • 1
  • 2
XENOPHONZ ( ) posted Thu, 26 May 2005 at 5:31 PM

PS Sorry. I'm not sounding off at you

neotekian --

If I understood correctly, then I believe that mac was referring to me, and not to krazik. In other words, mac was assuring me that his comments were not pointed in my direction.

IMO -- a little bit of a snappy response from someone who's not normally a PR-type......shouldn't create a major crisis.

We ought to give him some slack, and let it go down......

It's like a thrown pebble starting a war.

Gotta go. I'm supposed to be eating at a nice restaurant tonight.

I suggest doing the same to others.

;)

Something To Do At 3:00AM 



maclean ( ) posted Thu, 26 May 2005 at 5:33 PM

'PS Sorry. I'm not sounding off at you' neotekian, That postscript was to xenophonz. I was partly answering his post, so I wanted to making it clear that I wasn't mad at him. Yes, my use of F-words may have been uncalled for, I agree. But my response was dictated by my annoyance at krazik. If he's a CL employee, he should know better than any of us what piracy, phishing and other scams can do to a software manufacturer. My tone may have been excessive, but I think his sniping was totally unprofessional. I expect more from the people I give my hard-earned money to. If I treated my customers like that, I wouldn't get many return sales. And if you don't see anything wrong with telling a customer, whom you know is having problems, that you could help, but you're not going to, then I think we disagree about how customers should be treated. mac


neotekian ( ) posted Thu, 26 May 2005 at 5:37 PM

LOL yea that bit about "but I'm not going to" was not on par. Ok well let's just hope someone else from EF like CL-Steve will come in here and clear it all up soon. By the way, I have Poser 5 - do you guys feel it is worth upgrading to Poser 6 now with the SR1 if what I mostly do are still scenes that I later export to 3D Max as OBJ files?


maclean ( ) posted Thu, 26 May 2005 at 5:38 PM

xenophonz, I just saw your post. OK. I apologise to krazik if I've offended him. I don't normally snap at people like that. I was a bit angry at being told that I should know who he is and what he does. I've never heard of him before, so I was naturally suspicious. Honestly, would you all IM him your serial numbers? mac


maclean ( ) posted Thu, 26 May 2005 at 5:46 PM

hi neotekian, I've had every poser since P2, and I'd definitely say P6 is the best poser yet. I hated P5. It was (and still is) pretty cranky on my machine. Although, I will say this. P5 is as stable as a rock (after SR4), but P6 has cured a lot of the weird glitches, and it has a lot of new features that make it really usable and interesting. Mind you, if you're exporting to max, I'm not sure how much you'd benefit. But for working within poser, P6 can't be beat. mac


Casette ( ) posted Thu, 26 May 2005 at 10:55 PM

Folks, you bored me with stupid discussions. IM yes, IM not ... if you are inside internet, you know the game and play the game. And if anybody fake a CL/EF identity I doubt that he/she would post many posts without a mod action This is a nonsense. The important topic is the SR1. And I have found that Old Memory Bug is still there. Hide, but there. Probably the SR1 have increased the render limits, but the hellish "you havent sufficient memory blahblah" window appeared again. And again I need disable the texture filtering or set a lower texture size... the same old story. And this isnt a theatre full of unimesh people with dynamic wigs. Mayadoll V3 with a texture, Mike3 with a texture, a DM free temple and a dynamic cloth square. Nothing too much difficult. But ... THE BUG again Shit :(


CASETTE
=======
"Poser isn't a SOFTWARE... it's a RELIGION!"


Khai ( ) posted Thu, 26 May 2005 at 11:24 PM

"The settings labeled as final are very aggressive in terms of resource needs. It is possible that at such render settings, a complex scene consumes more memory than an application can use on a 32 bit Windows system (2 gigabytes)." Bingo. exactly what I was saying. thanks for the confirmation there.


Casette ( ) posted Thu, 26 May 2005 at 11:42 PM

Fantastic. So I need a 2 Gb RAM to working 100% with Poser6. And if my motherboard dont allow more than 1 Gb RAM Im pissed Soon a nice add at the EF site with the message: " ... and REMEMBER that for ENJOY all the NEW FEATURES of Poser6 you PROBABLY need TO BUY a NEW computer!!!" I hadnt uninstalled my Poser5. I was waiting the end of the memory bug to it. Obviously, Im still waiting ... Hey, whats about a SR2? :(


CASETTE
=======
"Poser isn't a SOFTWARE... it's a RELIGION!"


Casette ( ) posted Thu, 26 May 2005 at 11:48 PM

No more 12 years old scottish for them. Only coffee made with washing-floors-dirty-water for them. And without filtering it :(


CASETTE
=======
"Poser isn't a SOFTWARE... it's a RELIGION!"


JamesRoden ( ) posted Thu, 26 May 2005 at 11:48 PM · edited Thu, 26 May 2005 at 11:53 PM

I concur with Casette here...the memory bug is here and is even active when trying to use the Poser 4 render engine from within Poser 6. Using all the "new features". Heh, right now I am having difficulty using some of the old.

I am considering strongly stepping up to 2 gigs of ram from the 1 gig that I have now...but what if that still doesn't solve the problem?

Sigh...

Message edited on: 05/26/2005 23:53

Requiem "...angels fall from grace, and sometimes heroes die."
Tunnelrunners --The Complete Archive


Khai ( ) posted Thu, 26 May 2005 at 11:49 PM

" Fantastic. So I need a 2 Gb RAM to working 100% with Poser6. And if my motherboard dont allow more than 1 Gb RAM Im pissed" erm no. you can reach 2GB right now. the Limit mentioned is Phyisical RAM + Virtual = Windows Total Ram. if your MB has 1GB and you set your Virtual to 1GB you'll have 2GB of RAM for a program.


XENOPHONZ ( ) posted Fri, 27 May 2005 at 12:39 AM

Don't know, guys.

With SR1, it's working great for me -- so far.

But, as already mentioned -- that's with 2G of physical memory. Not just virtual memory.

Something To Do At 3:00AM 



Casette ( ) posted Fri, 27 May 2005 at 4:34 AM

Okay. This afternoon at home Ill try to update the virtual memory to fix the bug. But my hamster is horrorifyed ... I promised that if SR1 didnt work I would eat him ...


CASETTE
=======
"Poser isn't a SOFTWARE... it's a RELIGION!"


Gareee ( ) posted Fri, 27 May 2005 at 6:12 AM

The bottom line for all of this might just be if you want more state of the art rendering ability, that you'll need to upgrade. That's no different then all the new games that come out every year, or many 3d applications. Yeah, they'll work with less, but they are designed to push tech to it's limits. And I'd much rather have the option to have lots of bells and whistles and the ability to upgrade to them easily, then not have them at all. I've read many MANY times of people using Lightwave, Max, Maya and Vue running 2-4 Gig or ram. And when you really push hard with large photoshop images, lots of ram is a must have. I've only got 1 gig here, and I've been trying to decide if it's ime to upgrade my system (2.5 yrs old), or if more ram will be enough to keep me happy with it another year.

Way too many people take way too many things way too seriously.


uli_k ( ) posted Fri, 27 May 2005 at 12:35 PM · edited Fri, 27 May 2005 at 12:36 PM

Hi all,

some more detail on the "memory bug" issue: when I was referring to the 2 gig limit, I meant the maximum amount of virtual & physical memory that a process can allocate on a 32 bit Windows system. You don't have to have 2 gigs of physical RAM for Poser to use 2 gigs of RAM. Setting your virtual memory to system managed while having sufficient hard drive space will do (I run 1 gig of physical RAM).
That said, if you do very heavy renders on a regular basis, 2 gigs of physical RAM will be help, because access to virtual memory is slow and it is not guaranteed that Windows will give the memory requested to an application when all physical is maxed out.
If Poser is denied more memory by the operating system, it will present the error message that I think some people call "the memory bug". I personally wouldn't call it a bug, since the alternative to presenting the error message and stopping the render would be freezing or crashing.
If you want to know for sure whether or not you're trying to render a heavy scene, you can flip a little switch in Runtime/prefs/Poser.ini. Changing 'WRITE_MEMORY_LOG 0' to 'WRITE_MEMORY_LOG 1' will make Poser 6 SR1 leave a log file behind in the location where it is installed (i.e. where the 'Runtime' folder is located). The log file will present you a detailed listing of memory available at the start of a render and how much memory is needed for loading textures.

Uli

P.S.: XENOPHONZ, yes, I work for e frontier. Sorry for camouflaging.

Message edited on: 05/27/2005 12:36


XENOPHONZ ( ) posted Fri, 27 May 2005 at 5:05 PM

XENOPHONZ, yes, I work for e frontier. Sorry for camouflaging.

Your posts contain very helpful information. Thank you.

And, no -- I didn't think that you were "camouflaging".

But you spoke with a certain amount of authority -- i.e. - you sounded like you knew what you were talking about.

Therefore I concluded that you worked for CL.....uh, I meant to say EF.

Thanks!

;)

Something To Do At 3:00AM 



neotekian ( ) posted Fri, 27 May 2005 at 7:10 PM

Just a quick follow up -- I went ahead and upgraded to Poser 6 and I must say it really is a huge improvement over Poser 5 on my system. Thanks for the advice earlier people!


Casette ( ) posted Tue, 31 May 2005 at 7:47 AM

Thanks for the last tip, Uli. Ill try it :)


CASETTE
=======
"Poser isn't a SOFTWARE... it's a RELIGION!"


  • 1
  • 2

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.