Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 08 9:27 am)
Not sure, but have lost too much hair trying to figure out what would work anyways, lol. I suppose it is possible that the original jpg was corrupted or formatted weirdly, but it didn't look like it was. My guess is that my puter still wouldn't be able to handle a 300 dpi skin file, but that's just a guess. Good thinking though, I'll have to experiment when I get the time too.
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.
So there I was using a high res skin file for mike, when everytime I tried to render it poser would freeze up. I figured the skin texture was just too big. So I took it into paint shop pro and reduced the skin textures to the same size as the other textures I've used and were able to render, and then stuck them back on my mike model. Did it work? Noooooooooo... I couldn't figure out the problem at all. Why was one skin file freezing up poser when another one (that was the same size) didn't? Apparently, it all had to do with the dpi (dots per inch) of the texture file (not the dpi in the rendering options). I noticed when looking at the image information of the high res mike skin files in Paint Shop Pro that the dpi was 300, whereas my other skin files was 72. That being the only difference I could see between the two skin files, I had to create a new image that was the same size as the 300dpi image, but make the new image 72 dpi, then copy and paste the hi res skin file to the new lower dpi image and resave it, reload it. Then miraculously... everything worked fine. I thought it was very odd that the dpi value of a texture file mattered to the rendering of that file, but apparently it was. Anyone else have this prob?