Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 40

Thread: LWO Importer on the Unity Asset Store

  1. #16
    A.K.A "The Silver Fox" Gungho3D's Avatar
    Join Date
    Aug 2009
    Location
    Oztralia
    Posts
    411
    Quote Originally Posted by escape_artist View Post
    1. In a low-dynamic range Unity project, Lightwave BSDF materials convert to the Standard (Roughness setup) material, and Lightwave's Standard Materials are converted to the Standard (Specular setup). For HDR conversion I will need to look into it and try and figure out the most natural mapping.

    2. I decided that the closest thing to a bump map in Lightwave were height maps in Unity. If there are tearing artifacts then perhaps the height map value is too large? This can be changed in Lightwave -here's a screenshot showing that in the Materials example that comes with LWO Importer, the Bump Height is at just 5%. Generally, low values are best here.


    3. Yeah this is a limitation I'd like to fix but I'm not sure exactly the best way to do it right now. As you have noticed, the materials are 'locked' - greyed-out - when they come into Unity. Converting them to HDR I think makes copies of all the materials, just as you can do manually be selecting the material in the Project view by finding it under the imported model and duplicating it (cmd/ctrl - D), then re-assigning this duplicate material to the mesh in the scene. But this change doesn't survive importing the model again, as doing so will overwrite this.
    I think the fix is likely to be similar to Unity's .fbx import option where imported materials can be remapped to pre-existing materials in the assets import options. However this isn't a small job to implement so I'll need some time to determine how best to do it, and if it's definitely worth it.


    And I'm very happy to get feedback, thanks, so keep it coming!
    Hey Chris

    #1. is not a biggie, as remapping in Unity is mostly a piece of cake. It's would be super lazy of me to insist on everything being made super perfect your end in this regard.
    #2. I think I might explore the use of normal maps instead of height maps - I need to check out if via "height maps" Unity is actually trying to displace geometry ...
    #3. I didn't realise remapping to pre-existing materials was possible via Unity .fbx import … thanks!

  2. #17
    LWO Importer version 1.3 has gone live today on the asset store (link)

    Quite a big update which also addresses some of the feedback I received.
    Highlights:
    - Subdivision surfaces. This is a big one and I think it's very cool. Model in SubPatch or Catmull-Clarke surfaces and LWO Importer will read it and convert it into a Unity model. Supports (almost) all the different UV texture interpolation modes too. Oh and, unlike Lightwave, the interpolation modes work with Catmull-Clarke surfaces.
    LWO Importer lets you specify the number of iterations to use so you can basically turn a cube into a smooth sphere.
    Also, Lightwave Morph targets work in combination with SubPatch surfaces, meaning its possible to create some very cool subdivision surface animation for Unity. I'm working on a demo video at the moment to properly show it off.

    In the meantime here's a screenshot from Unity, showing the same lightwave model imported with 0, 1 and 2 iterations. It also shows off the subdiv/blendshape functionality.
    Click image for larger version. 

