Anyone purchased UD Hydra at daz? Everytime I apply the mat pose file in P5 I get the above error, And the material room no longer works. P5 won't render and I get the same error on any file I open after that until I close P5 and Restart it. I get no error in P4 loading the Hydra. I've loaded the cr2 in p4 applied the mat then saved the CR2 with textures and loaded in P5 same error. looking at the pose file I don't see anything out of the norm.

have you tried rendering without the textures? if it still happens then it's possibly the obj that's the problem, try opening it in UVMapper & saving it without doing anything else.

Renders fine without the mat file applied. Also the texture looks messed up when applied in P4 and P5 but according to the readme that is norm.

then it's something seriously wrong with those textures, why would it be normal for them to look screwed up? I've never had something come with screwed up textures especially when I've paid for it. how about opening them up in Photoshop/paintshop & resaving them maybe it's the dpi on them, ive read in other threads that poser can sometimes throw a fit if the dpi on a texture is anything but 72.

This seems to be a P5 bug, I've had similar problems. Once you start getting this error it seems to re-occur everytime you to render the same pz3, so I suspect that the (pz3) file has been corrupted in some way. Are you using the same pz3 or are you reloading the figure into a new scene from a cr2? It may be worth renaming whatever files you are having trouble with then recreating them (or re-installing if it is the cr2) and seeing if you can identify any differences that maybe causing the problem. Bill

ah I misunderstood what you said, it's not the obj or the textures, I haven't got the hydra yet but I found something else that does the same, after a few experiments I've found it's not the textures or the obj, it looks like something in the cr2 of a few items have something that Poser5 doesn't like, maybe it's a defective morph target.

I have hydra model and got the same error, then someone said maybe it was because the textures were very hi res, so I saved originals, and made smaller ones with same name, and now it loads fine and no error.

I can buy that solution but I think it's wierd that it works in P4 but not P5. I'm not going to bash P5 like others have, before the patch I had pretty much the same problems as everyone else. I kept my opinions to myself and went back to P4. Now after the patch the is the only problem I've had.

I never tried it in p4, but it will work after you reduce the textures a bit, at least it did for me :)

96dpi seems kinda wierd for a non print image I wonder if someone would try changing the dpi of the texture to 72 which should only change the size of the image by about 15 percent. perhaps firefly has a hard time translating UV coordanates to non standard dot sizes?

I had the same problem with the Hydra. See other thread about the Hydra, and the answer is there. (I can't remember the exact resolutions to change it to.) I didn't have to drop it too much to get it to work. I tried first halving the texture resolution, but you don't have to go to that extreme.

Hmm I just opened the textures in Photoshop and it said 72dpi. Dunno about that. The real-time display of Poser (any version) won't work with texture maps 5000x5000. That doesnt affect the final render. The FireFly renderer itself, as far as I know, won't render any texture and bump that is 5000x5000; or so a friend tells me. I was told that the program is running out of memory, and that causes the crash. I am not sure if that person is right or not. P4 has different memory handling so that might account for the fact that it doesn't happen there. As far as why we went with the large texture size? I decided to UV map as map parts as possible in one section to get the fewest seams. And the resolution was chosen incase of close-ups and the possibility of poster print makers. Most renders don't need that kind of texture resolution, but its easier to go down in res than up, so we shot higher. My suggestion for anyone having problems is to reduce the image sizes by 20% or 4000x4000 and 1600x1600 respectively. I apologize that anyone's having problems, but neither Mab or I have Poser5 so we had no way of knowing about the problem, having assumed P5 would do everything p4 is capable of and more.

I use P4 and the Hydra renders just fine with the Hi-res and renders just as normal as well. And very pretty I might add. That is a shame about it being a problem in P5. Mabey the next patch. :( Glad people figured out is wasn't the Hydra itself though. Michael worked really hard on it. See more heads are better than one...no pun intended. :) Anton

I Really like the Model and the detail of the textures I think this thread however went in the wrong direction I was just wondering why P4 works fine and P5 does'nt I guess this is the first model I've had with such a huge texture map. Thing is I've rendered 2 Mil dragons in a scene so with other characters SO i Don't think It is a Memory problem. So The answer seems to be that P5 can't handle a 5000x5000 tex map. Sorry about the wrong DPI settings I got them confused with somthing I was working on. You are correct 72 DPI

I'm getting "caught exception c" errors when I try to render a scene with items from the P5 runtime and the P4 runtime. I reported the error to CL but I hope I'm not going to have to re-do the image. I'm debating on installing Vicki again into the P5 runtime folder and trying again.
I didn't get these errors till I installed the patch.

Actually I've had the same problem with P5 and only when using the Firefly renderer. Poser 4 renderer doesn't seem to yield the same problem. Before new patch was installed Poser 5 crashed a lot but I didn't get that error. It's not an obj issue though it might be a texture issue or an issue with one of the firefly render settings. Not entirely sure. I have removed bump maps. I also have an unrelated problem with the firefly renderer causing small dashes on the render. Not sure what that's about. It happens on every render. It looks like as the Firefly renderer moves across the grid there are some gaps between the grid and the scene which causes some of these gaps. I might make a post of this eventually when I have more time and if I don't continuously get these exception errors. I haven't reported the problem to CL and I want to test the problem with additional RAM. Currently my system is an Athlon 2.1Ghz, 512MB RAM, Geforce 4 Ti4400. I've used textures as small as 2000x2000 and as large as 4000x4000.