Ok, I discovered that none of my V4 morphs++ sets are working on V4. 

I've been through the forum looking for solutions but so far nothing has worked. 

The innitialize script on the desktop runs, but it doesn't fix anything. 

I've re-downloaded and reinstalled V4 and the morphs++. I ran the innitialize script after reinstalling V4 and again after reinstalling the morphs. 

Everything is installed to my Poser 7 runtime and linked to from 2014's library. 

This doesn't matter though, because she won't work on P7 or on 2014, or even 2012. 

What am I doing wrong? 

Do I have to go in and edit each pz2 file to get it to work properly? 

This is holding me up from completing a client project that I should have had done last week but have been fighting with trying to get V4 to function, so I have to get this fixed ASAP. 

ETA: M4 and all his morphs (seem to) work just fine in all versions of Poser, so the issue is just with V4 it seems.

I'm running windows 7.

Thanks

~Shane

I suspect you have them installed to either Program Files or Program Files (x86) folder.  Those are protected folder in Windows 7 and user content should never be written to them.

They worked before. I've been using win7 for 2+ years now.

M4 and V4 are installed in the same directory. M4 works like he always has, yet V4 has decided not to for some reason.

So what do I do? According to DAZ's readme, the files have to be installed to Poser's main application runtime directory (which is in x86) in order for the "bodyforms" to work. 

~Shane

Sorry - that should have been 'morphforms'. 

From the DAZ readme: 

"As mentioned in the "What's new in Victoria 4.2" section above, "Due to the way Poser reads the ExP files, it is strongly recommended that Victoria 4.2 be kept in the default Poser Runtime. DAZ Studio users can place Victoria 4.2 in an external folder if desired."

The .cr2 file can be moved to an external Runtime, but the files in the Libraries:!DAZ folder should be kept in the default Poser Runtime. If the !DAZ folder is moved to an external Runtime, Poser first looks in the default Runtime, then starts looking through all files on all hard drives for the files. This can take a very long time to complete, as much as 15-20 minutes."

Thing is, it doesn't take but a minute or so for the morphs to load. The dials show up in most body parts, but they dont' do anything. Trying to change any of them to 1.0 reverts back to 0.0 and nothing happens. 

It doesn't seem to matter what runtime I install her to though. I have two 2012 runtimes - one on the desktop, one in my documents. Also have a 2014 runtime in my documents. She doesn't work in any of them. The figure loads, but the morphs won't work. 

The P7 runtime is in the x86 folder under e-frontier where it always has been. M4 and his morphs work just fine from that folder. 

I'm also using a fresh download from DAZ, so file corruption shouldn't be the issue either.

I also don't get why she's suddenly broken. Everything was working fine a month or so ago. 

~Shane

That is out of date.  The ExP system that allows unlimited morph channels is a script call that Poser 6 couldn't do if the files weren't in the main runtime.  Poser 7 up that isn't a problem.  Windows Vista and up added UAC that protects certain folders from being written to.  

It says the default Runtime, which in recent versions of Poser is in the Public/Shared Documents folder (Poser # Content). In any event, Poser 7 SR3 and later don't need the fourth generation figures to be in the default content location - I would advise removing the files from there and installing in an external library. Alternatively you could find the files generated by the updater in C:UsersYouAppDataLocalVirtual StorepathtoRuntime and manually merging the Runtime there with your actual default Runtime (for which you will need admin rights).

Quote - Alternatively you could find the files generated by the updater in C:UsersYouAppDataLocalVirtual StorepathtoRuntime and manually merging the Runtime there with your actual default Runtime (for which you will need admin rights).

I have admin rights - its my machine. 

Are you sure that's the correct path? I can't find the AppData folder. I get to "C:UsersYou" but from there the trail ends. No AppData directory. Unless you mean my documents. I can get to that from the desktop. No admin rights needed. I'm the only one that touches this machine so nothing is passworded. 

~Shane

AppData is hidden - if you enable the display of hidden files and folders in Folder Options>View you should see it.

Gotcha. I always forget about the hidden files crap.

Couldn't I just copy the P7 runtime to another location and link that to 2014? 

And how about removing the UAC thing that's muckin up the works? Or will Windows throw a fit?

~Shane

I don't know if this is related (I'm using P10 on my old XP)

but I had James suddenly quit working (but only with his head morphs) I could move his eyes.

