3DX Facial Profile Expression Fix for DAZ 4.9.2 FBX Export

Luv Lee

Hey, this is just a small fix for anyone who needs  to create facial expression in 3DX on an FBX character created in DAZ 4.9.2.   You can can modify the profile as needed and I'd advise it, as some morphs are fairly individual to characters.  These profiles are Genesis 2 male and female.  If you need one for genesis 1, or have any questions about 3DX expression editor, just ping me via PM. I hope this helps guys.

 

One Love,

 

A

burntmage_1197c5e6d4

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

Richard Haseltine

burntmage_1197c5e6d4 said:

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

In order for QA to pick the issue up someone would have had to be using iClone. There were public beta versions which could have been tested by iClone users, if the bug had then be found and reported in a timely fashion it might well already have been fixed. Once the issue was found it was speedily fixed, as shown in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel , and with luck there will soon be an update (as a release or public beta build) that you can use.

WendyLuvsCatz

Richard Haseltine said:

burntmage_1197c5e6d4 said:

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

In order for QA to pick the issue up someone would have had to be using iClone. There were public beta versions which could have been tested by iClone users, if the bug had then be found and reported in a timely fashion it might well already have been fixed. Once the issue was found it was speedily fixed, as shown in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel , and with luck there will soon be an update (as a release or public beta build) that you can use.

it was mentioned in the beta thread by me several times

Richard Haseltine

Sad said:

Richard Haseltine said:

burntmage_1197c5e6d4 said:

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

In order for QA to pick the issue up someone would have had to be using iClone. There were public beta versions which could have been tested by iClone users, if the bug had then be found and reported in a timely fashion it might well already have been fixed. Once the issue was found it was speedily fixed, as shown in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel , and with luck there will soon be an update (as a release or public beta build) that you can use.

it was mentioned in the beta thread by me several times

OK, but did you report it by opening a ticket?

WendyLuvsCatz

Richard Haseltine said:

Sad said:

Richard Haseltine said:

burntmage_1197c5e6d4 said:

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

In order for QA to pick the issue up someone would have had to be using iClone. There were public beta versions which could have been tested by iClone users, if the bug had then be found and reported in a timely fashion it might well already have been fixed. Once the issue was found it was speedily fixed, as shown in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel , and with luck there will soon be an update (as a release or public beta build) that you can use.

it was mentioned in the beta thread by me several times

OK, but did you report it by opening a ticket?

I certainly did once it was made general release, same day actually, I thought the beta forum was to iron out bugs and post issues. 

Richard Haseltine

Sad said:

Richard Haseltine said:

Sad said:

Richard Haseltine said:

burntmage_1197c5e6d4 said:

I'm really glad to see this. A major issue for my pipeline.

Its costing Time and Business for me..... Very Sad because it seem DAZ did not do its QA work to ensuring all the functionality of the previous version work in the new version. 

In order for QA to pick the issue up someone would have had to be using iClone. There were public beta versions which could have been tested by iClone users, if the bug had then be found and reported in a timely fashion it might well already have been fixed. Once the issue was found it was speedily fixed, as shown in the Change Log http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#private_channel , and with luck there will soon be an update (as a release or public beta build) that you can use.

it was mentioned in the beta thread by me several times

OK, but did you report it by opening a ticket?

I certainly did once it was made general release, same day actually, I thought the beta forum was to iron out bugs and post issues. 

And once, post release, the issue was reported the it was promptly fixed (going beyond working hours to so). While issues reported in the threads are often be picked up the proper way to do it, ideally having confirmed the issue and perhaps hammered out the details in the discussion thread, is to report it via a ticket so it can be logged for fixing.

WendyLuvsCatz

I am not going to argue about this anymore said enough and suffered the consequences trying to help, just glad I keep lots of back ups of old installers from every sofware I own.

I tend to feel for others too much having learnt the hard way myself things get broken and you may need to roll back, its a shame DAZ does not feel the need to keep the previous version available to users for this but I always will myself.

I do not install my main build with DIM for this reason only the betas because I have to and download an installer of each update, Jaderail actually taught me that.