Tue, Oct 22, 5:22 AM CDT

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Oct 22 3:39 am)



Subject: Force "Use Limits" on in .cr2 or pose


papillon68 ( ) posted Sat, 25 July 2009 at 6:16 AM · edited Tue, 22 October 2024 at 4:03 AM

Hi, any way to trigger the figure option "Use Limits" alway on for a certain character or pose, so that the user doesn't have to go through the menu and trigger it manually ? Thanks

visit my blog:  www.alessandromastronardi.com

My Rendo Store


lisarichie ( ) posted Sat, 25 July 2009 at 7:58 AM

Create a copy of the original .cr2 file.

Open the copy .cr2 in a text editor, I use Notepad ++,  change  forceLimits 0 to forceLimits 1 and save the file.

Test this revised .cr2 in Poser, the limits applied to the parameter dials should now be recognized.

If everything works properly replace the original .cr2 file with the revised edition. I keep the original in an archive just to be on the safe side.

There is some discussion on the non-zero value  to use (1-4) but I haven't noticed it making a difference so I just change it to 1, nothing has exploded......yet.


ockham ( ) posted Sat, 25 July 2009 at 8:39 AM

I'm pretty sure the 1 versus 4 difference was an urban legend, or possibly
true for some unusual circumstance.  I confess to helping spread the myth,
because I thought I saw the difference.

As far as I can tell (tested carefully in both P4 and P7 right now) the value 1 will
always force the limits regardless of the setting of Figure: Use Limits. 

More precisely, when forceLimits is 0, the figure:UseLimits setting matters. 
When forceLimits has a*ny nonzero value, *the limits are solid.  So 4 won't
make anything explode, but it's no different from 1.

My python page
My ShareCG freebies


lisarichie ( ) posted Sat, 25 July 2009 at 8:56 AM

Ironically DAZ studio will recognize the force limits set on a parameter dial in Poser figures without having to edit the .cr2.....bringing us to: WTF are Poser devs thinking?

Astoundingly blind to require manual editing to activate a parameter value that was set within the native application originally.


papillon68 ( ) posted Sat, 25 July 2009 at 10:21 AM

Well, thank you very much for these precious advices guys !

visit my blog:  www.alessandromastronardi.com

My Rendo Store


lesbentley ( ) posted Sat, 25 July 2009 at 9:16 PM

You can also use a pose file to force limits, eg: {

version
        {
        number 3.0
        }

actor head
        {
        channels
                {
                targetGeom RoundFace
                        {
                        forceLimits 1
                        }

                }
        }
}

The pose can also set the 'min' and 'max' value of the limits, eg: {

version
        {
        number 3.0
        }
actor head
        {
        channels
                {
                rotateY yrot
                        {
                        forceLimits 1
                        min -35
                        max 35
                        }
                }
        }
}


lesbentley ( ) posted Sat, 25 July 2009 at 9:37 PM · edited Sat, 25 July 2009 at 9:40 PM

For P5 and up, you can also make a generic pose file that will force limits on the selected actor, by using "actor $CURRENT", eg: {

version
        {
        number 5
        }

actor $CURRENT
        {
        channels
                {
                targetGeom PBMCC_04
                        {
                        forceLimits 1
                        min -0
                        max 1
                        }
                rotateX xrot
                        {
                        forceLimits 1
                        }
                rotateY yrot
                        {
                        forceLimits 1
                        }
                rotateZ zrot
                        {
                        forceLimits 1
                        }
                }
        }
}


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.