I had to go back to another morphed James that I had saved in the Library. Which was where the character I made originated from.

I dropped in a replacement from that Lib, and it worked fine... morphs worked. Perhaps it was something that happened when I saved the one time? I reopened and checked and the replacement still works.

I believe I still have the James that failed in the old Scene.

I don't know if that's the same with James or not. 

As for V4, there is something that's causing her morphs not to load in PP2014. 

I just had her working in P7 after yet another reinstall. I loaded all her morphs, tested to make sure they were working, and then saved the figure to the P7 Runtime. 

The figure I saved to the P7 Runtime - "V4 Full" - shows up in that runtime inside Poser, and will load, but it doesn't show up in the P7 Runtime via windows explorer. 

So I copied the entire P7 runtime to my desktop, then linked it to 2014's library. I made sure the V4 Full figure was showing in windows explorer. It saved the .cr2, a .pmd file that was over 12mb in size, and the thumbnail. But loading it into PP2014 does nothing. The morph dials are there with their names, but they're empty. 

i suspect this is all due to this UAC crap. How do I remove or disable that? That's the only thing it can be as far as I can tell. Unless someone else has other ideas. 

~Shane

So am I the only one who can't get V4 to work in 2014?

~Shane

I recall you also needed the poser exe just outside of the V4 runtime folder, that was years ago when I was using poser 6... in fact when I recently upped to 10 I imported my runtimes and instinctively replaced the exe's with the newer poser 10 exe's.

Dunno if that might have something to do with it? but still you had them working before... weird.

I was having problems with the morphs++ not working properly in Poser in the past, too.

But I hardly use V4, so it usually didn't bother me that much.   :-)

I'm using Windows 7 Home Premium with UAC disabled and all system files visible. I think between using Firefox with NoScript and ABP and not clicking randomnly on .exe files strangers send me, I'm pretty save and don't need no electronic nanny arguing with me about what I'm allowed to do on my own system.

Anyway...

...Vicky 4 usually gets her knickers in a twist if:

1. The injection and readscript files in the !DAZ folder are compressed

2. There's more than one instance of her installed. (Guess she's the jealous type)

3. A new morph-set wasn't properly "activated"

4. You haven't bought her enough stuff lately.

 BTW, I've installed all DAZ figures in an external runtime called "DAZ Base Meshes"

 (If she refuses, lure her in with a fake "Poser.exe" file.)

A-HA!

I got the b*tch to work by... proxy? Leap frog? I dont know.

Since she decided to behave again in P7, after who knows how many uninstalls/reinstalls, I linked my PP2012 library to P7, made a new folder inside the figures folder there, saved her with all her morphs loaded, into that library. 

But she still wouldn't work in 2014. 

So I loaded her into 2012, then saved her again to the 2014 library, which I also have linked to 2012, then finally was able to load her into 2014 and the morphs seem to be working now. 

I have no freakin clue why this is the only way I could get it to work, but it worked and that's all I care about. 

Yeah Joe, I HATE working with V4 too. I'm only doing this because I've been working on a custom dress for a customer that needs several FBMs in the clothing. I didn't know my morphs++ for her weren't working when I started the project. They were working the last time I built clothing for a customer. I updated 2014 to the most recent SR since then, so maybe that has something to do with it? I don't know. I'm not a coder so I can't even begin to guess what the problem is. 

I did notice that all .pz2 files for the inj's look like the code threw up, so maybe that has something to do with it? I was going to attempt trying to straighten it out until I realized I'd have to do that for all 330 files, and there's no guarantee that would even fix anything. But maybe because the files aren't running down the page, but instead its all one long string of code, 2014 is having issues reading it? Wasn't there a python update/change/something that happened in poser sometime between P7 and PP2014? 

I don't know. Don't care. I got it to work this way that's the important part. 

Maybe this can help someone else that runs into the same problem. 

~Shane

Quote - Gotcha. I always forget about the hidden files crap.

Couldn't I just copy the P7 runtime to another location and link that to 2014? 

Just move the entire Poser 7 directory out of Prgram Files and Poser 7 will still work just fine; just create a new shortcut.

Quote - 4. You haven't bought her enough stuff lately.

 

 BTW, I've installed all DAZ figures in an external runtime called "DAZ Base Meshes"

 (If she refuses, lure her in with a fake "Poser.exe" file.)

LOL! #4... yeah, no kidding.

Good to hear you got things working, and yes, this will be informative for a lot of people trying to kickstart their figures back into action.

Quote -4. You haven't bought her enough stuff lately.

Isn't that the case with most females? lol

Quote - Good to hear you got things working, and yes, this will be informative for a lot of people trying to kickstart their figures back into action.

Odd that more folks haven't run into the same or similar issues, especially since it's V4.

Quote - Just move the entire Poser 7 directory out of Prgram Files and Poser 7 will still work just fine; just create a new shortcut.

I wasn't aware that was possible. I thought that since P7 is a 32-bit program and I'm on a 64-bit system, all the 32-bit programs have to stay in the x86 directory so that windows can access them. 

I have Z-Brush installed in the x86 directory too, as it is still only 32-bits and thats where it installs to automatically. It saves all my work there unless I choose to put it somewhere else. Have never had any problems with it, or any other software. And as I said earlier, I don't even have these problems with M4, or any other figures. Just V4, that temperamental hag. 

~Shane

Don't know if you've already tried below

Believe with pp2012 the configured runtime paths can be found in the LibraryPrefs.xml in the user profile area, don't know if this is the same in pp2014 but this info could be used to double check the pp2014 seach path to make sure there are no duplicate V4 installs (or V4 pz2 files) that could be confusing the search of the runtimes.

Might also be worth looking at the CONTENT_INSTALL_RUNTIME variable in poser.ini for pp2014 and making sure it also doesn't have an unexpected v4 install.

The other thought is how DzCreateExPFiles.exe is locating the runtime. It could just be taking the location from where itself is installed, or it could be using the Daz install path variable "dzContentLastDir" setting from the dzInstall.ini in the DAZ3D user profile directory. If its doing the latter and the path is wrong it may explain why its not working but you say the files are being created so this seems unlikely.

No idea if it was a similar problem or not, but I had V4's morphs++ suddenly stop working on me in PP2012 a while back. Started working again on about the 3rd or 4th reinstall. I was shouting a lot by then so maybe scared her into submission?

Don't know if it matters, or will help, but I have Poser 6, Pro 2010, Pro 2012, and 2014 all installed top level under the C: drive. All the runtimes are installed traditionally (under their respective Poser directories) with file search set for "Deep". V4 is installed under both P6 and PP2012. UAC is disabled. Win 7 64

All of it operates seamlessly across all runtimes.

Quote - I recall you also needed the poser exe just outside of the V4 runtime folder, that was years ago when I was using poser 6... in fact when I recently upped to 10 I imported my runtimes and instinctively replaced the exe's with the newer poser 10 exe's.

No, the V4 base installer looked for Poser.exe in the destination folder if Poser was selected as the target application (because of the need to be in the application folder with Poser 6), that could be worked around with a dummy "poser.exe" - just an empty text file renamed - or by selecting DAZ Studio as the target application (which had no effect on the files installed). With the move to zips, manually installed or installed through the Install Manager, that is no longer an issue and it was never needed for use, only for the installation of the base figure itself.

Quote - The other thought is how DzCreateExPFiles.exe is locating the runtime. It could just be taking the location from where itself is installed, or it could be using the Daz install path variable "dzContentLastDir" setting from the dzInstall.ini in the DAZ3D user profile directory. If its doing the latter and the path is wrong it may explain why its not working but you say the files are being created so this seems unlikely.

 

The "updater" is DzCreateExPFiles-v4.bat (or Mac equivalent), which lives in the RuntimeLibraries!DAZ folder. It passes the current path to the actual CreateExPfiles application, there's no looking paths up from any stored source.

Quote - I suspect this is all due to this UAC crap. How do I remove or disable that? That's the only thing it can be as far as I can tell. Unless someone else has other ideas. 

The UAC controls can be found under Control Panel: System and Security. Open up the "Change User Account Control Settings" and drag the slider all the way to the bottom to (essentially) disable it.

And fortunately it will have no adverse effects on the operation of Windows to do that.

However, it might leave you vulnerable to malware or viruses.

That's why you should have a good anti-virus/anti-malware program installed.

And I've had to deal with a computer that had a malware infection, because the user mindlessly clicked "yes" in the UAC prompt when the malware tried to install itself, because they'd gotten into the habit of doing so for every legitimate program.