oddboots opened this issue on Aug 13, 2005 ยท 9 posts
oddboots posted Sat, 13 August 2005 at 4:02 AM
Hi all - Just wondered if anyone could help me out with a recurring error message in poser 5:
"A requested texture map does not exist or can't be read"
I seem to be getting this quite a lot when rendering moderately complex scenes, e.g. containing 2 textured V3/M3's plus a stonemason environment. Anyway, I was wondering if anyone might know what the problem is likely to be? (I'm planning a new system at the moment and it would be great to know how I might be able to avoid these errors in the future)
Many thanks in advance!
p.s. - my current PC is a Pentium 4c 2.8 with 2 gig ram and it renders Jim Burton's test in about 190 seconds (http://www.renderosity.com/messages.ez?Form.ShowMessage=1403770Mser%20Resources%20-%20Microsoft%20Internet)
jt411 posted Sat, 13 August 2005 at 4:38 AM
I don't think it's a hardware problem. Sounds like Poser just can't locate certain textures, or maybe those textures are in a format Poser can't read. Go through your figures and props in the material room, check the node for anything using an image map. Just click on the name of the image from the node to verify it's file path and type. That's my theory at least.
oddboots posted Sat, 13 August 2005 at 4:57 AM
Thanks for the reply - the thing is that the paths etc seem to be fine and figures/environments all render well individually (or even in pairs). The problem only seems to arise when the scene hits a certain (and by no means extreme) level of complexity.
One thing you've made me think of is that I tend to customize a lot of the textures I use (to make them more realistic) and save them as photoshop files (loading them manually in the material room). Maybe P5 doesn't like handling too many .psd files at once?
Thanks again for your suggestion :)
Fazzel posted Sat, 13 August 2005 at 5:48 AM
Make sure the file your cr2 or pp2 or pz2 has the exact same name and extension as the file in your texture folder. One letter or number off and Poser will never find it. Also make sure your folder paths in your files are correct
TrekkieGrrrl posted Sat, 13 August 2005 at 6:25 AM
It IS generally a memory problem. My Poser 6 tells me the same if I try to render things with large textures (like V3) and accidentally turns Texture filtering on. I don't think the psd thing is an issue but you could try saving them as jpg's (high quality) and see if it helps on the issue...
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
oddboots posted Sat, 13 August 2005 at 7:16 AM
Thanks for the responses all - I've tried changing the textures to jpg's, but the same thing happens. Guess I'll just have to make do with less complex scenes... :( Has anyone any idea if improving my hardware might help (eg faster or twin cpu, raid 0 hard drives, faster ram...)? thanks again :)
randym77 posted Sat, 13 August 2005 at 9:11 AM
Post a screenshot of your render settings. You can probably adjust them so it renders. Your computer is already pretty good, so I don't think upgrading will make a big difference.
svdl posted Sat, 13 August 2005 at 10:52 AM
Weird. I've rendered much more complex scenes in P5 without any problems, on a slightly lighter PC (P4 2.8 Ghz 1.5 GB RAM). So I don't think it's a hardware problem. Is it possible that two textures have the same filename? Poser doesn't remember the path, it may get confused. If this is the problem, you should get an error message when rendering certain pairs of figures. You could try running the free version of CorrectReference (freestuff here) on your .pz3. I always run it after installing new content.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
oddboots posted Wed, 17 August 2005 at 3:25 PM
Thanks for all your suggestions! I eveentually had to reduce the resolution of some of the textures I was using - not ideal, but it worked. btw, I mostly just use the P4 renderer in P5 (lol, still haven't got to grips with displacement maps!) so the errors aren't due to extravagant render settings. Thanks again for your help all!