Name:	Screen Shot 2018-11-12 at 20.29.13.png 
Views:	71 
Size:	1.18 MB 
ID:	143345

    - Smoothing Angles in materials are now used to create hard edges in the imported models.

    - Option to smooth normals over varying surfaces.

    - Ability to remap imported materials to pre-existing ones. So if you're not happy with the imported materials you can easily swap them out. And whenever you import the model again these remapped materials will be remembered and restored automatically.

    Any feedback is always welcome.
    Cheers
    -Chris
    Last edited by escape_artist; 11-12-2018 at 12:31 PM. Reason: Added image

  3. #18
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    did you have any luck with the hdr issue? I find the materials keep getting lost, when I use the remap materials option. is this related?

    also of note, when you change the name of a material and save the LWO, in LW 2018 (not sure of 2017), unity object will not reflect the change, even with RMB click on the object and selecting re-import.
    Last edited by gar26lw; 12-11-2018 at 11:07 PM.

  4. #19
    Hi, yes I built the new 'remap materials' functionality to fix the HDR issue and in my limited tests it does. But I'd be interested in understanding what's going wrong for you.
    Just to make sure we are both on the same page, here are the steps I use when testing HDR:
    1. In a HDR Unity project, add a .lwo file and drag the asset into a scene so you can see it. The materials will all draw as bright pink in the scene preview.
    2. In the project hierarchy view, expand the imported .lwo file to reveal its materials.
    3. Select the materials.
    4. Duplicate the materials (CMD D/Ctrl D) and drag them into a folder called HDR materials.
    5. Select these new materials and go to Edit>Render Pipeline>Upgrade Selected Materials To High Definition Materials
    6. With the .lwo file selected, drag each of these newly upgraded materials onto each remapped material slot.
    7. Hit Apply.
    The object will render correctly, with the remapped materials. Subsequent re-imports do not override the remapped materials. Can you try recreating these steps exactly and see if it matches what you are doing and if it goes wrong, where?

    Also, I have had no luck recreating the material name bug you describe, using LW2018. Frustratingly, when I rename a material in LW and save the object, the material is renamed in Unity too. Are you able to provide more details in your process so I can recreate the bug? Thanks

  5. #20
    Quote Originally Posted by gar26lw View Post
    I find the materials keep getting lost, when I use the remap materials option. is this related?
    ok I think I've managed to recreate this issue. I'll see if I can work out what's going on and submit a fix. Thanks for letting me know.

  6. #21
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    Quote Originally Posted by escape_artist View Post
    ok I think I've managed to recreate this issue. I'll see if I can work out what's going on and submit a fix. Thanks for letting me know.
    thanks, no problem. Got another one

    seems lwo3 objects (lw 2018 objects) somehow make unity freak out at loading of scenes. Don't know if this is connected to SVN. Things were working fine, then suddenly they are not upon reload of the project.

    Unity2018.2.0f2

    When I open the lwo3 in lw 2018.0.7 and save as an lwo2, over the top of the original lwo3 file.. now unity works and loads the level. Of course, materials are destroyed.

    Looks to me like lwo3 support is not ready for primetime. I advise sticking to lw 2015 for the use of the plugin atm. lw 2018 needs some loving.

    Sorry I cant be of more help with an explanation, there is no way to know what is going on, I have to kill off unity form task manager. All I know is the fix above works to get unity loading a project again.

    I'll take a look at those steps you mention to see if I get issues with that workflow.
    Last edited by gar26lw; 12-17-2018 at 08:01 AM.

  7. #22
    Quote Originally Posted by gar26lw View Post
    Looks to me like lwo3 support is not ready for primetime.
    I'm using it myself for production work and I've not encountered anything like this. LWO Importer imports the model fine but on subsequent reloading of the Unity project it fails, right? When you reload the Unity project my code isn't getting called - it's only called when you import the file into the Unity project, or explicitly select Reimport on the object. From then on it exists as a serialised Unity object in the Library folder in your project.

    I'm not using SVN - it could very well be the culprit.
    If you create a new Unity project with no source control and import your model into it, then reload the scene, does it still crash?

    btw I submitted a new version yesterday - 1.34 - to the Unity Asset Store. It will hopefully fix your remapped material issues.

  8. #23
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    Quote Originally Posted by escape_artist View Post
    I'm using it myself for production work and I've not encountered anything like this. LWO Importer imports the model fine but on subsequent reloading of the Unity project it fails, right? When you reload the Unity project my code isn't getting called - it's only called when you import the file into the Unity project, or explicitly select Reimport on the object. From then on it exists as a serialised Unity object in the Library folder in your project.

    I'm not using SVN - it could very well be the culprit.
    If you create a new Unity project with no source control and import your model into it, then reload the scene, does it still crash?

    btw I submitted a new version yesterday - 1.34 - to the Unity Asset Store. It will hopefully fix your remapped material issues.
    thanks man, yeah id not be surprised if this is an svn issue, especially with you using in production. thanks

  9. #24

    Cool LWO Importer 1.40 is now fully compatible with Lightwave 2019.

    Version 1.40 has just gone live, and it's now fully compatible with Lightwave 2019.
    A couple of significant additions:
    - Smoothing Groups created in Lightwave 2019 are supported. This makes it easy to define hard edges in your models.
    - Remapped Materials have been re-vamped. Rather than use the Surface Index extracted from Lightwave which can change when deleting/adding materials, LWO Importer now matches the material name with the remapped material. This is generally much more robust and should avoid situations where the remapping of materials were getting corrupted.

    Here's how the editor interface looks now, with the new Material Remapping:
    Click image for larger version. 

Name:	Screenshot 2019-02-13 at 11.56.27.png 
Views:	48 
Size:	121.5 KB 
ID:	144122

    Happy Importing!

    -Chris

  10. #25
    Super Member JohnMarchant's Avatar
    Join Date
    Mar 2003
    Location
    Murcia, Spain
    Posts
    2,959
    Just got my copy.
    Dell XPS 15
    15.6-inch (3840 x 2160) 4K 282ppi IPS LCD
    Intel i7 7700HQ 2.8GHz
    Windows 10 64Bit
    NVidia GeForce GTX 1050 Ti
    1TB SDD
    32Gb Ram

    LightWave 2019.03

    Very nice Laptop

  11. #26
    Quote Originally Posted by JohnMarchant View Post
    Just got my copy.
    Excellent! Hope you like it.

    Another small update (1.41) went live very recently, adding Subpatch Weight Map support, along with an updated example scene to show it off.

  12. #27
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    cool, thanks.

  13. #28
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    hi,

    using unity 2018.3.0f2 and the lwo importer version 1.41

    i can not get textures to import on materials in 2015.3 or 2019.0.3

    setting content directory to assets/lwo_content

    subdirectories with /objects and /images

    unity lwo importer throws and error saying “unable to find texture file Images/texture.png” paths should be relative.

    texture will only be recognized on the lwo material in unity via importer if i place the texture.png in the same folder as the lwo file.

    i assume that this is a bug? it’s stopping me from using the std lw content for project setup.

    states in docs that this should work and is the preferred method.

    what am i doing wrong?

    thanks

  14. #29
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    Additional bug in 1.41 :

    lwo layer names are not transitioning to mesh in the unity asset.
    this means you cannot see/select an items sub-mesh from within unity very easily.
    I thought this worked before ?

  15. #30
    Registered User
    Join Date
    Aug 2016
    Location
    a place
    Posts
    1,755
    Another bug : I think the UV's are not coming across with the LWO files. Materials already created in Unity on other models do not pick them up. Material assignments are there but the albedo texture etc.. does not appear in the unity viewport.

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •