V4 eyes don´t close



  • Here's what I get

    PHMEyeCloseTopR rEye Up-Down 0.0333329997957
    PHMEyeCloseTopR Head EyeLidTopUp-DownR 0.0333329997957
    PHMEyeCloseBottomR rEye Up-Down -0.0166660007089
    PHMEyeCloseBottomR Head EMPTY-Happy 0.490999996662
    PHMEyeCloseBottomR Head EMPTY-Sad 0.70300000906
    PHMEyeCloseBottomR Head EMPTY-Afraid 1.0
    PHMEyeCloseBottomR Head EMPTY-Disgusted 0.675999999046
    PHMEyeCloseBottomR Head EMPTY-Angry 0.365000009537
    PHMEyeCloseBottomR Head EMPTY-Surprised 0.437000006437
    PHMEyeCloseBottomR Head EyeLidBottomUp-DownR -0.0166660007089
    PHMEyeCloseTopL lEye Up-Down 0.0333329997957
    PHMEyeCloseTopL Head EyeLidTopUp-DownL 0.0333329997957
    PHMEyeCloseBottomL lEye Up-Down -0.0166660007089
    PHMEyeCloseBottomL Head EMPTY-Happy 0.612999975681
    PHMEyeCloseBottomL Head EMPTY-Sad 0.279000014067
    PHMEyeCloseBottomL Head EMPTY-Afraid 0.709999978542
    PHMEyeCloseBottomL Head EMPTY-Disgusted 0.824000000954
    PHMEyeCloseBottomL Head EMPTY-Angry 0.490999996662
    PHMEyeCloseBottomL Head EMPTY-Surprised 0.194000005722
    PHMEyeCloseBottomL Head EyeLidBottomUp-DownL -0.0166660007089



  • So yeah, the deltas for these four should be 2 and -2, like the stuff in the links said (F$%^ING EDIT TIMEOUT AGAIN ! Ijust wantedto highlight those four lines in the previous post!)
    PHMEyeCloseTopR Head EyeLidTopUp-DownR 0.0333329997957
    PHMEyeCloseBottomR Head EyeLidBottomUp-DownR -0.0166660007089
    PHMEyeCloseTopL Head EyeLidTopUp-DownL 0.0333329997957
    PHMEyeCloseBottomL Head EyeLidBottomUp-DownL -0.0166660007089



  • @3dcheapskate these probably mean that there are typos in the ERC injection file :Victoria 4:Runtime:libraries:!DAZ:Victoria 4:head:05-ps_pe069_DAZ_ERC.pz2. Mine's timestamped 20080209. Looking at the file, it has:

    		targetGeom PHMEyeCloseBottomL
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidBottomUp-DownL
    			deltaAddDelta 2
    			valueOpDeltaAdd
    				Figure
    				lEye:1
    				xrot
    			deltaAddDelta -0.016666
    			}
    		targetGeom PHMEyeCloseBottomR
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidBottomUp-DownR
    			deltaAddDelta 2
    			valueOpDeltaAdd
    				Figure
    				rEye:1
    				xrot
    			deltaAddDelta -0.016666
    			}
    		targetGeom PHMEyeCloseTopL
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidTopUp-DownL
    			deltaAddDelta -2
    			valueOpDeltaAdd
    				Figure
    				lEye:1
    				xrot
    			deltaAddDelta 0.033333
    			}
    		targetGeom PHMEyeCloseTopR
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidTopUp-DownR
    			deltaAddDelta -2
    			valueOpDeltaAdd
    				Figure
    				rEye:1
    				xrot
    			deltaAddDelta 0.033333
    			}
    

    which are the relevant value operations.



  • And mine (timestamped 2015, probably my most recent reinstall of everything) looks identical. The deltas for slaving to the 'PHMEyeLid...' dials are +/-2 as they should be. So that's not the problem. It looksto meas ifit's actually using the deltas for the xrots...

    		targetGeom PHMEyeCloseBottomL
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidBottomUp-DownL
    			deltaAddDelta 2
    			valueOpDeltaAdd
    				Figure
    				lEye:1
    				xrot
    			deltaAddDelta -0.016666
    			}
    		targetGeom PHMEyeCloseBottomR
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidBottomUp-DownR
    			deltaAddDelta 2
    			valueOpDeltaAdd
    				Figure
    				rEye:1
    				xrot
    			deltaAddDelta -0.016666
    			}
    		targetGeom PHMEyeCloseTopL
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidTopUp-DownL
    			deltaAddDelta -2
    			valueOpDeltaAdd
    				Figure
    				lEye:1
    				xrot
    			deltaAddDelta 0.033333
    			}
    		targetGeom PHMEyeCloseTopR
    			{
    			valueOpDeltaAdd
    				Figure
    				head:1
    				PHMEyeLidTopUp-DownR
    			deltaAddDelta -2
    			valueOpDeltaAdd
    				Figure
    				rEye:1
    				xrot
    			deltaAddDelta 0.033333
    			}
    


  • *F&^ING EDIT TIMEOUT !
    It looks to me as if it's actually using the deltas for the xrots... see the picture I posted a short while back, and note the values that I've put red Xs against



  • THIS IS BEYOND A F#$%ING JOKE ! Not only does it tell me the edit has timed out, but I can't get what I just typed back !
    (and I'd better not start typing again in this post because that's an edit and it will timeout too.)



  • @trekkiegrrrl The problem normally shows up after one applies poses to V4, particularly 3rd party poses.



  • @will_i_am So are you suggesting folks close V4's eyes BEFORE applying a 3rd-party pose? Will that prevent this issue from occuring?



  • The PHMEyeCloseTopL/R are 0.017 (which is half of 0.033333), and PHMEyeCloseBottomL/R are 0.008 (which is half of 0.016666) - and the half is the 0.5 that I had set EyesOpenClose to.

    And... relaaaaxxxxx ! ;o)



  • @miss-b No. My primary "fix" as always been "V4 unhide eyes" then if necessary adjusting the dependency parameters.



  • @will_i_am Ahhh, OK.



  • I just found that EyesSquint (a dial under Head-Morphs/Expression-Base) works when EyesOpen does not. Maybe not a perfect solution, but good enough for what I'm doing now.



  • @3dcheapskate the trouble is, if you're loading a saved V4 from the library, that may already have it's valueOperations screwed up.

    The only time the ERC poses from the !DAZ hierarchy are used, is when a base V4 with readScript lines calls on the contents of the !DAZ hierarchy files to build a V4 while it's loading. If there was a problem with that process, and the figure was saved back to the library, what you get next time will preserve the problem, whether it's subsequently been fixed in the hierarchy files or not. Your source file looks correct, but unless you start with the base V4 loader, or a known correct figure loaded from the library, you will keep getting this problem.

    If you have a text editor that can cope with gzip compressed files (BBEdit on macOS or Notepad++ on Windows), in case any of your library is in compressed format, you can try opening the .cr2 file with a problem you are loading from the library and search for that PHMEyeLidBottomUp-DownL line. It shouldn't appear in more than a few places, and unless it's completely missing from PHMEyeCloseBottomL valueOperations, you could even fix the deltaAddDelta value then and there. The same for all the others. That way you'll know that file will work every time you load it.

    Generally speaking, applying poses to figure should NOT be adding or modifying value operations (though pose files can do so). If your figure can blink before you load the pose, and then not blink after the pose is applied, bin the pose file and complain to the vendor (or just open it and look for any valueOp lines and delete them yourself).



  • @willshetterly That would be a quick fix, but not satisfying, if you want some realistic blink effects in your animation. I´m experimenting with some of your suggestions and at the moment it seems, that the best solution is to: Load the 4.2 figure, set EyesOpen-Close to -1 (wow, the eyes close like they should :)) and inject the morphs after that. The eyes keep closed, while the morphs are loaded. Seems to work pretty good!



  • @anomalaus It's the V4 in my PP2014 'preferred state' that was screwed. I removed her and set the preferred state, then added her back and set the preferred state again. Her eyes close fine now.
    So maybe before saving any scene with V4 in it, or setting a 'preferred state' with V4 in, or saving a CR2 including V4 you should always ask her to blink once just to check her eyes are okay ? ;o)

    (note: this Oct2014 DAZ forum post, linked from post 11in the CGBytes thread recommends changing the deltas of the xrots to +/-2, which sort-of confirms what I thought)

    P.S. My apologies to everybody reading this thread for losing my temper yesterday !



  • @3dcheapskate glad you solved the source of the problem. :-)

    I do so much continuous development of V4, I don't trust any file saved back to the library as anything other than a source of deltas for new morphs I create, which I then incorporate back into my own parallel version of the !DAZ hierarchy. It's very time consuming, especially when I need to propagate morphs to multiple conforming clothing figures. However, the consequence of chopping everything up into chunks which match the DAZ hierarchy (except for the morph injection structure, which I don't bother with for clothing items), is that I can have lightweight figure files which readScript in not only the base figure, but conforming clothing and corresponding fitting poses.

    Every time I start a new scene and load V4 figures (haven't got around to doing the same to any other one, though I may go that route with PE, despite a lesser incentive), I know I have the latest mods and morphs and won't have legacy issues unless I've stuffed something up. If I want different clothing, or a different skin texture, everything's modularised, so I just need to create a new combination file which incorporates all of the components via readScript: objects (for base figure, props and conformers), base figure definition {actors (body parts, props and deformers), figure block with extracted texture selected by readScript], default pose and expression for base figure, then figure+texture definition and fitting pose for each of the conformed clothing items.

    With a standard figure+clothing set, I can create folders of multi-figure pose files, which use tiny python scripts to incrementally select the next figure in the scene, between loading base figure and fitting poses for the known clothing items. One double-click and everything gets posed. Run a different script, and I can have it load an entire folder of such poses, one frame at a time, for a complete sequence.



  • I used to have the problem until I had to install Aiko 4. This was because I didn't check requirements on a Character I bought which is 'cos I'm hard of thinking. Since then if I inject A4 the eyes work fine. Also some of the Expression packs I had bought over the years (Ironman13 and Tempesta3d from memory) were much improved. It appears A4 brings a load of expression morphs to the table. Still if you can fix it without spending any beer tokens, then that's always a bonus.



  • Here is the solution which works best for me:

    1. I made a reinstallation of V4 (you don´t have to do this, I just wanted to be sure)
    2. Open: My DAZ 3DLibrary\Runtime\libraries!DAZ\Victoria 4\head: 05-ps_pe069_DAZ_ERC.pz2 with an editor like notepad.
    3. Change this four parameters:
      targetGeom PHMEyeCloseBottomL, deltaAddDelta -2
      targetGeom PHMEyeCloseBottomR, deltaAddDelta -2
      targetGeom PHMEyeCloseTopL, deltaAddDelta 2
      targetGeom PHMEyeCloseTopR, deltaAddDelta 2
    4. Save the file.
    5. Open the Victoria 4.2 figure from the DAZ people folder. She is able to close her eyes now :)
    6. Inject the morphs that you need.
    7. Rebuild your model, I used a pose for that. Then you just have to load the right textures and hair and you´re done!

    Here is my result:
    0_1536837219257_BlackwomanEyesClosed.png
    Thank you all for your help!!!



  • @steve_vaii can you confirm what the deltaAddDelta values were before you changed them?



  • @anomalaus Before they were:
    -0.016666
    -0.016666
    0.033333
    0.033333