Can anyone else get V4.1 to work with themorph tool in P7? My P7 crashes the second I click on the morph tool.

Now, I can use any other figure, including V4 and everything works fine. It does not mater what runtime I use. I have my V4.1 in my P7 runtime so I would like to know if anyone else is having problems and if not where do you have your V4.1 installed.

This is the very first P7 crash that I have had and it does it every time with ONLY P4.

Works well for me.  1) turn off binary morph targets, 2) load a V4, load whatever morphs, and 3) most important  - save a new copy of the CR2 in the characters library, with binary MTs OFF,  It appears parts of the DAZ distributed OBJ are binary, and my problems didn't go away until I got it all converted to text.  Yes, this means P7 still has problems with binary PMD files.  Otherwise mine has been very well behaved.

First , binary morphs are turned off and I even saved a new version of V4.1 but still crashes and it's not morphs I'm having the problems with, it's using the morph tool.

second, it V4.1 that is crashing not V4

third, it has been confirmed by someone else at Daz that it does the same thing to them.

But, thanks for trying.

V4 already was no much use with the P7 MorphBrush because you have to jump through several hoops just to mirror a morph for her.
(Some mastermind at DAZ obviously thought that meshes with non-mirrored vertex order were a good idea.)

And now you say 4.1 completely stops working with the Poser 7 morphbrush ?

Mwaaahahahaaaaa !

Splendid !  ABSOLUTELY splendid !

:thumbupboth:

Beryld had you tried this step of re-saving the CR2 and operating from that?  Rather than just be a shithead and laugh at you, I'm suggesting something that solved this type of problem for me.  I was getting a lot of trouble with morph dials ceasing to work and "error saving binary morph data" even though binary PMDs was turned off for me too, that's what I was saying.

PS, in case it is not perfectly clear, I am talking about V4.1.

"Rather than just be a shithead and laugh at you, I'm suggesting something that solved this type of problem for me."

QFT

And here comes your third report for a TOS violation.
Let's see if we can't teach you some manners.

BTW, there is a very easy solution for all those various V4 and V4.1 problems:

JUST SAY NO !

:laugh:  :laugh:  :laugh:

Oh, and finally, I was laughing about DAZ and not Beryld.
If you find my postings too hard too understand, look for an adult to help you with the difficult parts.

Quote - BTW, there is a very easy solution for all those various V4 and V4.1 problems ...

Spend a little time finding out what the problem is -> http://forum.daz3d.com/viewtopic.php?p=849024&highlight=#849024

Appears to another case of DAZ not doing enough testing and Poser 7 not having enough sanity checking code
(like last time -> http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2679897)

Nruddock that is a really good find.  Thanks for the info, I'm going to look through my own CR2 to see if there are other instances like that.

Reviewed the files in RuntimeLibraries!DAZVictoria 4*, and they are all in PZ2 format (none are binary).  I do not know why Poser gave a dialog that referred to problems saving binary morph targets, but I'm very sure I have had the option disabled for some time.  I expect that is a bug in Poser 7.1.

Quote - Nruddock that is a really good find.  Thanks for the info, I'm going to look through my own CR2 to see if there are other instances like that.

The problem is in one of the files included by the CR2.
As there are a lot of them it would be a long tedious job to check them all, I just going to wait until any reports of other body parts causing crashes come in (i.e. focused checking, DAZ can do the exhaustive one).

Yeah, that is why I'm reviewing the newly-written CR2 described above, it is converted to a single file with no sub-files called by readScript.  42mb, about 2/3 done (god is this boring)

pjz99 , First I don't have a problem with morphs, don't know why that is a problem for you to understand. The only problem I have is the instant crash of P7 when I click on the MORPH TOOL. V4.1 has something different to V4 so as not to work. V4 does work fine.

I have been doing this stuff for years and I wouldn't have asked in the first place without already doing what you suggestd first. I wanted to know if anyone else has had this problem when using the MORPH TOOL.

Now I have had more saying the same thing is happening to them. I was not not being anything to you. I at least never stooped as low to call you ignorant names. I also read what someone posts so as to not to question what has already been stated.

