Here is the "brand new," "built from the ground up" Poser 5 ten minutes after I told it to stop looking for a texture. Was the program locked up or should I have waited another ten minutes? CL, are you ever ever **ever** going to fix this??? I know you're busy on the "issues" with your 3rd-party add-ons to Poser, but this is, IMO, a serious *problem* and/or *BUG* that is also (coincidentally) in Poser 4 and the Pro Pack. Why are you guys so affraid to touch the core of the original program? Rosity members: sorry for the rant but I just couldn't take it any more. I'm done now.

Bravo on "issue". I'm damn tired of people "addressing issues". We need to get back to "solving problems", which is a constructive process, instead of "addressing issues", which is nothing but yakity-yak. I wish some ex-CL type would break through the NDA shield for a moment and at least explain why the original Poser code is untouchable.

My python page
My ShareCG freebies

Jackson, I have found that if I am very very patient (like anything up to 45 mins), Poser will eventually "unfreeze" from this state. A pain in the arse to be sure, but better than having to rebuild your scene if you didn't save before applying that MAT pose wince I'm running P5 on its own 80gb HDD with 1024 DDR RAM and a 2.4gb processor. Poser is teaching me patience, if nothing else ;-)

---

"you are terrifying
and strange and beautiful
something not everyone knows how to love." - Warsan Shire

for some reason when this happens to me, if I just wait for it to "unfreeze" it'll take up to 20 minutes. But if I just start clicking my browser a few times or hit the send/receive button on my e-mail, Poser will unfreeze almost immediatly. Don't know why but for me it works.

Of course, you can always force-quit Poser and reboot Windows in less than 5 minutes. But the question remains: why does Poser STILL freeze/ crash/ lock when a texture can't be found? Professional 3-D programs ask the user for an alternate texture or skip the file completely. Why doesn't Poser do this? Or is searching the entire hard drive for a file with the same name as the texture??

I wish some ex-CL type would break through the NDA shield for a moment NDAs are still valid after your employment. I am not allowed tell you internals about the Poser source code or wether Pepsi or Coke is in the fridge in 655 Capitola Road.

Sometimes, it's not a freeze-- the problem is I never know when that is. I have been known to wait an hour or two--once I waited overnight. I really think those were freezes. The argument against force-quitting is nobodys' perfect and although I tell myself to save before any major occurence-- large texture change, adding a figure, light change, rendering, I don't always remember to do it, and the last time I had to reconstruct an hour's work. How hard is it to reprogram Poser to let go of the search with one cancel? The window to do that is already there! Apparently this is as hard as perpetual motion or exceeding the speed of light. Emily

Thanks to those who made suggestions but I've been working with Poser since the release of 4 and I know all the workarounds. I'm just fed up is all and would like to see it and the other major problems fixed. I bought the Pro Pack hoping for fixes; no such luck. But then they promised all would be well in P5. What a joke, nothing was fixed with the core. Stewer: I don't want to know about the source code. I just want to know why you guys don't seem to want to even try to fix or rebuild it. Is it owned by some sadistic hermit in a cave who won't give permission? Oh, and sorry about the huge picture...I thought I'd shrunk it more than that.

I do not represent CL in any way and I especially will not make any comment on decisions that were made by CL because I know people will quote me as "CL said ...". After all, this is how some folks here made DefaultGuy and Nosfiratuu leave Renderosity. I am just another 'rosity member and Poser addict, OK?

Sure, NP. I was just responding to your response regarding revealing internals about the source code.

My assumption in the vacuum of response that comes from CL is that either 1.) They don't know How to fix it. or 2.) They don't care. Cause it sure isn't that they don't know it needs fixing. We've been bitching long enough. Given that the people I heard speaking for CL back in Kupa's days seem to care almost too much, I have to think that they just don't know how to fix it. Or, thought they had but it didn't take. Emily

While I would not ask anybody to violate an NDA, it sure would be nice to know whether CL or Egisys is even intending to come out with a SR4 release. They have a history of 3 (strikes/SRs) and yer OUT (of luck), if ya get my drift. At least, if i knew they had plans to deliver a 4th SR, I wouldn't wast so much of my time trying to find work-arounds and fixes that I'm not being paid to do. So if anybody can at least tell us that without violating an NDA, it would make a lot of us feel better.

The answer for SR-4 is easy: I don't know. I think the missing textures problem can be worked around without having access to the Poser source code: One could write a Python script that'd skim through the pz3 file and check wether the files it refers to exist or not, and if they don't exist, it'd remove them completely. Then it would save the modified file and open it in Poser.

Thanks, stewer. I think Hogsoft's Correct Reference utility would help identify missing texture issues, but I've had lock-ups like this happen even though I know that thetures and path references were correct (although much less frequently since SR3). Do you know what else might be creating the conflict?