Mon, Jan 20, 12:59 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 20 11:41 am)



Subject: Victoria 4.2 eyes wont close or open???


MrFiddles22 ( ) posted Sun, 29 June 2014 at 3:37 AM · edited Mon, 20 January 2025 at 12:56 PM

Anybody know what the issue is with Victoria 4.2 eyes morph dial not opening or closing the eyes when adjusted in Poser Pro. The left and right close/open doesn’t work either?
I have seen other posts about this, but no real fix was mentioned. Tried a complete uninstall and reinstall of both Poser and Daz and deleting and reinstalling their content libraries, but the problems still remains.


hornet3d ( ) posted Sun, 29 June 2014 at 4:05 AM

I use Poser Pro 2014 and V4WM and the eye morph dials work correctly, they also worked in Poser Pro 2012 so I do not think it is a Poser Pro issue.  Did to re-initalise V4 when you reinstalled?

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.


MrFiddles22 ( ) posted Sun, 29 June 2014 at 4:19 AM

Quote - I use Poser Pro 2014 and V4WM and the eye morph dials work correctly, they also worked in Poser Pro 2012 so I do not think it is a Poser Pro issue.  Did to re-initalise V4 when you reinstalled?

Thanks for youe reply. I'm not quite sure how to "re-initialize" the character, can you explain what that is? Thanks


xen ( ) posted Sun, 29 June 2014 at 6:16 AM

This is a recurring problem. Here is another thread:

http://www.renderosity.com/mod/forumpro/showthread.php?message_id=3632332&ebot_calc_page#message_3632332

 

The solution is discussed here on this RDNA thread:

http://forum.runtimedna.com/archive/index.php/t-64299.html

 

It fixed the problem for a while for me, but the problem came back.

 

If someone could make an inject pose to reenable the blink morphs that would be most helpful.


hornet3d ( ) posted Sun, 29 June 2014 at 7:44 AM

A quote from R Hasletine in another thread although it has been mentioned elsewhere.

"Remember, if manually installing, to run the RuntimeLibraries!DAZDzCreateExPFiles-v4.bat (or Mac equivalent after extracting the files or Poser won't know to load the new morph channels. Also, if you are using Windows Vista or later the content should not be installed to the application folder."

The thread was on a different subject but the above does decribe what to do when V4 is installed manually.  It may not be the solution to your problem but worth knowing I think.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.


xen ( ) posted Sun, 29 June 2014 at 8:05 AM

It is useful to know about re-initialising, but that didn't fix it for me.

I have just started on a fix injection myself and it works half way at least.


hborre ( ) posted Sun, 29 June 2014 at 8:43 AM

Does everyone have the latest version of V4?  The files have been updated several times with fixes.  I would suggest resetting your DAZ account and redownload Vicky.


WandW ( ) posted Sun, 29 June 2014 at 10:14 AM

You don't need to reset the downloads any more, just download it from the Product Library in your DAZ account.

Keep in mind that the zip files DAZ now uses don't have runtime in the root directory; the runtime folder is within the Content folder of the zip, so you will beed to browse the zip file, or unzip to an empry folder and drag the runtime folder where it needs to go.  Note that you will need to reinitialize V4 as noted above after installing V4 and her morph packages...

----------------------------------------------------------------------------------------

The Wisdom of bagginsbill:

"Oh - the manual says that? I have never read the manual - this must be why."
“I could buy better software, but then I'd have to be an artist and what's the point of that?"
"The [R'osity Forum Search] 'Default' label should actually say 'Don't Find What I'm Looking For'".
bagginsbill's Free Stuff... https://web.archive.org/web/20201010171535/https://sites.google.com/site/bagginsbill/Home


MistyLaraCarrara ( ) posted Sun, 29 June 2014 at 11:47 AM · edited Sun, 29 June 2014 at 11:53 AM

you're loading a fresh vicki from the daz people folder? 

blink is a base morph.

iirc, the !daz morphs folder can only be in one runtime

 

do you have a cr2 editor? might have to look under the hood for a level3 diagnostic.  she's a big file to open in wordpad.

 

head scr'ch ... i don't understand how the library figure can be broken.  i can imagine losing a morph in a customized v4 character saved to the library, but the original figure?



♥ My Gallery Albums    ♥   My YT   ♥   Party in the CarrarArtists Forum  ♪♪ 10 years of Carrara forum ♥ My FreeStuff


MrFiddles22 ( ) posted Sun, 29 June 2014 at 3:54 PM · edited Sun, 29 June 2014 at 3:55 PM

Wow a lot of advice on this. (The "Victoria 4.2 Morphs++" file seems to be the issue)

After some trial and error, it seems there is an issue with the "Victoria 4.2 Morphs++" file. Because when I use DAZ Install Manager, and uninstall it, she suddenly can blink, and when I reinstall it she can't blink. And of course you loose a lot of functionality of the morphs without this download/file.

I wonder what part of this file is causing the problem?


MrFiddles22 ( ) posted Sun, 29 June 2014 at 11:08 PM

Quote - The solution is discussed here on this RDNA thread:

http://forum.runtimedna.com/archive/index.php/t-64299.html

 

 

I saw this too, I looked over the post again, and tried editing the dependencies. It seems to work, but needs some tweaking. I'll have to test it out. I'll guess editing the dependencies is the best option for now if you want to have the morphs++ file installed and eyes blink. Thanks.


xen ( ) posted Mon, 30 June 2014 at 12:44 AM

head scr'ch ... i don't understand how the library figure can be broken.

I know. Weird, but seems to happen to lots of people.

I saw this too, I looked over the post again, and tried editing the dependencies

Tell me if you want to help to get that inject script to fix it


MrFiddles22 ( ) posted Mon, 30 June 2014 at 4:10 AM

Quote - > head scr'ch ... i don't understand how the library figure can be broken.

I know. Weird, but seems to happen to lots of people.

I saw this too, I looked over the post again, and tried editing the dependencies

Tell me if you want to help to get that inject script to fix it

If you have somthing that helps, that would be great. Is the script a custom one you made?


jestmart ( ) posted Mon, 30 June 2014 at 10:54 AM

The number one reason morphs stop working on V4 or any of DAZ's generation 4 figures is having them installed to more than one runtime.  Avoid headaches by creating a unique library folder for them and point the installer(s) and Poser to that library folder.


hornet3d ( ) posted Mon, 30 June 2014 at 12:33 PM

Since Pose 6 I have had a seperate Runtime for V4 which may explain why I have never seen the problem.

 

 

I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 -  Ryzen 9 5900HX, with 64 gig ram and 3 TB  storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU .   The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.


WandW ( ) posted Mon, 30 June 2014 at 1:27 PM

Quote - Since Pose 6 I have had a seperate Runtime for V4 which may explain why I have never seen the problem.

Just get rid of whatever V4 stuff you recently installed and add the v4 runtime to the Poser Library as an external runtime.  I've been using the same V4 runtime since Poser 7...

----------------------------------------------------------------------------------------

The Wisdom of bagginsbill:

"Oh - the manual says that? I have never read the manual - this must be why."
“I could buy better software, but then I'd have to be an artist and what's the point of that?"
"The [R'osity Forum Search] 'Default' label should actually say 'Don't Find What I'm Looking For'".
bagginsbill's Free Stuff... https://web.archive.org/web/20201010171535/https://sites.google.com/site/bagginsbill/Home


xen ( ) posted Mon, 30 June 2014 at 3:09 PM

This all sounds like sage advice, however I still got the blink problem with a single runtime, and after re-initialisation. I filed a ticket at DAZ ages ago, but they didn't know how to fix it.


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.