Finished reviewing the re-written V4.1 CR2 and I found no instance where "indexes" is followed by a non-zero number where there was not a block of deltas data.

This is the block from my original DAZ-installed PS_pe070_DAZ_Chnnls.pz2 (installed by the V4.1 installer):
  targetGeom PHMEyesIrisConvexity
   {
   name EyesIrisConvexity
   initValue 0
   hidden 0
   forceLimits 1
   min -1
   max 2
   trackingScale 0.004
   keys
    {
    static  0
    k  0  0
    }
   interpStyleLocked 0
**   indexes 529
   numbDeltas 2099
   deltas
    {
    }**   }

Corresponding block from the newly-written CR2:
  targetGeom PHMEyesIrisConvexity
   {
   name EyesIrisConvexity
   initValue 0
   hidden 0
   forceLimits 1
   min -1
   max 2
   trackingScale 0.004
   keys
    {
    static  0
    k  0  0
    }
   interpStyleLocked 0
**   indexes 529
   numbDeltas 2099
   deltas
    {
    d 0 0.624685 0.226265 0.917647
    d 0 0.282501 0.375315 0.226265
    d 0 0.0823534 0.282501 0.624685
    d 0 0.773735 0.917647 0.717499** .....

It appears that the problem with the sub-files got silently corrected by Poser when it wrote the new CR2 file (as I've observed without understanding why, now I do understand why, thanks Nruddock).  I suspect the deltas are loaded correctly in another of the sub-files, and while there is not sufficient sanity checking at load-in time, and while in memory, this somehow gets caught and written out correctly.  The morph for EyesIrisConvexity does work (just tested that with the freshly-written V4.1 CR2).

Beryld I understand you are having problems with the morph tool.  I didn't direct anything hostile towards you whatsoever, I apologize if that came across that way.  I know you are talking about V4.1.  I am talking about V4.1 also - I see that I actually said that incorrectly in my first response.  I understand you are talking about problems with the morph tool.  I am talking about similar problems - load a blank V4.1, touch the morph tool, get an error.  Other errors happened to me too, like I described.  This fixed it for me and I think it may fix it for you too.  That's all.

Interesting investigative work, nruddock! :)

I had a similar problem with my iPP plugin under similar circumstances (not V4.1) - non-zero indexes in morph dials (targetGeoms) with no morph deltas or mismatched count (someone forgot to remove a base morph on a pose or something).  I solved that by letting the parser 'read' the non-existent deltas and actually count them.  That number is then used instead of the misrepresentative one in 'indexes'. ;)

This is not only a problem with Poser 'sanity checks', but also that since Poser files are text and can be edited by anyone, it is entirely possible for someone to flub up these key systems.  The lack of Poser sanity checks makes these human errors more problematic.

beryld,I'm thinking you're kind of missing it here. In the thread nruddock pointed you to:

Go to Runtime/libraries/!Daz/head/05-ps_pe070_DAZ_Chnnls.pz2
Open the file in Wordpad (or similar)
In the edit menu, use 'Find' and search for   "PHMEyesIrisConvexity"
Scroll down a few lines to where it say's "indexes 529" and change the 529 to zero
Next, find "PHMEyesIrisAlign" and where the indexes say 881, change it to 0

Do that and your morph tool should work.

I fixed it. That was the problem, or at least it fixed the crash. I read the fix over at Daz.

I take it by the avitar that nruddock is noelr at Daz.
I renamed the original with an x in front so I don't have to move it or lose it. Save the fixed file back into the original file.

Thanks for all the help in solving yet another Daz/poser problem. Sure seems to be a lot of them these days.

Edit to say, no I didn't miss the thread pointing.

Glad to hear that helped you out :)

Quote - Interesting investigative work, nruddock! :)

This one didn't take to long to track down, as I got a crash as soon as I clicked on the Head with the Morph Tool active.
Most of the time went into snipping out a bit of the include file, restarting Poser and checking for a crash until I'd sufficiently narrowed down where in the file the problem was to be able to spot something suspicious and apply a candidate fix to confirm.

Quote - I take it by the avitar that nruddock is noelr at DAZ.

Yep, that me