Thu, Nov 28, 3:59 PM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: SET files - This shouldn't work, but it does. Why?


maclean ( ) posted Sun, 13 April 2003 at 6:20 PM · edited Sat, 16 November 2024 at 3:00 PM

I made some SET files which 'set' the position and visibility of figures and their body parts. I've been making all these files affect BODY:1, because I discovered that when they're applied to any figure with the same body part names, they work every time. So, I then tried making one which included body parts from 2 different figures, applied it to one, and it also affected the other. Cool...but why? Here's a shortened version of the SET. --------------------------- { version { number 4.01 } actor BODY:1 { channels { translateX xtran { keys { k 0 -2.092 } } } } actor fill_1:1 { on } actor fill_2:1 { off } actor back_1:1 { off } actor back_1:1 { on } } -------------------------------- The actors 'fill' are part of one figure, and 'back' part of another. No use to anyone who doesn't have the figure, of course, but I wondered if anyone else has tried this, and with what results. mac


EnglishBob ( ) posted Mon, 14 April 2003 at 6:23 AM

Sounds like a semi-useful (?) application of crosstalk to me. I suspect if you had two identical figures, both with 'fill' and 'back' actors, anything you applied to one figure would affect the other also.


maclean ( ) posted Mon, 14 April 2003 at 2:11 PM

Yes, that's exactly what happens. I've been messing around with it, using several figures at a time, and it seems that if you load the actors from separate figures in one SET file and just use a generic BODY:1 header, it runs through the entire hierarchy of every figure, and makes the necessary changes. It could be connected to crosstalk. I still haven't installed my poser 5 yet, so I can't check. mac


maclean ( ) posted Mon, 14 April 2003 at 4:12 PM

I made a MAT with 2 materials, each one from a different figure, and it works, although you have to select the figures separately and apply the MAT to each. The problem is..... the MAT adds the material which isn't in the figure, to the figure, if you know what I mean. I used 'back' and 'front' in the MAT. One figure had a 'back' material, the other a 'front'. After applying the MAT, each figure has a new material appended at the end of it's list, front or back, according to whichever one it DIDN'T have before. The new material doesn't do anything, of course, but if you save the figure, it retains the new material. Mixing materials would be useful to me, if I could figure how to NOT get a new material added. Any suggestions? mac


lesbentley ( ) posted Tue, 15 April 2003 at 6:08 AM

In the case from post #1 do the figures share a parented relationship? If so do you still get the same results if you un-parent them?


maclean ( ) posted Tue, 15 April 2003 at 3:13 PM

Nope, les. They were 2 separate figures, unparented. It didn't occur to me to even try it with parented figures. mac


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.