uncle808us opened this issue on May 11, 2010 · 10 posts
uncle808us posted Tue, 11 May 2010 at 9:44 AM
Is there a script or something that can speed up adding materials to spawned props? I find it tedious to import a prop, spawn props, then have to go thru all the props to add materials. Thanks.
MacBook Pro OSX El Capitan Ver 10.11.6
ockham posted Tue, 11 May 2010 at 9:50 AM
If the 'offspring' are all going to be the same, you could just set up one by hand,
save as MC6, then apply the MC6 to the others. I doubt that any script could
do the job noticeably faster than that, unless you wanted to have a specific pattern.
(For instance, spawning 30 flowers from a plant and setting their colors to random
values....)
uncle808us posted Tue, 11 May 2010 at 10:00 AM
What I'm talking about is a building with say 20 props door,window,roof,beams,nails,etc. When I import the prop all the textures are there but, after spawning the props I have to go into the material room and redo all the materials. tedious...
MacBook Pro OSX El Capitan Ver 10.11.6
parkdalegardener posted Tue, 11 May 2010 at 11:42 AM
Quote - What I'm talking about is a building with say 20 props door,window,roof,beams,nails,etc. When I import the prop all the textures are there but, after spawning the props I have to go into the material room and redo all the materials. tedious...
Have you looked at BB's VSS. He used it to texture a house made from many dozens of props but loaded the shaders on them with one click. Most people use it only for skin as BB placed an excellent skin shader in the package but it's way more useful than that.
pdg
uncle808us posted Tue, 11 May 2010 at 11:56 AM
Is this for cr2's or for pp2's?
MacBook Pro OSX El Capitan Ver 10.11.6
Pengie posted Tue, 11 May 2010 at 4:11 PM
I think the priority should be finding out why the materials are being lost in the first place. Have you tried saving the imported prop to the props library, deleting it from the scene, and loading the new prop from the library before spawning the components?
Pengie posted Tue, 11 May 2010 at 4:31 PM
An experiment that I did just now:
I copied a folder containing a Waveform OBJ and its textures into the RuntimeTextures folder, and imported the OBJ. That caused the texture references to be reasonable for the prop. I saved the prop to the library and restarted Poser. The prop loaded with textures in place, and the references look correct in the PP2 file. I created a polygon group and spawned a prop. The new prop was correctly textured.
uncle808us posted Tue, 11 May 2010 at 4:41 PM
You put the .obj file and the textures into >runtime>textures or just the textures?
Oh yeah. This sounds exciting have to wait till tomorrow though. Man If this works it will be great. Thanks
MacBook Pro OSX El Capitan Ver 10.11.6
Pengie posted Wed, 12 May 2010 at 6:19 AM
I put both. OBJ format imports like their textures in the same directory as the geometry. Also, when I've made props in the past I've made bad texture references that bit me later, so I thought I'd eliminate that problem. Once a prop is in the library, the copy of the geometry can be deleted from Textures.
I was thinking that, since some unfamiliar bug involving textures was popping up, maybe there was bad internal data being generated when the OBJ or other geometry was imported that didn't show up until new props were spawned.
uncle808us posted Wed, 12 May 2010 at 9:14 AM
Yes it worked creating (single new props) but did not work with (Spawn props) but that still is an advantage. I thank you for the knowledge. Thanks.
MacBook Pro OSX El Capitan Ver 10.11.6