Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 24 8:11 pm)
When I add the lightsaber as a prop, (.3ds model,) and set up the colors just the way I want them, ie. with all transparency settings just right to get the exact 'glow' effect above, then either save the file, or add as a new character, the lightsaber IS added to the saved file, the .pz3, or the .cr2; however, and here is the punch: Poser is adding a new generic 'MATERIAL' to the lightsaber when I either reload the scene, or add/replace the character in the scene. This new material overrides my current object coloring settings, and so even if the file is saved with the appropriate settings, it gets HOSED when it is reloaded. If anyone can help with this, please let me know. I have worked very hard on this model, and would like some possible way to circumvent the above from happening. I leave it now to the people of this wonderful forum to help me figure this out. Thank you. Communion
Alright! I believe I have SOLVED this bug. Here is a workaround if the above "ghost material" syndrome starts to happen to your complicated color splits in .3ds imported props that get hosed on reload: Import the .3ds object placed where you want. Export the file to obj. with only the prop selected in the heirarchy editor. Then open it in Compose, and give each material in the object a name unique other than, 'Material_1, Material_2 etc.' The name 'Material' seems to be the issue here. Then click on all objects, and choose "split by surfaces." Then re-save the file to the same .obj, and reimport the model with all options unchecked. This seems to be a solid fix, as now Maul's saber color and transparency settings are maintained through character changes, and in a scene reload. Thanks for the input. I should have the Ultimate Darth Maul ready to upload to my site sometime tomorrow. I will post again when I have done so. Communion
This should work in Poser 3, I don't see why not, as he is based on the Poser 3 nude male, with lots of reworking, and many additions that were from other sources, I just brought all of them together, and reworked the texture map to DEATH to get it to map properly on the face. However, this has not been tested in Poser 4, and may give an error that a new version # was expected. Since the lightsaber has a transparent texture that only Poser 4 can translate, I believe that Poser 3 will attempt to parse the file anyway. Someone please correct me if I am wrong here. Should post him to my site this evening. By the way, Compose ROCKS! Communion
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.