Mon, Jan 20, 10:52 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

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



Subject: Vicky mapping bug


pack ( ) posted Thu, 29 June 2000 at 11:03 PM ยท edited Mon, 05 August 2024 at 4:40 AM

When I changed Vicky's skin map (aka SkinBody)to a different image map, the new map gets applied to the SkinHead as well (Face has clothes map on it). Visa versa when I try to fix the head map back, it changes the body map so it has a face on it. I am picking the proper groups, I've been doing this a while, Am I the only one with this problem?. Can someone confirm this problem? the last map I apply gets applied to all other groups (lashes,head,body etc),


cooler ( ) posted Thu, 29 June 2000 at 11:22 PM

sounds like you're leaving the "apply to entire figure" box checked instead of unchecking the box & selecting the respective texture map to go with the desired target area.


LoboUK ( ) posted Fri, 30 June 2000 at 4:55 AM

This one is especially designed to catch everyone out :) Mostly, "apply to entire figure" gets left on when you're applying texture maps to posette. However, if you do this with Vickie, it tries to apply the body map to the face (or vice versa). As cooler says, you need to deselect "apply texture to entire figure" Paul


picnic ( ) posted Fri, 30 June 2000 at 7:49 AM

Paul, just stepping in, but he may be getting caught with something that I haven't figured out either. When I have clothing and Vicky in and change maps for instance on the clothing, I'll render and suddenly find that the head map is now mapped to all of Vic, even though I had set it up differently and it had worked before. I've had this happen way more times than once--and have specifically watched for the 'texture all' thing. I haven't figured out a pattern yet though. Yes, and when I've tried changing the texture on Vic, which I do a lot, it happens also. You start to think you've made a mistake and when you specifically watch for it, it still happens. Only happens for me when I have several maps (Vic and clothing) in my list of maps. Diane


LoboUK ( ) posted Fri, 30 June 2000 at 8:10 AM

Hmmmm ::scratches chin and looks pensive:: I'll have to try that one out Diane, see if I can get the same result Paul


picnic ( ) posted Fri, 30 June 2000 at 8:22 AM

Have never had it happen with Posette, but when I was using Rena's composite of Vic/Posette the other night and also had Vicky in the window, I had it happen over and over--kept thinking I was losing my mind LOL. I was trying to set the composite back to 'sort of' Vicky so I had a more or less clean slate to start with her, so had the same map on Vicky and the composite to try and do that--and strange things would happen when I would render G.


jschoen ( ) posted Sat, 01 July 2000 at 1:03 AM

Just a quick thought. Are you using the "mapped" Vicky? When you first installed Victoria, it installed 2 Victoria's 1: Was just a plain Victoria no maps applied and just color materials assigned for all the body parts. 2: Was a already mapped Victoria. With both of Zygote's Head and Body maps already applied. The choice was if you had purchased the textures from Zygote you wouldn't have to hand apply the textures. SO I'm assuming the texture path and name is hard-coded into the CR2 I can see where this may cause problems. Try using the Vicky without the tx maps and see if that helps. James


picnic ( ) posted Sat, 01 July 2000 at 8:29 AM

No, I created a 'white' Vicky so I could more easily use my own maps. I did buy that one, and have her in my library, but don't use it. I'll have to research this a bit more and pay attention to when it happens exactly--what maps are in list, if I have 2 models, etc. Diane


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.