Please never again pre-define my morph dial limits, minimum OR maximum.  I'm an adult, I can figure out what looks bad and when.

That is all.

-WTB

We really TRIED to get Daz to NOT limit the dials, but you can see how that's gone. I think the problem is there are so many new people who complain something doesn't work when dialed to "10"...LOL!

Be nice if there was a python script out there where we had a menu with a list of dials, and we could select a range, and have "unlimit" applied to them.

Maybe with the new python features in P7 this is possible?

I guess we could bug PhilC and see if he could add it as an addition to poser toolbox?

Way too many people take way too many things way too seriously.

Quote - Please never again pre-define my morph dial limits, minimum OR maximum.  I'm an adult, I can figure out what looks bad and when.

That is all.

-WTB

 

Ahhh, Greg, not having a good day?  Need a hug?  :wub:

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.

I think most seasoned poser users HATE dial limiting, and most noobs love dial limiting, because it makes use easier for them.
I just wish if we have "use limits" unchecked no limiting was implimented, instead of just joint manipluation being limited.

Maybe a future feature request to EF?

Way too many people take way too many things way too seriously.

Have they used the "forceLimits" line? If not just deselect "Use Limits" in the Figure menu.

Talk about on the ball, Phil! LOL!

Way too many people take way too many things way too seriously.

edit the cr2 file and do a global replace of "forcelimits 4" to "forcelimits 0"  and your done

Yes, except it doesn't work.  Morphs still have limits.

The global replace could get dicey for joints and things, I'm just worried about morph parameters.

I have a great idea, how about they just never include them ever again?  That's all.  Just don't do it in the first place.

-WTB

yeah, I think the "use limits" command is over-ridden by forcelimits 4, but not by forcelimits 1.

I'll usually set limits on my products tio maximum useability negative and positive. With a lot of morphs, once you hit a certain point, they become useless.

I'm sure there are some adjustments that could possibly be made beyond the limits I set, but most likely not many, or maybe if they are affecting other morphs not included in my sets.

I'm more in favor of sensible limits. If a dial can be used to 5, 6 or 10, then limit it to that. Don't just limit everything to "1".

Heck, I even double naming some of my morph dials, because in many cases, the end user can then get dual use from them.

Way too many people take way too many things way too seriously.

*"Be nice if there was a python script out there where we had a menu with a list of dials, and we could select a range, and have "unlimit" applied to them."

*Did PhilC's suggestion work %100? 

If not, Ockhams the man.  He wrote a script called Limitmorphs.py, to help my with work with Bushi's FaceRandomizer.py, so I would'nt get such wild results using a lot of MTs.  I did'nt see it on his python index, but I still have my copy, as well as his permission to share.  If anyone would like it, just drop me an IM with your e-mail, and a promise to thank Ockham!

Sounds like a script worth preserving.. so many things just fade away with time...

Way too many people take way too many things way too seriously.

Just a word o' warning - especially if this topic is directed at V4:

If you actually change the limit values (min/max), you may also be affecting master-slave relationships.  WTB, you should be keenly aware that a slave dial (with valueOp...) cannot be set past its min or max values by its master dial(s).  VK clued me in to this and experiments definitely bear this out!

In other words, changing min and max for a dial willy-nilly and inconsiderate of possible slaving of that dial could end you up with a whole bunch of strange behaviour.

I mention V4 because if you look inside the CR2, there are thousands (!!) of master-slave relationships (just take a gander at the linkParms list in the figure section - you can clamp your jaws back into place now).  ;D

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone

lol yes, I am aware.  That's why the above solution of just uniformily changing all of them in text editor was rejected.

But hey, what in the hell is a LinkParm?  I never noticed them before, nor do I ever use them when making master/slave dials.  It seems like a redundacy.  Any idea?

You could 'sneak up on it' , one dial at a time with the Parameter Settings dialog, test it out - carefully - then put it back to the original limits if it doesn't work out. That would save blind work in a text editor, if you're not trying to change a ton of dials at a time. Or am I being too simplistic? :unsure:

I haven't had any problems screwing with the limits on facial morph targets, even the ones that slave to left and right.  I have changed the values one at a time as needed within poser, which is time consuming and aggravating.  -WTB

WTB, give this a whirl. Save the following text as a python script (I'd call it V4-IncreaseHeadMorphRanges.py). It should only affect head morphs that have an internal name starting with PHM, which is all the head morphs. It will not affect Scaling (SCL), magnet dials (JSM), Control (CTRL) dials, etc ad naseum.

It will set at minimum limit of -10, max limit of 10 - think that will be sufficient? ;)

# Set Greater Range in HeadMorph Limits (PHM)<br></br><br></br>import poser<br></br><br></br>scene = poser.Scene()<br></br>act = scene.Actor('Head')<br></br>parms = act.Parameters()<br></br><br></br>for parm in parms:<br></br>    parmname = parm.InternalName()<br></br>    if parmname[:3] == "PHM":<br></br>               parm.SetMinValue(-10.0)<br></br>           parm.SetMaxValue(10.0)<br></br>

.

Thanks, that's right in the pocket!  Great!.

Still, just have to stress one more time...DAZ, if you're listening...cut it out!

-WTB

I agree, cut it out.

What's the worst that can happen? Reset to default? Hopefully we won't permanently cripple V4 with a failed extreme idea, right?

Working with V4 last few days, I thought I was doing something wrong!  I did not realize that the publisher had set limits.

With EJ or Miki I always get a kick out of seeing what a 'way minus' mixed with a 'way plus' can do.

I wanted to attempt to combine high fitness with high negative emaciation, for instance. Or body builder with negative definition.

The dials don't go very far.

Cut it out.

::::: Opera :::::

Quote - But hey, what in the hell is a LinkParm?  I never noticed them before, nor do I ever use them when making master/slave dials.  It seems like a redundacy.  Any idea?

The LinkParms are an older form of master-slave (before the valueOp... commands).  One big difference is that instead of having variable function values independent of the slave dial's value, the dial values are directly linked.  The other is that this is a two-way connection.  When you LinkParm the eyes' Side-Side rotations, rotating the left affects the right and rotating the right affects the left.  I take it that this is the type of behaviour that DAZ wanted for these connections instead of the other behaviour.

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone

i see, thanks :)