Jump to content
3DCoat Forums

LightWave 10 Applink


Keeks
 Share

Recommended Posts

  • 4 weeks later...
  • New Member
On 4/6/2018 at 10:14 AM, Styler said:

I'm updating LW part. Since Coat cannot handle LWO 2018 I'll be using different file formats for sending data between apps.

Thanks a lot !

Good to see a new AppLink for 3DCoat and Lightwave 2018 !!!
This will be really helpful !

Hopefully LWO 2018 format will be supported natively in 3Dcoat since PBR arrived in Lightwave and it makes so much sense now.

Thank you for finding a way of roundtripping between the Apps by now.

Excellent !!!

Regards,

Marcus

  • 2 months later...
  • Member
On 4/5/2018 at 1:14 AM, Styler said:

I'm currently working on an update for LW applink. I believe that this will be done soon-ish.

Really looking forward to this !

Exporting a 2015 LW model to get it into 3dC, ... then bringing it back in to LW, ... and setting up and monkeying with the surface nodes gets pretty time consuming.

Sorry guys. I'll will not able to finish a new applink due to complexity and time that I need to spend with it. Too much work for me, besides my primary job. If someone is interested to continue I can provide the source code and instructions how to accomplished it.

Here is a brief explanation.

All previous applinks used material slots and that was quite easy to do because we have access to this part through scripting language or lwsdk. Somebody can say "Dude.. But we have node editor and many cool nodes! Why don't you make shaders using this approach?!". I have to say this is a first thing I'd do,  especially in LW 2018 where legacy materials give you a bounded potential. Sounds good in theory, but the access to nodes is heavily limited in lwsdk. Even in LW 2018! You can write and compile your own nodes as additional plugins, and later use them in NodeEditor, but there is no way to create a simple node from script or code, only manually. From the developer perspective a node is just a black box, which does some magic stuff. I spent a lot of time trying to get access through different hacks, but apparently it's not possible. The only one way that I could see is writing your own LWO parser and override information directly in lw object files. This is a pretty big task and require a lot of patience and time. Beside that not every LWO chunk has a description in the sdk documentation. If you still interested please try =), it's pure fun!

Edited by Styler
  • Advanced Member

Can you put the code up in GitHub or some equivalent location?  Otherwise, what license would apply, and how do we obtain the source code?

I can't make any promises, but there's a fairly decent chance someone will finish the AppLink for LW2018.

  • Like 1
  • Advanced Member
3 hours ago, Carlosan said:

That thread just links back to this thread, it doesn't contain the source code itself.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...