Sat, Jan 11, 8:40 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)



Subject: Not Picking Up Textures


Seliah ( ) posted Mon, 24 May 2004 at 5:39 PM · edited Sat, 11 January 2025 at 6:05 AM

file_110512.jpg

This is really wonky. I've never seen this before, in three years of playing with this programme. LOL I have a conforming figure right now (the SUDI boots from the armour set), that when I assign the textures to the material, it 'shows' prior to rendering. However, when I render... the one surface does NOT pick up the texture, while the other part of the surface DOES. The pic shows what I mean. I was working on Ruby a bit more, making a pic for the ad picture, and was going to use these boots (I LOVE the things, and they work with her...), but if I can't texture them... :( The model on the right is non-rendered, the one on the left is what it looks like when I render... Anyone have any ideas? Yes, I checked to make sure the texture map was set to 100 percent, and I double checked and it is indeed showing the texture file there. I'm at a loss. :/ Can't figure out how to get these things to pick up the textures I'm assigning! ~Seliah



Ajax ( ) posted Mon, 24 May 2004 at 7:02 PM

I've seen this lots of times. It usually means you have too many high res textures in the scene and there's not enough memory to handle it. Try reducing the size of some of your textures or try closing Poser and everything else, rebooting and then making sure that Poser is the only thing you have running.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


ronstuff ( ) posted Mon, 24 May 2004 at 7:39 PM

Ypu need to delete the shadernodes and re-apply the texture


Seliah ( ) posted Mon, 24 May 2004 at 7:54 PM

Ajax - thanks, I'll double check the pz3, but I think the only texture files in use is the leather texture on the clothing, the eyelash trans, the figure's body/head texture and the hair... And Ron - sorry, but what on earth do you mean by shadernodes? If it's a Poser 5 thing it doesn't apply to me.. I'm still running on Poser 4. ^.^ ~Seliah



Seliah ( ) posted Mon, 24 May 2004 at 8:25 PM

Ajax - I rebooted the machine, absolutely nothing else but Poser running. Started a clean (new) scene. Loaded ONLY those boots in. Applied one texture - no reflection or trans or bump maps. Just the base texture. Same thing. :( sigh Alright. Guess I'll have to find a different set of boots... because these are just NOT going to take a texture. It applies, it shows the texture pre-render, and then as soon as I render it, it renders white... I don't know what else I can do with it. I can't force the blessed things to render. :( ~Seliah



ronstuff ( ) posted Mon, 24 May 2004 at 10:20 PM

If it is Poser 4 or Pro Pack, try this: set the material settings so that ambient color AND reflect color and highlight color are all black and reflect value is 0. This may allow the basic texture to render. If it does, then one of these may have been overriding the texture, but not showing up in preview.


Seliah ( ) posted Mon, 24 May 2004 at 10:45 PM

file_110513.jpg

Ron- Yep, I tried that too. I loaded up the rest of the entire set, and discovered identical problems with part of the chest armour. *points to the pic up above* I've been experimenting with the set now... I think it's just a matter of not being UVMapped? It's a v.07beta ... I'm going to pull the boots into UVmapper I think. And see what I come up with. ~Seliah



Ajax ( ) posted Mon, 24 May 2004 at 11:19 PM

If it shows in preview, the UV mapping should be OK. How big (width by height) is the texture that's not showing?


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


Seliah ( ) posted Mon, 24 May 2004 at 11:25 PM

file_110514.jpg

I've tried 3 versions of the texture. One was a res of 2048x2048, the other was a res of 600x600, and the third was a res of 800x800. No go. On an interesting note - when I do pull the boots into UVMapper and remap them, then save the OBJ. If I import THAT obj of the boots into poser, it textures and renders w/the texture intact perfectly. However, if I try to plug the 'new' obj file into the Ccr2 at all, then it either loads the figure up with me back at square one (non-rendering texture), or else it 'loads' a figure, but the figure is not actualy in the scene visually. It is only listed below the window as being there. This particular set does not have any Geometry files - the obj's are all in the character folder ... I've tried plugging the 'new' obj into the current cr2 both by putting it in the Geometries folder and pointing it there, AND by overwriting the 'old' obj and by adding the 'new' obj to the character folder and pointing it there. No luck yet. But they DO texture as an obj file... not too sure what is going on with it - I don't know enough about cr2 files to be able to dig through all that code and find the spot that's gone awry... ~Seliah



ronstuff ( ) posted Tue, 25 May 2004 at 12:11 AM

It is an interesting problem... I agree with Ajax about the mapping - if it shows in preview then there is some kind of mapping. It is looking like the problem is with material assignement, perhaps a naming or grouping conflict, or maybe Poser can't find the texture at render time. I had that happen once when I tried to use a 256 color PNG file for a texture - Poser did the preview OK but it would not render. I know this is grasping at straws, but I think the problem is in the cr2 rather than in the obj. Good luck... I hope you solve the mystery :-)


Seliah ( ) posted Tue, 25 May 2004 at 1:12 AM

file_110515.jpg

Nope, problem was indeed with the OBJ. There was absolutely NO UV info on it at all. It was never mapped. All fixed now !! One of the folks over on RDNA helped me out quite a bit. ^.^ I was one step shy of the actual proper procedure to fix it, lol, he picked it up where I was stuck and got it working. Just had to remap the OBJ entirely... import the UV's, save the OBJ in the Geometries, and bingo. Works perfectly now ! ~Seliah



Ajax ( ) posted Tue, 25 May 2004 at 4:40 AM

That's really strange. Oh well, at least you've got them working now. Have you contacted the maker to let them know about the problem? Sounds like they put the wrong mesh into the zip.


View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message


Nevermore ( ) posted Tue, 25 May 2004 at 7:34 AM

What's the set called and where is it available from? Looks pretty darn stonky, wouldn't mind picking it up myself :o)


Seliah ( ) posted Tue, 25 May 2004 at 11:39 AM

Ajax - it's a v.07 beta set, and the creator makes no bones about it being incomplete yet, and says there's still some problems he's seen with it. I have sent him an email about what we did to fix the 'one' little problem and let him know that I'm going to be remapping the rest of the set as well. Nevermore - it's the SUDI armour v.07beta, and can be found on this page: http://myweb.hinet.net/home5/sudi/sudi_armor.html It's a nice set - just needs to be mapped is all. ^.^ I'll be remapping the rest of the set today, so if you download it and want the remapped obj's get ahold of me via email - seliah (AT) childeoffyre.com and I'll send them to you. ~Seliah



Seliah ( ) posted Tue, 25 May 2004 at 7:19 PM

file_110516.jpg

Okay, I think I've got this thing remapped, with exception of the thigh pieces... For some reason they don't want to cooperate. LOL I'm doing the exact same thing with them as I did with the others, and I've checked the cr2 for typos and none there, yet they just will not load properly at all. LOL But anyway - this is the rest of the outfit... ^.^ Got it working nicely, I think. ~Seliah



Privacy Notice

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.