Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 09 8:30 pm)
It could be memory related since some of those bum files can be real honkers in size and doing a pic in 300dpi is putting a load of the system as it is. The way around it is give poser much more memory, which may or may not work since the cpu is having to do everything it may get bogged down so, idea 2, use bbedit to open the cr2 of what you want to use in the pic and change every instance of .bum to .jpg that way you use the jpeg files that the bums were made off of and you save a HUGE amount of space. :-)
Why shouldn't speech be free? Very little of it is worth anything.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Hello Renderoos, Just created a groooovy texture along with bump maps, and it renders beautifully in Poser. It's hard to type when you're patting yourself on the back LOL. But then... a problem! It renders just fine when I render it in Poser's main window at 72 pixels per inch. But when I tried to render it in a new window at a higher resolution (330ppi, suitable for printing), I got the dreaded message "A requested bump map does not exist or can't be read".... Now, obviously it exists, coz I just made it, and it can be read, coz Poser just read it before... so... is this a memory problem? Anyone else had this? Any ideas how I get round it? I'm using Poser 4 on a Mac.