Jump to content
3D Coat Forums

Styler

Applink Developer
  • Content count

    103
  • Joined

  • Last visited

  • Days Won

    7

Styler last won the day on November 20 2017

Styler had the most liked content!

Community Reputation

37 Excellent

About Styler

  • Rank
    Novice

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Enable
  1. Styler

    LightWave Applink

    Here is the archive with the source files lw_applink_source_latest.zip
  2. Styler

    LightWave Applink

    ok, ok... give me a day to clean up what I have and I'll post it.
  3. Styler

    LightWave Applink

    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!
  4. Styler

    LightWave Applink

    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.
  5. Styler

    LightWave Applink

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

    LightWave Applink

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

    Maya AppLink

    Currently it's not possible. Only of rewrite it in C++.
  8. Styler

    Maya AppLink

    version 2.2.2 ************* Fixed: - The issue with exporting selected objects 3dcoat_for_maya_v2.2.2.zip
  9. Styler

    Maya AppLink

    Hi Swinny, Yes, you're right. Apparently I broke something during refactoring. I'll check and fix the issue asap. Thanks for the bug report!
  10. Styler

    Maya AppLink

    You'll get all correct files, If you do File->Open in Original App (see attachment) Exchange.7z
  11. Styler

    Maya AppLink

    Seems like it's another bug in 3D-Coat. After export it should create at least a pair of files (export.txt, textures.txt) or even 3 files, includes Export.xml. Something definitely went wrong here. I'll tell to Andrew. Thanks for finding the bug!
  12. Styler

    Maya AppLink

    How do you send your painted object back to Maya? I guess you do Export To->Maya instead of Open in Original App
  13. Styler

    Maya AppLink

    And you're using the latest applink version v.2.2.1 and 3D-Coat 4.8, right?
  14. Styler

    Maya AppLink

    Удалой Did you uncheck "Use export constructor for per/ channel packing" option in the export dialog box, as shown in the picture above?
  15. Styler

    modo AppLink

    As I see, the exception occurs when the applink tries to read and sync presets. The applink assumes that there are no subfolders in "Documents\3D-CoatV48\Temp\TempPresets" but you have one named "Add". The quick solution is just to move all existing presets from "Add" to "TempPresets" and delete "Add". I'll support subfolders in "TempPresets" in the next release.
×