Hi, been on a Poser hiatus for a couple of years and now I'm trying to take it up again. Having a few problems and I would really appreciate some help.

Poser Pro 2012, Windows 7, 64bit 

I re-installed Poser Pro 2012,  then downloaded from DAZ all my V4 and M4 purchases, which included V4 Base, V4++Morphs, V4 Muscle Morphs, M4 Base and M4++ Morphs.

Both V4 and M4 load fine from the character library, but when I try to inject any or all of the Base or ++ morphs, they do not load. Well, actually, "Wirey" loads for V4, but does not work, and "Neck Twist" loads for M4, but does not work. Here's the next odd thing. If I attempt to load a DAZ morph package for M4, for example: the "Marco" package, the necessary morphs load and work. If I attempt to load a DAZ morph package for V4, example: "Kesnia", the face morphs load, but nothing else.  

Any ideas? 

I thumbed through my General Preferences tab and unchecked "External binary morph targets. While there, I noticed under the "Misc" tab that "temp files" is set to save at "userspaulappdatalocaltempposer pro9   Is this okay?

Any help would be much appreciated. 

 Did you initialise V4 and M4 after you installed the figures.   I files to do this should have been downloaded with the figures. 

Where the temp files are stored is not really an issue so the default is normally OK.   The only reason I can think of for moving the temp files is if the default is storing them on an Solid State Drive (SSD), if that is the case I would move them temp location to a conventional hard drive.  SSDs are a lot more reliable these days but reducing the read/write cycles can only help in extending the life.

 Hornet3D, I remembered the original initialise process, but it seems to be no longer applicable. There is not mention of it in the DAZ read me's, nor is there any to download.

You may be right, it is a long time since I re-installed V4.  On the other hand I am sure I have seen this problem reported more than once and the solution appeared to be to re-initialise using the .bat files that used to be supplied with V4.

In my case these are located at - drive E/V4.2/Runtime/Libraries/!DAZ.  Those files will have been there from way back as the 'E' drive holds all my runtimes and all I do it point and new versions of Poser to those runtimes.  It may have been there since Pose 6,  Also there have been some updates of  V4 but as I am using V4WM and I am happy with how the figure works I never updated.  A case of it isn't broke, don't try and fix it.  All of this could mean you no longer need to initialise V4, if so I hope someone else adds to this thread to confirm.

The necessary .bat file should be included with the base V4 package.  Unfortunately, I am nowhere near my computer to direct you the target file.  Someone else might chime in.  The other concern is where PP2012 is installed in relation to it's content.  If you followed the installation procedures for PP2012, the core program should be in your Program Files and content placed in your share folder, such as Documents.  This is where your M4 and V4 should be installed or their own runtimes linked to Poser.  However, if you decided to install content to Poser's runtime folder then you may experience UAC interference within Window 7 which will disrupt access and functionality.

RuntimeLibraries!DAZDzCreateExPFiles-m4 (or v4) is the updater. It's also important to make sure you have only one RuntimeLIbraries!DAZVictoria 4 or Michael 4 folder.

 Okay, I've found those files in Runtime-Libraries-!DAZ folder. There is a V4, M4 and M4Genitals batch files, along with DZCreateExPFiles application. I'm going to try them and see if it works. Thanks!!!

 Ahhh! No luck! Any other ideas? And thanks for trying.

Where is your Runtime, and what operating system are you using? Are you sure there's only one RuntimeLibraries!DAZfigure name folder for each figure on your system?

 Okay, here's how I fixed it. I uninstalled and deleted everything. I downloaded Daz's downloader, let it put the V4 and M4 base in it's own file, which includes a runtime folder, then merged that runtime folder with mine. Now everything works fine. Thanks everyone!!!