Wed, Jan 8, 5:42 PM CST

Renderosity Forums / Poser Python Scripting



Welcome to the Poser Python Scripting Forum

Forum Moderators: Staff

Poser Python Scripting F.A.Q (Last Updated: 2024 Dec 02 3:16 pm)

We now have a ProPack Section in the Poser FreeStuff.
Check out the new Poser Python Wish List thread. If you have an idea for a script, jot it down and maybe someone can write it. If you're looking to write a script, check out this thread for useful suggestions.

Also, check out the official Python site for interpreters, sample code, applications, cool links and debuggers. This is THE central site for Python.

You can now attach text files to your posts to pass around scripts. Just attach the script as a txt file like you would a jpg or gif. Since the forum will use a random name for the file in the link, you should give instructions on what the file name should be and where to install it. Its a good idea to usually put that info right in the script file as well.

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



Subject: Drop to Floor Problems


grichter ( ) posted Mon, 09 January 2012 at 3:39 PM · edited Tue, 10 December 2024 at 6:14 PM

When I run the following pz2 which calls a script since the upgrade to PP2012 SR1, V4 which is the only character that seems to have the problem (V3. M3, M4 all work as expected) goes negative y -10320000.000000. Same occours if I run just the drop to floor script from the scripts menu.

Anybody got a clue why this is haywire all of a sudden?

Thanks in advance for any assitance.

 

{
version
    {
    number 6
    }

actor BODY
    {
    channels
        {
        valueParm SCLS4Short
            {
            keys
                {
                k 0 0.400
                }
            }
        }
    }
runPythonScript ":Runtime:Python:poserScripts:ScriptsMenu:Utility:dropFigToFloor.py"    
}

which calls this script

scene = poser.Scene()

actor = scene.CurrentActor()
actor.DropToFloor()

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"


semidieu ( ) posted Mon, 09 January 2012 at 4:09 PM

And does it occur the same if you drop to floor using the Figure menu from Poser ?

And what is the actor selected before running the script ?


grichter ( ) posted Mon, 09 January 2012 at 10:03 PM · edited Mon, 09 January 2012 at 10:05 PM

Yes the actor is selected and the figure menu drop to floor works as expected, But the value gets stuck at-10320000.000000 if you do it after running the script. You get the character back in the scene instead of 10,320,000 poser units below the poser ground plane. But the value shows -10320000

I have a bunch of scripts I wrote to create charatcers for various scenes, where I either use the SP4 proprotions on V4 of via proprogating scalling to change their physical height, etc of other characters and load texture maps, and morphs, etc.  They all include a drop to floor at the end of the character creation script. Agian only the V4 characters have the problem.

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"


markschum ( ) posted Mon, 09 January 2012 at 11:55 PM

what display units are you using ? 


grichter ( ) posted Tue, 10 January 2012 at 6:16 AM

Poser Units

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"


EnglishBob ( ) posted Sat, 14 January 2012 at 5:16 AM

Sorry, I have nothing useful to contribute - but that offset value is interesting, given that 1 PNU = 103.2 inches. I can't figure what the connection is, if any. Just a bug in actor.DropToFloor(), most likely.


grichter ( ) posted Sun, 15 January 2012 at 10:16 PM

I am beginning to believe it is a scaling issue. All the V4 characters that have problems have the SP4 proportions morph injected, and set from .1 to .5 in the various cr2's I load. Don't hold me to that, still messing around.

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"


markschum ( ) posted Sun, 15 January 2012 at 10:37 PM

I wonder if changing to box tracking would reveal anything interesting ?


grichter ( ) posted Sun, 15 January 2012 at 10:49 PM

Quote - I wonder if changing to box tracking would reveal anything interesting ?

 

No difference

Gary

"Those who lose themselves in a passion lose less than those who lose their passion"


lesbentley ( ) posted Sun, 18 March 2012 at 2:29 AM · edited Sun, 18 March 2012 at 2:30 AM

Check yTran of the Body, before and after running DTF, does it change?

Also, if there are any body handles involved, that could be a cause.

Another suspect could be the V4 native magnets. This is just a wilde guess, but it's one thing that V4 has, and most other figures don't. Yet another suspect might be that the hidden bodyMoprphs actor is involved in some way.


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.