Hold out Lady Paintalot! Rescue is near!

Actually, a wxPython script I dangled together the last days. It's not the most elegant one, but it should be OK for now. It should work alike on an MS-Windows-PC AND a MAC.

Still trying to implement some additional features into the script, but since this is my first attempt od a wxPython script, it take some time until I Googled for useful code snippets and made them work.

For more details, look at the SM Poser forum thread

https://forum.smithmicro.com/topic/7939/mat-preset-to-change-only-colors-on-a-blender-node/17#

• Special thanks to @ironsoul for his code examples:

This is exactly what I need to improve my knowledge, because I can look at thes code and see how it's actually done! Most other "examples" found in the InterWebs are far from useful because they are too abstract.

Thank you ALL for helping us!

Karina

That what I intended with this setup. Since I never saw the "Custom_output_" nodes used in any texture I ever saw, so I just tried it and it works.

Fortunam temptare...

K .

@ ironsoul:

What do you think about my solution?

http://sasha-16.forumprofi.de/showthread.php?tid=93&pid=605#pid605

The drawback is that it's still in tkPython, but I don't know any better yet. What do you think?

Cheers! K

Thanks for the nice preview! You ain't a painter in real life, perchance? :D

For a possible solution, please look at your other thread at SM Poser Forum

HTH Karina

Sorry to hear about your problems @shinner.

However, with an estimated 10000+ Poser users (that's a very cauteous guess!) for whom the library works fine, did you ever consider that there might be something wrong AT YOUR END?

This always remembers me of the countless "pass don't work!!1!" comments for archives on certain "chan"s:

obviously the pass works fine for tens of thousands of people, yet those few people still insist that by magic the pass only is wrong for them, even though the pass sometimes is as simple as "#pass123#" - really! Often the reason is that they can't do a simple mark/copy/paste...

So if you're still the odd man out with a problem:

• Have you ever considered that there might be something wrong ON YOUR END?

• Did you try a fresh Windows install, without all the fancy "add-ons" that most of the time do more harm than they are of use?

• Do you actually run the latest versions of hardware drivers, and software add-ons needed?

• DO you know how to "computer"?

Sorry mate, but I think it's YOU who must do some homework before asking to be breast-fed by people who have better to do. Especially since you just cried "don't work!!1!" without supplying us any details about your rig' specifications and other details.

Good Luck! Karina

That's due to (another) Poser inconsistency in the files.

Go to Poser's main program directory: (For other versions replace the "Poser Pro 2010" part by YOUR version's path!)

Program FilesSmith MicroPoser Pro 2010RuntimeGeometriesBalance

This folder "should" contain a file "com.obz" which is nothing more than a compressed (zipped) version of the "com.obj" file.

Unzip it to create the "com.obj" file in the same directory. I'd also advise to (just in case) also COPY that file to Program FilesSmith MicroPoser Pro 2010RuntimeGeometries to create a duplicate in the "Geometries" folder.

That should solve your problems

Karina

wolf359 posted at 11:24AM Fri, 27 April 2018 - #4329034

Ah! Finally the other member of the Troll duo has arrived! I'm amused.

Though I won't reply to any of your ramblings MISTER @MaleMedia.. You're only here to stir up shit in company with your pal @woof359", and I won't support yous in your'se "mission"

Now please SOAD.

Karina

wolf359 posted at 3:20PM Tue, 24 April 2018 - #4328823

What of the much anticipated Project E??? is she not the new Default Poser female..after the "outsourcing" of her is settled and the content comes flooding in??

Sorry >@woof359<, but how does this concern you, as a DAZ vendor? Just another try to stir up shit as you like to do?? Until i've got an explanation I'll consider your post as what it is - TROLL JUNK. -K-

You're right, negative values can be problematic esp. if you don't do the maths correctly (minus times minus equals plus, remember) So better avoid negative values at all.

To start with, create all your lights with a strength of 1(100%), then hook them to your main "light switch" by the four "valueOpTimes" lines as shown in my previous post.

After that you can switch all your lights on or off with your "light switch" (which, of course, is only a master dial in your control prop)

If you've come to this point and made sure that it works OK, then you can set individual lights to individual brightnesses as you wish (in the lights' individual settings). The light strength (or on/off) will still be controlled by the master dial because 10% of 100% light is 10% light, 10% of 10% light is 1% light, and 0% of all that is ALWAYS 0% light, thus, DARKNESS :)

That's the advantage of the "valueOpTimes" method because you don't have to fiddle with "valueOpDeltaAdd" numbers which are relative to the individual setting and can easily produce even negative values...

LATER:

