but darnit if the strangest things don't happen in P5. I just spent an hour or so fooling around in the materials room setting up a scene. Finally got the scene looking just right, even the reflection in the water looked good. So I go to render again - just like I had done a dozen times before. The scene renders. Wow! Hey, I think to myself, the firefly render in P5 is pretty neat. The render is done and I am looking at my masterpiece thinking, this one I'll save it actually looks great. Then suddenly an error message pops up, can not find texture so and so. Then another, and another, and another. This continues on a run away course right up until Poser 5 suddenly closes. Of course I loose the render, but what gets me is my hard drive is still ticking away generating these silly can not be found errors. So, I have to reboot. No, its not a virus. This computer never goes on-line and I always scan for virsus before I load any files onto it. So I figure it has got to be a bug. In fact, I have gotten the can not find texture error message before, and normally all I have to do is repoint P5 to my texture libary. What got me is it had no prob finding the textures all those renders before, and then it went crazy and I guess tried to make up for it by pulling a runaway. So I am laughing, smiling, and being optimistic. Afterall, no point crying over spilt milk and all that... So, anyone else have a similar great happy moment? Or am I just lucky. :O)

Always and I mean always save your scene before rendering.

Yeah, you are right. Even when you are just tinkering around, cause it might turn out to be better than you expected. And gosh darnit you regret you didn't. LOL!

Did you move your P4 runtime folder by any chance? if so that is probably your problem. You might want to try using hogwardens CorrectReference to sort out your texture errors, P5 is a lot less forgiving then P4 about absolute refrences.

That's probably what it be then, cause I did. Course, like I said, makes no sense that it render all those times before and didn't have any problems finding the textures. LOL! Oh well. Live and learn. Thanks for the tip. :O)

I had this occur only once. Accidentally double clicked on a .pz3 file whose textures and other necessities hadn't been added yet (I was in the process of loading all of my add-on stuff at the time). Well, when P5 opened, it naturally asked for a reference to a texture it could not find. I mistakenly :) chose 'Cancel' and it proceeded to ask for it ad infinitum. No matter how many times I cancelled, it continued to request a reference to that same texture. Had I chose any old texture, it may have continued (asking for the other texture references, that is), but I ended up ending the P5 process instead. My point: Seems to me that P5 should have either said, "Oh, well, he don't want a texture" and moved on -or- raised a graceful error like "My life is meaningless without that texture" and discontinued loading the .pz3 file. Hopefully this will be fixed in the patch. Otherwise I'll make a note to contact them about it. Like you say, shadownet, "Live and learn." Kuroyume

And having so much fun in the process. :O) See I am still smiling and being positive. Though must my hair is in a pile on the floor.

Attached Link: http://www.renderosity.com/freestuff.ez?Form.Contrib=hogwarden&Topsectionid=0

Kuroyume0161, FWIW, it asks for the texture once for each time it's used: Once for the pupil. Once for the eye white. Once for the fingernails. Once for the toenails, and so on ad nauseum.

heyas; if it was rendering okay before, it can't be a missing or incorrect texture file reference. sounds to me like a memory leak deal, where it renders just one too many times and finally explodes.

Even if I laid Poser down forever(in favor of some other masochistic pusuit),I would still check in daily with this forum.You guys are great fun.

Thanks for the comments. Bloodsong, I think you are right on the memory leak. A bit later, I had the hierarchy editor freeze up on me when I went to scroll down. Use to have this happen in P4, so I started using rambooster. When every Poser got sluggish or one of the interface would freeze, I would do a memory dump and everything would start working again. Think I will try that with P5 and see if it helps. (Oh, btw, came across your P5 tutorials, thanks!!!! :O) Well, I am off again to venture deep into the mysterious, dark, unknowns of Poser 5. So wish me luck, and if I am never heard from again - just remember the movie Jumanji! Cheers,

On textures and such, I merged my textures and Geometries folders into the P5 hierarchy (I still have all of my P4 stuff backed up, though.) I did that after I loaded Mandi in P5 and it started asking for the location of her .obj file, textures, bump maps, etc etc. After I merged those two folders (the rest you can park anywhere), all went well. /P

Bobasaur: Then it must have referenced it fifty times or more. That's a possibility, but a slim one. I was cancelling for ten minutes. wdupre: As I said, the textures for the .pz3 hadn't even been loaded yet. They were still in a zip file. Why was the .pz3 already there? Because I had copied my Poser project directory (not part of Poser 5 program directories) from my other computer, but the textures were in the Runtime of P4, not copied for obvious reasons, which is why I was in the process of loading them into P5. Capiche? :) Kuroyume

So, we are all agreed then. P5 is the best thing to come along since sliced, buttered bread. And just like buttered bread, sometimes you need a little jam to go with it. See, still thinking them happy thoughts. :O) cheers,

Kuroyume, yeah I got you, that link was more for shadownet who said he did move his P4 library. I think a lot of bugs in the system are being caused by inproper file refrences and how P5 is insistant on straitening them out before going on to the next step, not to say that that is not a legitamate bug, but it's a good Idea to get those refrences Ironed out if just to speed up the process of loading scenes up.

And I thank you again for the tip. Good idea to address any probs that might be a result of wrong references first.