Andrew Shpagin

General AppLinks info

45 posts in this topic

Every AppLink in this forum will work in similar way.

At first, you should read installation notes, then install corresponding AppLink.

After installing you should run your App, then run 3D-Coat. There should appear the new menu in 3D-Coat - File-> Open in -> Your app name.

You may use this item to bring 3D-Coat's models from any room (Paint, Retopo, Voxels) to your app with color, normal, displacement and specular. But you should choose what you need - displacement or normalmap, not both at once.

Also you may bring your models from your app to 3D-Coat using plugin. In this case you will get new item in menu - File -> Open in original app. In so way you may bring model back to your app.

You need at least 3.5.01+ to use AppLinks.

Share this post


Link to post
Share on other sites

Is there any ETA ("estimate time of arrival") for the other AppLinks, for instance (most interesting to me personally) the Softimage one?

;)

Share this post


Link to post
Share on other sites

Is there any ETA ("estimate time of arrival") for the other AppLinks, for instance (most interesting to me personally) the Softimage one?

;)

XSI AppLink is expected in 1-2 weeks

Maya in a week

LW in 2-3 weeks.

Messiah - in couple of days

Houdini - in 2-3 weeks

Share this post


Link to post
Share on other sites

Awesome news, I have one more thing to look forward to now.

Share this post


Link to post
Share on other sites

XSI AppLink is expected in 1-2 weeks

Maya in a week

LW in 2-3 weeks.

Messiah - in couple of days

Houdini - in 2-3 weeks

Any ETA on Cinema4D ?

Peace,

Rich_Art. :good:

Share this post


Link to post
Share on other sites

Any ETA on Cinema4D ?

Peace,

Rich_Art. :good:

It is in queue, but I have no ETA.

Share this post


Link to post
Share on other sites

Thanks Andrew. I will update the script very soon. There is couple things. It would be nice if we can edit import dialog too, like we can do export dialog now.

And the other thing is that right now output textures naming is based only uv-sets and material. It would be nice if object would be included into naming.

Like for example if I have two objects in 3d-coat scene the naming would be like this

Cube_Material_UvSet1_disp.jpg

Sphere_Material2_UvSet1_disp.jpg

In my opinion order Object_Material_Uvset_texturetype.jpg would be the best order.

Share this post


Link to post
Share on other sites

Any word on the LightWave AppLink?

Share this post


Link to post
Share on other sites

Any word on the LightWave AppLink?

The programmer working on the Maya AppLink is also working on the LW applink, he's re-working the Maya one and is nearly finished. Shortly thereafter he'll begin coding the LW applink.

Share this post


Link to post
Share on other sites

Thanks.

Share this post


Link to post
Share on other sites

Sure thing. :)

Share this post


Link to post
Share on other sites

Is it possible to exchange the voxeldata from and to 3d-coat ??

I am thinking about an Houdini applink for volumedata ..

Share this post


Link to post
Share on other sites

Another vote and thank you for the development efforts going into AppLink. Now that Lightwave 10 is being released and modo 501 is out, these are the two AppLinks that I would welcome. Can 3DC link to and respect the folders of existing texture images, and create new ones in the same folder as needed??

Thank you again.

Paul

Share this post


Link to post
Share on other sites

Andrew, please tell me. Why 3dcoat adds "import_" prefix for each texture in during export? I can't remember. So was always?

Share this post


Link to post
Share on other sites

Andrew, please tell me. Why 3dcoat adds "import_" prefix for each texture in during export? I can't remember. So was always?

Preffix is just exported OBJ file name.

Share this post


Link to post
Share on other sites

ok. I have next problem. Each time when export happens from 3dcoat, I have clear obj-name, but +extra "import_" in texture name.

Example:

1-st interaction:
-----------------
Maya export:

obj: export.obj, import.obj
texture: __

***

3dcoat export back:
obj: import.obj
texture: import_initialShadingGroup_color.tga

2-nd interaction:
-----------------
Maya export:

obj: export.obj, import.obj
texture: import_initialShadingGroup_color.tga

***

3dcoat export back:
obj: import.obj
texture: import_import_initialShadingGroup_color.tga

As you can see, after 10 interactions we have a very very long names ))

Share this post


Link to post
Share on other sites

Ok, I will resolve this problem, I will cut extra "import_" - s.

Share this post


Link to post
Share on other sites

Andrew, two version already released, but the bug still has been present. Probably you forgot? )

Share this post


Link to post
Share on other sites

Andrew, two version already released, but the bug still has been present. Probably you forgot? )

3.5.19A removes all duplicate words like import_ from textures names. Please check.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now