After you've made yourself familiar with this method you can even add more "master control" dials to control groups of lights individually, e.g."all lights on left" or "all lights from above" etc.

The possibilities are endless, and it's so easy once you've understood the method. Unfortunately you can't do this directly in older Poser versions, so you must do it by directly editing the scene file as shown in my previous post. IT COULD work in Poser11 because from what I've read about it you can now also add "valueOpTimes" operators from within P11. But as said, I don't know.

Good Luck!

Karina

Now this is really strange, because my method should work under any circumstances.

My only guess is that there are some dependencies in your document that somehow went bonkers.

Make a backup of your file, delete ALL dependencies that you can get hold of (use Poser for this), save it and then try to apply the code lines that I've suggested above to your document (in PoseFileEditor if you have!).

One of the main problems with lights is that if they do have a preset value in the lights parameters themselves,you may get weird results with "valueOpDeltaAdd" if you don't calculate the "deltaAddDelta" correctly!

Even with "valueOpKey" it may become complicated if you don't set all keys (esp. min and max values to the correct values, and it even becomes harder because the curve from one key to the next is interpolated as a bezier curve ~~~ by the program, which may oveshoot or undershoot the correct values for any settings in between.

_In short, you're about to open a can of worms here! _

Especially if you don't eradicate all the other (probably wrong) dependencies that you already have in your document.

Karina

A more elegant method would be the "valueOpTimes" function which would even provide you with a dimmer, as well as avoiding the other problems.

First, make sure the light's intensity is set to 1 (=100%)

Then modify the code like this: (lines starting with // are comments and must not be added to the code)

// look for your light and go to the "channels" section:

channels
{
    // groups declarations...
    // and some variables follow...
    // ...
    // you are looking for THIS:
    kdIntensity KdIntensity
    {
        name INTENSITY
        initValue 1  // default value, set this to 1 !
        // some more lines of code, ignore...
        // ...
        keys
        {
            k  0  1  // make sure the second number is 1 which equals 100% brightness
        }
        interpStyleLocked 0
        // now add these four lines, directly below the interpStyleLocked 0:
        valueOpTimes
        _NO_FIG_
        LightSwitch  // *internal* name of your light switch prop
        LightsOn  // *internal* name of your light dial
    }
    //  more code, ignore...
}

When the "LightsOn" dial is at 0.0 the light is OFF.

When it's at 0.5 the light is at 50% brightness, and ON

When it's at 1.0 the light is at 100% brightness, and ON

When it's at 1.5 the light is at 150% brightness, and ON

etc.

Maximum flexibility, ease of use.

Cheers!

K

(Shameless self promotion to follow :D )

Try THIS weight mapped V4 instead and see if the (customized) morph injections work for you:

http://sasha-16.forumprofi.de/showthread.php?tid=2

If you still have problems even with SASHA you've probably installed some of your V4 content files into some wrong folders. You're welcome to ask for further help in SASHA's forum.

Good luck! Karina

I didn't try this, but who knows:

If (in Poser's Hierarchy Editor) you parent a prop (manually) to UNIVERSE (i.e. unparent it from the figure), it's real coordinates are shown in the prop's parameters.

Maybe unparenting the prop in Python, then reading it's (hopefully) RW-coordinates and finally reparenting it to it's original parent could do the trick?

Karina

Hello shed_e, use the "Pose Writer Panel" by PhilC. It comes with Poser and can be found under the "Scripts" menu. Make sure to have read the (really good) manual to understand the basics (esp. about the location to where the poses are saved.)

Unlike Poser, PWP does include bends induced by master parameters like the "Morphforms" for the hands (and torso too b.t.w). That should solve your problems.

Explanation: In Poser a dial for e.g. limb bend can have two values:

• The "main" value (which is set by directly spinning the dial or moving the body part.
• The "dependent" value which is set by master dials like e.g. the "Morphforms" dials for the fingers, hands and torso.
• The "total value" is the sum of the "main" and the "dependent" value.

Unfortunately Poser does ignore any "dependent" values and only saves the "main" value when writing a pose. PoseWriterPanel writes the pose with the correct "total" value.

HTH Karina

ssgbryan posted at 1:52PM Tue, 16 January 2018 - #4322346

Dealing with Vendor follies or Why we can't have nice things in Poser [-snip-]

THAT!! Signed, stamped, sealed and filed every bloody single line of the rant.

And @ssgbrian's method works! I do so with every new item I aquire, right after I unpacked the ZIP/RAR, and before I copy anything to one of my runtimes. Since then I rarely need the search function of the library at all because everything is in a logical place and easy to locate, in a matter of minutes or even seconds.