donquixote opened this issue on Apr 14, 2005 ยท 74 posts
donquixote posted Thu, 14 April 2005 at 11:14 AM
1.) Where the %&^ is P6 SR1? Except for the major memory problem and a couple of other minor glitches, Poser6 is so almost there. It is SO FRUSTRATING having it crash all the time. 2.) Who are all these folks who say Poser 6 works perfectly on their system? Are they CL stockholders? Or ... ? 3.) And why, really, is Blackhearted holding his head in the MOTM photo? A), He is suffering for his art?; B), His brain is so big he has to keep constant pressure on his skull to keep everything in place?; C), The photographer simply thought it looked Cool?; D), I know, but I'll never tell.
thixen posted Thu, 14 April 2005 at 11:24 AM
3)it's either that a) years ago he accidently superglued his hand to his head and was too embarassed to get it taken care of or b) because he is going bald and doesn't want anyone to know. am I close?
nickedshield posted Thu, 14 April 2005 at 11:32 AM
I must remember to remember what it was I had to remember.
XENOPHONZ posted Thu, 14 April 2005 at 11:46 AM
Except for the major memory problem and a couple of other minor glitches, Poser6 is so almost there. Yep.
donquixote posted Thu, 14 April 2005 at 11:46 AM
donquixote posted Thu, 14 April 2005 at 11:49 AM
XENOPHONZ, Poser 6 is such a pleasure to use, or it would be. That's why I find it so frustrating.
hpdrag posted Thu, 14 April 2005 at 11:53 AM
I have critized P6 rather hardly in former posts, but meanwhile i like it more and more, even if the bugs are still there. But i have rather complicated scenes, a lot of figures, background stuff, lights, and i think that people who are doing more portrait- and single figure pictures will rarely run into the memory bug. Furthermore it seems to me, that P6 works much better with scenes build up from the scratch in P6, but with scenes imported from P5. Another point: to work with P5 and P6 without too much frustration you should carefully read the manual-chapter or tutorials about the render-settings. Things like the 'minimum shader rate', 'pixel-samples' and so on have an enourmous effects on quality, speed an stability of the firefly-renderer. And there is a third thing: many characters like V3 use rather dirty tricks to 'abuse' the poser-data-structure in a way, that most likely wasn't planned from the developpers (or maybe planned, but then stopped, because they recognized that alle those inner morph-chains were too buggy). It must be a hell for the programmers to look for bugs in structures, that they would like to throw to the garbage, only to keep the very popular products from a competitor alive ;-)
XENOPHONZ posted Thu, 14 April 2005 at 11:56 AM
claiming that someone has had no trouble with Poser 6), I'm rather flabbergasted. How can that be?
A couple of likely reasons.
One reason being that many people never attempt to push Poser very far beyond the basics. The memory issue is probably either rarely or never going to affect them.
Another reason derives from.....as indicated in the header of this thread........the mystery of myriad PC hardware/software combinations. Different systems might achieve distinctly different results -- results affected by a set of factors that no one can account for 100%.
A problem comes in when certain individuals that aren't experiencing the bug themselves act all self-righteous about the issue:
"Well......I'm running Poser 6 on a 20-year-old Tandy.....and I'm not having any problems. Must be something wrong with you..........."
I just want CL to get out the fix. Then we'll have it.
blaufeld posted Thu, 14 April 2005 at 11:56 AM
Well, I AM one without P6 problems so far... My PC is only an AMD Athlon XP 2500+, 1Gig ram, Radeon 9800 Pro graphic card, so it's clear I'm NOT a CL stockholder (I would like it...). For now, I find P6 much more responsive that P5, expecially when I choose to end prematurely a render - it has not shown the annoying habit of lock up the prog if I hit the "Cancel" button... :P
XENOPHONZ posted Thu, 14 April 2005 at 11:59 AM
XENOPHONZ, Poser 6 is such a pleasure to use, or it would be. That's why I find it so frustrating.
I agree with you totally.
I've stated as much myself in several threads on the subject.
The GREAT potential of what P6 could be.......with just a little more help in the memory management department........
XENOPHONZ posted Thu, 14 April 2005 at 12:07 PM
I have critized P6 rather hardly in former posts, but meanwhile i like it more and more, even if the bugs are still there. Same here. And that's the inherent contradiction of P6. The aggravating combination of joy and annoyance. Love the program.......hate the memory bug.
aeilkema posted Thu, 14 April 2005 at 12:09 PM
Got no problems either, unless I do a huge scene, then the rendering bug shows up. Got an AMD Athlon XP 2400+, 1Gb ram, Radeon 9600 Pro graphic card. I'm no CL stockholder either, but I do love P6 and I'm very happy with it and don't find it frustrating at all. I wouldn't be suprised if the major problems are with people using high end systems.
Artwork and 3DToons items, create the perfect place for you toon and other figures!
http://www.renderosity.com/mod/bcs/index.php?vendor=23722
Due to the childish TOS changes, I'm not allowed to link to my other products outside of Rendo anymore :(
Food for thought.....
https://www.youtube.com/watch?v=pYZw0dfLmLk
Tyger_purr posted Thu, 14 April 2005 at 12:12 PM
My Homepage - Free stuff and Galleries
XENOPHONZ posted Thu, 14 April 2005 at 12:18 PM
read the responses above and there are others with only 1Gig and no reported problems. It's worse with less memory. Currently, I've upgraded to 1.5G. I'll be jumping it up to 2G in a week or two.
XENOPHONZ posted Thu, 14 April 2005 at 12:22 PM
It's obvious that enough people are experiencing this difficulty to acknowledge it as a genuine problem. It's not a figment of our imagination. Curious Labs has admitted that it's there. If you aren't having this trouble, then that's great. But many of us are.
dialyn posted Thu, 14 April 2005 at 12:23 PM
Well, for me, Poser 6 works better out of the box than Poser 5 did. I got the "out of memory" error once, when I had been rendering one character over and over for about an hour (for reasons not related to Poser 6). I would have gotten the same error in Poser 5 had I been doing the same thing. My problem is that I need to sit down and figure out what everything does. There is enough new that I find some things quite confusing. No problems with the new hair (I never got dynamic hair to render in Poser 5 - froze the program every time so I gave up on it) or the cloth room (fingers crossed). I'm not excited about Jessi who just seems like another model wanna be, but the guy is pretty hunky. I'm seriously thinking of removing Poser 5 from my computer system and keeping Poser 4 (because of Vicky and her breathern) and Poser 6.
But I understand everyone is having a different experience. It was the same with Poser 5.
Message edited on: 04/14/2005 12:25
XENOPHONZ posted Thu, 14 April 2005 at 12:28 PM
I'll be jumping it up to 2G in a week or two. Maybe then I'll be able to render a couple of scenes that are currently sitting on my hard drive -- unable to be rendered because of the memory bug.
Kristta posted Thu, 14 April 2005 at 12:30 PM
Out of Mem error just once with one sided square, custom created texture for that square, SP3 from Daz, Ivey texture for SP3, Eastern Mil Dragon 2, Eastern Jewels for the EMD2, 4 custom spotlights. The file did not corrupt. Changed bucket size from 64 to 50, rendered file in about 50 seconds. I've made quite a few changes to the file and have not encountered the Out of Mem error again. AMD 3000+, Win2000, 512MB RAM, ATI Radeon 9600 Pro 256MB video card. I'm not a stockholder.
thixen posted Thu, 14 April 2005 at 12:37 PM
this did bring up an interesting peice of information though. The 2 times that I got the Memory bug (and I have 1gb ram BTW so it's not just the 2gb people) I was rendering a p5 scene that I deleted out a light dome and added a IBL AO light. After 2 attempts I gave up. Since then I've only rendered scenes that I've built from the ground up in P6. I wonder if anyone else has noticed something simular, or is it just a coincidence?
nickedshield posted Thu, 14 April 2005 at 12:39 PM
Jumping back in with a few questions: I don't know if this makes any difference or not but before installing P6 I was reading other threads about P5 issues and how it's best to make it happy by installing to it's own hard drive. Since I blew out my secondary drive I just waited for the new one. I don't know if not installing the complete package has any bearing. I did not install the Legacy stuff or the non-nude stuff. Yes I have run into the memory bug on a very complex scene but by following the suggestions on the error splash screen I was able to complete the render by changing some settings. I agree with XENOPHONZ that a memory fix would be most welcome. Then I could set up the scene, select my rendering options without worrying whether it will crash or not.
I must remember to remember what it was I had to remember.
steerpike posted Thu, 14 April 2005 at 12:46 PM
"Well......I'm running Poser 6 on a 20-year-old Tandy.....and I'm not having any problems. Must be something wrong with you..........."
Piffle! It's running on a ZX-81 here; sweet as a nut.
Tirjasdyn posted Thu, 14 April 2005 at 12:46 PM
Attached Link: http://fnproductions.net/graphics/tutorial/poser6/
Some tips on avoiding the memory bug for now.
thefixer posted Thu, 14 April 2005 at 12:59 PM
Thixen, I recently took one of my old P5 images and deleted all the lights and replaced them with 3 point lights in P6. Worked great. That said P6 runs like a pig most of the time! It works fine with 1 V3 a couple of props and 3 or 4 lights, which is pants to me because I usually like 3 figures usually in my scenes. System: Pentium 4, 3.4 Ghz HT, 1 Gig of RAM and a 256 Meg ATI Radeon X600 graphics card. thefixer poser coordinator
Injustice will be avenged.
Cofiwch Dryweryn.
Rance01 posted Thu, 14 April 2005 at 1:16 PM
No major problems here and NO memory problems at all. I have done a couple of big scenes and have used some of the newer functions Ambient Occlusion, etc. Pentium 4/2.8 GHz 2.0 GB DDR SDRAM 128 MB NVIDA GeForce FX Go5700 Poser 6 seems to run as good or better than P5 for me on this machine -- hp PAvilion Notebook. Best Wishes, Rance
XENOPHONZ posted Thu, 14 April 2005 at 1:22 PM
My repeated posts on this subject have three objectives:
I've stated this little history before, and I'll repeat myself again in this thread (it bears repeating):
Over the last years, I have mentioned a few things here and there about P5's rendering problems. Ultimately, I was forced to do all of my rendering in Vue. Because P5 just couldn't do the job.
So.......P6 comes along. Hurray! Now I can render my scenes natively in Poser........
This issue has been brewing for a long time.
They need to fix it.
jjsemp posted Thu, 14 April 2005 at 1:54 PM
One would have to assume that they know that and are working on it. Yelling at them won't make it get here any faster.
XENOPHONZ posted Thu, 14 April 2005 at 2:08 PM
One would have to assume that they know that and are working on it.
Yes, one would have to assume this. Especially as they've indicated that it's so.
Yelling at them won't make it get here any faster.
You are right -- it won't.
That's why I'm not yelling. I can't speak for others in this -- but I can speak for myself.
What I am doing is engaging in a reasonable disscussion about a very real issue. Not the faked-up problem that some seem to think that it is.
If the problem doesn't get talked about, then it's likely to be ignored.
Which would be just dandy for some of those individuals who aren't personally experiencing the pleasure of the memory bug. At least, those individuals with an utterly inexplicable attitude towards those of us that are.
When the memory bug goes away, then I'll praise CL for their good work. Just as they already deserve praise for about 95% of what they've done with P6.
Once the memory bug is gone, then it'll go up to 99% - 100%. In the meantime, the issue isn't going to go away.
yp6 posted Thu, 14 April 2005 at 2:12 PM
One would have to assume that they know that and are working on it. Yelling at them won't make it get here any faster. Unless it'll cost them income, they have no reason to fix it. Hasn't this same glitch been around since P5?
XENOPHONZ posted Thu, 14 April 2005 at 2:20 PM
BTW -- I have no desire to join the ranks of the chronic Curious Labs bashers. Nor will I. But one cannot ignore crashed renders and courrupted files. It's not my idea of fun.
thixen posted Thu, 14 April 2005 at 2:31 PM
"Unless it'll cost them income, they have no reason to fix it. Hasn't this same glitch been around since P5? "
It's more prominate in P6, and it's already costing them income in the fact that there are a lot of people who would of upgraded, but haven't yet because of this ohh I just wanted to add that I do have pretty good faith in CL's ability to fix this, and I think by doing so P6 will probably be the first Poser that can compete in the professional dept seriously and not just lie on the fringe.
Message edited on: 04/14/2005 14:35
dialyn posted Thu, 14 April 2005 at 2:33 PM
What makes a problem more challenging to solve is when it occurs with irregularity and inconsistency. I am not saying the problem doesn't exist. This isn't an all or nothing kind of thing. But why it exists at varying levels on similar equipment makes it difficult to create a uniform solution. Or I would think so. I was not posting my experience to say that any of you didn't have the experience you did. As with Poser 5, the program seems to work differently from person to person, and it doesn't seemed particularly to matter if one is experienced or a novice, with new and high end equipment or older models. That is what is interesting to me. But it must be frustrating for those looking for fixes.
yp6 posted Thu, 14 April 2005 at 2:41 PM
It's more prominate in P6, and it's already costing them income in the fact that there are a lot of people who would of upgraded, but haven't yet because of this Some of us had the silly idea that after all the problems with P5, CL would make more of an effort with P6. I suspect they made quite a few sales of P6. (A lot more than they deserved.)
Tyger_purr posted Thu, 14 April 2005 at 2:45 PM
Curious Labs must have some clue as to what is going on. They are the ones who announce that the problem existed. And as i recall they anounced that they had identified a memory problem, after they had given the go-ahead to make the "final" CDs. so when they said go, they believed that what they were releasing had no significant errors/bugs.
My Homepage - Free stuff and Galleries
XENOPHONZ posted Thu, 14 April 2005 at 2:48 PM
But it must be frustrating for those looking for fixes.
Yes, it is frustrating.
I didn't get from your post that you in particular were holding out an attitude towards those of us with the memory-usage problem......that is to say: those of us that dare to talk about it.
Unfortunately, some others do seem to have such an attitude.
Once we get past that little bump, then we can -- as you say -- begin to discuss solutions.
sigh
At the moment, the only "official" work-arounds are:
If anyone can add to this list -- it would be appreciated.
mylemonblue posted Thu, 14 April 2005 at 3:07 PM
yp6 I agree with you.
My brain is just a toy box filled with weird things
hpdrag posted Thu, 14 April 2005 at 3:10 PM
You'd better do: 'SaveAs & Exit', if you don't want to loose your work ;-)
XENOPHONZ posted Thu, 14 April 2005 at 3:21 PM
You'd better do: 'SaveAs & Exit'
Yep. Over & over again.
The process makes for a very efficient workflow.
;-)
Lawndart posted Thu, 14 April 2005 at 3:24 PM
yp6 posted Thu, 14 April 2005 at 3:27 PM
Curious Labs must have some clue as to what is going on. They are the ones who announce that the problem existed. And as i recall they anounced that they had identified a memory problem, after they had given the go-ahead to make the "final" CDs. IIRC, it was the bad character joint setup they knew about after they started printing CD's but before everything was shipped (though they didn't bother to mention it until users started pointing it out.) Of course, no problem! Just sign up for Content Paradox and we'll get you the fix as soon as you wade through all the advertising and put your serial number in a few times! (People resented it the first time, well you have to sign up now if you want your product to work right!)
Lawndart posted Thu, 14 April 2005 at 3:31 PM
FYI: Curious Labs loves you. They would never hurt you on purpose. :) BTW: There are plenty of people out there that won't upgrade to P6 because insert excuse. If it wasn't the memory bug it would be something else. It's unfortunate for them. They are missing out on all the fun. ;) Boy, I feel fiesty today. LOL...
yp6 posted Thu, 14 April 2005 at 3:42 PM
to know if recent download purchasers (since the character joint fix was released) still had to go to CP for the fix. If they didn't, that would indicate the bogus Jesse joints weren't a marketing ploy to force people to sign up for CP...
JohnRickardJR posted Thu, 14 April 2005 at 3:44 PM
The content updater (the full one) has now appeared on the Curious Labs website. Seems like they just take a little longer to change things there (took a couple of weeks before Poser 6 was added to the register list for me)
XENOPHONZ posted Thu, 14 April 2005 at 3:50 PM
Boy, I feel fiesty today. LOL...
You? What's the world coming to........?
They are missing out on all the fun. ;)
I've already said this elsewhere, but I need to say it again here:
P6 -- even with the memory bug -- is worth.....no, MORE than worth.......it's price.
Buy it, or completely miss the boat.
I can't stress the good points of P6 enough. They are wonderful.
But this wonderful program is dragged down by a flaw at the end.
Get rid of that, and you've got what Poser should be.
yp6 posted Thu, 14 April 2005 at 4:01 PM
The content updater (the full one) has now appeared on the Curious Labs website. Seems like they just take a little longer to change things there (took a couple of weeks before Poser 6 was added to the register list for me) The link takes you to Content Paradise...
thixen posted Thu, 14 April 2005 at 4:02 PM
personally I think it's a Beer and stale popcorn nazi conspiracy to me. What-cha thinl Xeno is it the Nazis ?? :D :p
STORM3 posted Thu, 14 April 2005 at 4:03 PM
Everyone suffers from the memory leak bug, some just don't use the program in a way that exposes it frequently or have systems that are more robust in dealing with it. But it exists and until it is fixed it is a major impediment to doing anything serious with P6.
CL may have released a less buggy version in P6 than they did in P5, but they still risk being tarred with the same brush unless they fix this problem soon. At the end of the day, the customer will not forgive them if the problems still persist in a few weeks time, particularly as CL knew about the bugs when releasing P6. That fact will come back to haunt them unless they fix the problems soon.
Frequent information updates from CL as regards progress of the fix will re-assure customers. Silence will only increase the speculation and anger.
XENOPHONZ posted Thu, 14 April 2005 at 4:09 PM
personally I think it's a Beer and stale popcorn nazi conspiracy to me. What-cha thinl Xeno is it the Nazis ?? Nahhhh. This has nothing to do with the TOS. So it's unlikely to involve Nazis.
Kristta posted Thu, 14 April 2005 at 4:12 PM
Just out of curiosity, has any one sent bug reports to CL when they've encountered the memory bug? They can produce a fix faster if they know what systems, what hardware, what the scene consists of, etc. When programming for AutoCAD a couple years ago, we'd get reports of "a button doesn't work". That's great, considering we'd made about 120 buttons and no one reported which one was working, it didn't do us a lot of good. The more they know, the easier it will be to fix.
JohnRickardJR posted Thu, 14 April 2005 at 4:13 PM
I noticed where the CL link took you too late to stop the post, and couldn't find this threat again, but then I often loose the thread
jjsemp posted Thu, 14 April 2005 at 4:17 PM
"That's why I'm not yelling. I can't speak for others in this -- but I can speak for myself. What I am doing is engaging in a reasonable disscussion about a very real issue. Not the faked-up problem that some seem to think that it is. If the problem doesn't get talked about, then it's likely to be ignored." ____________________________________________________ "Yelling" is when you put things in caps or in bold letters, which you did. I don't think anybody thinks that this is "faked up problem". I can't recall a single person accusing anybody of complaining without just cause. Furthermore, nobody's ignoring this problem. But the memory problem has been talked about to death, this thread adds nothing new to the discussion, and more complaining isn't really going to help. I think there's a point at which complaining becomes counter-productive. It reaches its saturation point and there really isn't anything NEW to be said. And, not that you're one of them, but I am tired of hearing from people who have an axe to grind against CL and want to proudly proclaim that they're glad THEY didn't upgrade to P6 because (fill in the blanks). Who cares? I said this back in the middle of the Poser 5 brouhaha and I'll say it again today. This is a ridiculously cheap, amazingly powerful little piece of software that's being held together by spit and glue. But the company has never abandoned it. They've managed to find a way to keep it going, and we have to have a little patience and faith, and give them our support. If you want a higher order of perfection and sophistication for two-hundred bucks (or less), you're not living in the real world. There isn't even one piece of software that does this same kind of stuff for the same price. As of this writing, Daz Studio does NOT do animation. And I've been using Hash Animator since back in the old Amiga days, and it's always been as buggy as the jungles of the Amazon on a hot day. Really, if you want a smoother ride, go pay more and get Softimage. And in the spirit of contributing something USEFUL to the discussion, I haven't seen anybody mention this, but the corrupted file-saving aspect of the memory problem seems to be somewhat tamed by dropping your display down from 32 bit to 16 bit, or at least it has helped on my system. Your mileage may vary. -jjsemp (who's REALLY feeling fiesty today).
Tucan-Tiki posted Thu, 14 April 2005 at 4:18 PM
why do peploe defend a badly constructed program ? 1. get rid of content paradise it's offensive to have it shoved on you rather then have a choice to not want it. 2. poser6 is not much more then poser 5 very disapointed by that and the memory bug curious labs knew about but rushed to sell the product anyway before fixing it. 3. 6 I don't use because it's real slow or it gives an annoying memory error, whatever happened to speed? Another thing why can't they make this program access multiple runtimes?
aeilkema posted Thu, 14 April 2005 at 4:21 PM
"But it exists and until it is fixed it is a major impediment to doing anything serious with P6." That to me sounds like exaggerating the whole problem. By now I've created a full comic in P6 (it's on it's way way to the printer as we speak for a first series of 5500 to be printed) and I'm working on a second comic by now. But of course that's nothing serious at all. The problem is that some of you seem so scared by the bug, that it paralizes you, putting the same fear into others. But as we've seen from this thread, there are many using P6 with pleasure and without problems. The bug is there, but it seems to affect some worse then others, haven't figured out why that is..... For some it kicks in with even small scenes, with others only when using larger scenes. For me it only comes when using more then 9 fully textured & clothed figures and for time being I can live with that. But to claim nothing serious can be done is just stretching it way to far. "Over the last years, I have mentioned a few things here and there about P5's rendering problems. Ultimately, I was forced to do all of my rendering in Vue. Because P5 just couldn't do the job. So.......P6 comes along. Hurray! Now I can render my scenes natively in Poser......." Funny that you mention that, I was thinking the same thing. Actually I've already sold Vue 5 and am using P6 only for my creations (with some help of of TrueSpace for modeling). Fortunally for me the bug hasn't stopped me from switching completely. As for the corrupted scenes,I'm not sure if that is even related to the memory bug at all. I've encountered the bug a couple of times when pushing P6 to the edge, but none of my files has been corrupted at all. I'm using 16bits too, so perhaps jjsemp may be correct in his findings.
Artwork and 3DToons items, create the perfect place for you toon and other figures!
http://www.renderosity.com/mod/bcs/index.php?vendor=23722
Due to the childish TOS changes, I'm not allowed to link to my other products outside of Rendo anymore :(
Food for thought.....
https://www.youtube.com/watch?v=pYZw0dfLmLk
STORM3 posted Thu, 14 April 2005 at 4:46 PM
"That to me sounds like exaggerating the whole problem. By now I've created a full comic in P6 (it's on it's way way to the printer as we speak for a first series of 5500 to be printed) and I'm working on a second comic by now. But of course that's nothing serious at all."
Everyone uses Poser in different ways for different kinds of work. I have managed to reduce the memory bug issue by various means (posted at RDNA) and that works fine for low resource intensive scenes. Start adding figures (and I don't mean 20 V3s) clothing, hair, props and a few other goodies to the scene and it is a no-go.
I don't know your work requirements or your system or even how you work. (I have my own solutions such as multiple renders of partial elements in the same scene with Photoshop composition as the solution for the final image). However, I can render much more stuff in P5 in one pass without a Memory Bug problems than I can in P6.
That is a serious problem that needs to be fixed and it is no exaggeration to say it is one. And I am not scared to push the limits, the problems are the lost time and file defragmentation that results with a major Poser crash.
Message edited on: 04/14/2005 16:48
XENOPHONZ posted Thu, 14 April 2005 at 4:55 PM
And in the spirit of contributing something USEFUL to the discussion
People shouldn't type in all caps like that. Yelling that way is just so gauche.
I don't think anybody thinks that this is "faked up problem". I can't recall a single person accusing anybody of complaining without just cause.
Oh?
Some things are communicated by "yelling" implications and by attitudes........rather than by the facility of explicit statements.
*Furthermore, nobody's ignoring this problem. But the memory problem has been talked about to death, this thread adds nothing new to the discussion, and more complaining isn't really going to help. I think there's a point at which complaining becomes counter-productive. It reaches its saturation point and there really isn't anything NEW to be said. And, not that you're one of them, but I am tired of hearing from people who have an axe to grind against CL and want to proudly proclaim that they're glad THEY didn't upgrade to P6 because (fill in the blanks). Who cares?
I said this back in the middle of the Poser 5 brouhaha and I'll say it again today. This is a ridiculously cheap, amazingly powerful little piece of software that's being held together by spit and glue. But the company has never abandoned it. They've managed to find a way to keep it going, and we have to have a little patience and faith, and give them our support.
If you want a higher order of perfection and sophistication for two-hundred bucks (or less), you're not living in the real world. There isn't even one piece of software that does this same kind of stuff for the same price. As of this writing, Daz Studio does NOT do animation. And I've been using Hash Animator since back in the old Amiga days, and it's always been as buggy as the jungles of the Amazon on a hot day.*
I agree with about 90% of what you have to say here. And I have consistently been one of CL's defenders on this board.
Yes.....the obssessive-compulsive Curious Labs bashers have motivations that go beyond simply pointing out technical problems. It's a personal thing with them. And I recognize that fact.
BUT (there I go, yelling again): that fact in no way mitigates a REAL (yelling) problem.
Just because certain individuals are paranoid doesn't mean that we don't have a real issue here. And an issue that's worthy of being talked about. Until such time as it gets fixed.
You know.......it's an odd approach to attack a problem like the memory bug by telling those discussing it that they need to be quiet. Just shut up.
After all, it's not bothering me -- so why should I be concerned about it for others? Those people just need to stop talking and go away.
I am not sorry to say this at all -- I have NO (yelling) intentions of "shutting up and going away" on this issue.
Some might not like it: tough.
who's REALLY feeling fiesty today
Do you have to yell like that?
How rude!
XENOPHONZ posted Thu, 14 April 2005 at 5:23 PM
That is a serious problem that needs to be fixed and it is no exaggeration to say it is one.
Yes. I totally agree with you.
But we really should stop yelling......er......talking about the issue. Or so I've been told, anyway.
Pointing out a genuine problem is bad form.
;-)
jjsemp posted Thu, 14 April 2005 at 6:48 PM
I never said yelling wasn't fun (it's GREAT fun) or wasn't allowed in this forum. I simply pointed out that yelling at CL about the memory bug problem wasn't going to achieve anything. And it won't. CL said right up front that they were aware of the problem and were going to fix it. What more do you want them to do? That's not a rhetorical question. I'm really curious --EXACTLY what more do you want them to do? And I never told anybody to "shut up and go away." That IS rude, offensive and gauche. What I asked was, what more can be gained by shouting at CL to fix the problem? If they were ignoring us and not responding, then we'd have every right to raise the hue and cry. But the problem was announced, CL said they were aware of it and were trying to fix it -- end of story. We can discuss our common "memory bug" experiences or try to solve the problem temporarily ourselves by sharing information, but constantly shouting at CL to fix it gets us nowhere. And it smacks of gratuitous CL-bashing, which I find counter-productive and pointless. It's like shouting at Blackhearted to let go of his head. -jjsemp
yp6 posted Thu, 14 April 2005 at 6:58 PM
CL said right up front that they were aware of the problem and were going to fix it. What more do you want them to do? That's not a rhetorical question. I'm really curious --EXACTLY what more do you want them to do? How about a refund of our purchase price if it doesn't get fixed until Poser 9? >:) HOW ABOUT, IN THE FUTURE, NOT SELLING CRAP UNTIL IT'S BEEN THOROUGHLY TESTED AND DEBUGGED. (I know, that's way too much to expect from them. If they didn't learn that with P5, they're probably not going to learn it at all.)
jjsemp posted Thu, 14 April 2005 at 7:35 PM
"How about a refund of our purchase price if it doesn't get fixed until Poser 9? >:) HOW ABOUT, IN THE FUTURE, NOT SELLING CRAP UNTIL IT'S BEEN THOROUGHLY TESTED AND DEBUGGED. (I know, that's way too much to expect from them. If they didn't learn that with P5, they're probably not going to learn it at all.)" ___________________________________________________ Good point. Follow your own advice. If you're unhappy, return the software and get your money back. Last time I checked, that was an option that every respectable vendor offers to every repectable purchaser. I'm sure CL is no different. I doubt that they've skipped town in the middle of the night with your paltry two-hundred bucks. See there's a difference between endlessly bitching about something and simply acting proactively. Unhappy? Return the product and get a refund and go buy 3D Studio Max. Why complain to us? P6 isn't crap by any stretch of the imagination, and NO piece of software arrives "thoroughly tested and debugged". What planet are you living on? Oh, I get it. It's simply more fun to bitch, bitch, bitch. "CL are crooks. P6 is crap." Blah, blah, blah. Fine. You have every right, so I'll just leave you to it. -jjsemp
templargfx posted Thu, 14 April 2005 at 8:00 PM
My Computer AMD Athlon 2400+ (1.8ghz) 768MB dual DDR RAM Geforce 2 MX 64MB (my lordy! thats old) Windows XP sp2 I keep task manager running ever since I heard of this memory problem, and Poser 6 generally sits at 500Mb commit, and ups to over 800Mb commit while rendering, but always drops to the 500-600Mb commit mark when rendering stops. For me the only problem with P6 I have is the EXTREME interface slow down compared to Poser 5, it's never crashed on me (i've had it cancel the render by itself) My rendering settings : Shadows : yes Texture Filter : No RayTrace : yes Raytrace Bounces : 6 Min Shading Rate : 0.00 Pixel Samples : 10 Max Texture Size : 4096 Max Bucket Size : 64 Min Displacement Bounds : 0.00 Smooth Polygons : Yes Use Displacement : Yes Post Filter Size : 2 Post Filter Type : Sync I always use IBL and AO at the moment (cause there new!) the most complex scene I have worked on so far is V3, C4U clothes, over 15 pieces of furniature, a room with windows and doors modelled, 90% of stuff has textures. V3 has one of my famous overly-complex node setups on her. has anyone considered that the problem that might be occoring (and why some are not effected) is due to windows, and in particular, the updates? I have not updated my windows for over 3 months (because everything works great, and I always say, "if it aint broke, dont fix it!)
TemplarGFX
3D Hobbyist since 1996
I use poser native units
yp6 posted Thu, 14 April 2005 at 8:03 PM
If you're unhappy, return the software and get your money back. I requested an RMA this morning. I'll give them a couple of days, request again, and then go to my credit card company if I have to. See there's a difference between endlessly bitching about something and simply acting proactively. Couldn't agree more. However, members of this forum have the right to see both sides.
ratscloset posted Thu, 14 April 2005 at 8:31 PM
Okay, I have not piped in on these discussions (and I use that term loosely!) I have an AMD 2800 with 1GB of RAM and a nVidia GeForce 6200 with 256MB. I am running WinXP with AVG and Wins own Firewall. I just finished a 10 second animation with 8 figures, several of them Mil3 figures. The lighting was simple, due to the nature of the animation, but I had no trouble whatsoever with Memory issues, any crashes, saves, etc... This is not a powerhouse machine, but it is set up for Graphics work only, and no games. I run Works Calendar, IE, Outlook Express, Bookshelf(I can not spell well!), Bryce, Shade, FastCAD, PSP, and Poser along with several other programs at the same time. So far I have not crashed a single program (out of all of these, the most unstable is the stupid Calender and its reminders!). When I had issues in the past similar to what many are describing with other programs, I finally traced it to the latest game and something it had installed on my system to make the game work with my soundcard and video card. I did a complete uninstall of the game and issue went away. Since then I stopped playing games on my machine that I use for work. I do not know if this may be the cause, but I mention it, because some people were having an issue with Norton (I think) at one time.
ratscloset
aka John
XENOPHONZ posted Thu, 14 April 2005 at 11:13 PM
And I never told anybody to "shut up and go away." That IS rude, offensive and gauche.
No, you didn't word it in that fashion.
But that is the thrust of what you've been saying.
What I asked was, what more can be gained by shouting at CL to fix the problem? If they were ignoring us and not responding, then we'd have every right to raise the hue and cry. But the problem was announced, CL said they were aware of it and were trying to fix it -- end of story.
I don't really have any problems with this statement.
But since what you suggest isn't what I am doing, your point here utterly escapes me.
However, I have to admit that your own approach to the problem puzzles me.
We aren't allowed to discuss the issue.
How very strange.
I'm really curious --EXACTLY what more do you want them to do?
I'm really curious -- WHY does this matter to you?
For someone that apparently regards a serious flaw in the software as a thing to be overlooked, and not to be discussed too thoroughly by others.......you shouldn't care. Why does it matter?
However, I will say this much: it would help if they would keep us updated on what's going on.
constantly shouting at CL to fix it gets us nowhere. And it smacks of gratuitous CL-bashing, which I find counter-productive and pointless.
I agree with you.
That's why I'm not constantly shouting at CL. Nor am I CL-bashing.
If you care to re-read my posts in this thread, you will note that I give full credit where credit is due.
Likewise, I make no attempts to hide from reality. Even when that reality is a negative one.
That would be counter-productive and pointless.
XENOPHONZ posted Thu, 14 April 2005 at 11:17 PM
I have not updated my windows for over 3 months (because everything works great, and I always say, "if it aint broke, dont fix it!) A co-worker of mine received a virus on his office computer. The virus would have been fended off of his machine if he had performed regular updates.
XENOPHONZ posted Thu, 14 April 2005 at 11:19 PM
P6 isn't crap by any stretch of the imagination On this point, we agree. Outside of the memory bug, P6 is golden.
donquixote posted Fri, 15 April 2005 at 12:45 AM
jjsemp, XENOPHONZ, how 'bout we let it go? I mean passion can be a very good thing, but why not save it for the ART? And as for CL bashing, I at least was mostly clowning. I only meant to convey that I like Poser 6 a lot, and it is just very frustrating that I can't really use it as effectively as I'd like.
XENOPHONZ posted Fri, 15 April 2005 at 1:47 AM
how 'bout we let it go?
I suspect that this thread is about done anyway. It's on the second page. 3rd page: and not many people will notice it any longer. Including moi.
Frankly, I agree with about 85 to 90 percent of what jjsemp has to say.
But just like the memory bug -- it's that 10% at the end that causes the render to crash.
Ah, well......we haven't heard the last of this issue. Not by a long shot.
I hope that anyone who objects to discussing the subject will take the simple expedient of avoiding the conversation.
Better for all concerned.
Because some of us aren't going to leave off talking about a flaw this central to the program that we are addicted to.
lmckenzie posted Fri, 15 April 2005 at 3:43 AM
Poser works fine for me. Oops, forgot I'm using Poser 4. But seriously folks since this thing seems to be cumulative to some extent, kicking in after a certain amount of use, has anyone tried using one of the RAM freeing utilities periodically while running P6--possibly a stopgap help until the (demons/victims) at CL git 'er done? "If the police arrest a mime, do they tell him he has the right to remain silent?" - George Carlin
"Democracy is a pathetic belief in the collective wisdom of individual ignorance." - H. L. Mencken
Blackhearted posted Sat, 16 April 2005 at 9:33 AM
geez, i had no idea it was such a mystery.. im holding my head because im dead tired, it was like 4am and after some out of focus and underexposed shots i was just hoping to get the damn thing over with. as for P6, ill buy the darn thing when the bugs are finally ironed out - im on slowass dialup now and i can't afford to be downloading hundreds of megs of patches. CL has a history of releasing bug-laden software that should have been in beta testing for a few more months, i hope they smarten up by P7.
LornaW posted Sat, 16 April 2005 at 9:43 AM
Lol! I'd be holding my head too if I had to have my pic on the front page here and ended up with remarks like, maybe he's bald! Big pimple or wart anyone? Maybe covering up a third eye?? A forehead nipple? Wooooh, creepy! I might be tempted to holding or covering up other areas too, never know what kind of imaginations run rampant here. The TOS only covers posted pictures, the thoughts are still there!
donquixote posted Sat, 16 April 2005 at 12:44 PM
"because im dead tired, it was like 4am and after some out of focus and underexposed shots i was just hoping to get the damn thing over with." --- Oh c'mon Blackhearted, you expect us to believe that? What kind of fools do you take us for? ;*)
LornaW posted Sat, 16 April 2005 at 1:19 PM
Very foolish! It IS a third eye he's hiding you know, and it's always watching!
Blackhearted posted Sat, 16 April 2005 at 6:24 PM
notice the one on my artist page has it covered too... its a conspiracy. (speaking of which, i should ditch the santa hat since xmas was like 5 months ago. the next photo will reveal that i actually have a little guy growing out of my forehead - like quato from total recall.. he holds my cigars for me sometimes)
Lawndart posted Sun, 17 April 2005 at 1:36 AM
nice... LOL
yp6 posted Sun, 17 April 2005 at 5:06 AM
(speaking of which, i should ditch the santa hat since xmas was like 5 months ago. the next photo will reveal that i actually have a little guy growing out of my forehead - like quato from total recall.. he holds my cigars for me sometimes) Handy, a "nicotiene co-processor!" ;)