[Half Life]

An improvement not mentioned in the release notes is a big improvement with importing FBX or Collada files into Studio -- this is something I find a very big help when working with DAZ assets. Combining the new subdivision modifiers with FBX files can really streamline the workflow signifigantly over working with OBJ files.

One thing worth mentioning is there is currently a bug in DAZ's FBX exporter where certain morphs are not baked properly -- if you experience this it is best to revert to OBJ files for those assets.

Best,
Jason.

[PeterP]

Can you be more specific about the DAZ FBX export bug?

I've had export problems with non-character items where they are randomly offset on export - is that the bug?

Pete

[Half Life]

Some JCM's are not properly baked (on certain figures) -- which can result in deformation and poke through. I reported this bug to DAZ already, so they know of it and hopefully a fix will be coming.

I have seen what you are talking about as well, and the solution in those cases is to export that item by itself (I've had it happen on autofit hair for instance).

There is no work-around for the JCM bug, your only option is to use OBJ instead... however you may never see it if you don't use a pose that reveals the bug.

Best,
Jason.

[sandykoufax]

I think new FBX feature of Maxwell Studio 3 is worse than 2.7

Here is my test. I exported it with lastest Maxwell Max plugin.



What's wrong?

[Mihai]

Looks like it's not interpreting the vertex normals correctly, but why are you exporting an FBX from Max, then importing it into Studio? Or was it just as a test? Seems a really strange workflow to me...

[sandykoufax]

Looks like it's not interpreting the vertex normals correctly, but why are you exporting an FBX from Max, then importing it into Studio? Or was it just as a test? Seems a really strange workflow to me...

Actually I'm not using this workflow too. I'm just check my FBX format files that exported from Max.
In fact, it's my only usage of Maxwell Studio.

[juan]

Apart from a few other fixes (UVs, update to the last fbx sdk, etc), now the importer recalculates the normals when the FBX import process finishes. Could you please check if when you recalculate normals in 2.7 you get the same result as in v3?

Thanks,

[sandykoufax]

Yes, right. When I recalculate objects in 2.7, I got the same result as in v3.

[juan]

ok, During the testing we detected that recalculating normals was probably a better idea but it seems is probably not, so we will revert this change in the next path, people can always recalculate normals manually later. Anyway we will research more in when normals inside the fbx are good and when they are not, but apparently there is no way to know that.

[sandykoufax]

How about preference option with FBX import?

[juan]

A preference might work but could be dangerous if you don't remember if it is active or not and suddenly the beautiful normals in the fbx get broken. Maybe a "do you want to recalculate normals in this object?" with a "Do not ask me again in this session" should be enough, I do not think this is a process you do hundreds of times a day so probably that question will not be too annoying, right?