We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

Instanced objects with different materials are not visible in version 2.17 pre-2

Home › Forums › Bug Reports and Feature Requests › Instanced objects with different materials are not visible in version 2.17 pre-2

Tagged: , , ,

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • 2019-12-07 at 3:24 pm #21799
    illussimo
    Customer

    Hello, I’ve tried version 2.17 pre-2 with Blender 2.81.
    Armatures, animations and procedural textures export fine now. :good:
    But, I noticed one important issue.
    – Instanced objects with different materials are visible in version 2.16 (exported from Blender 2.80)
    – Instanced objects with different materials are not visible :cry: in version 2.17 pre-2 (exported from Blender 2.81)
    See attached images.
    Hopefully, this can be fixed in the upcoming version. :yes:
    :bye:

    2019-12-07 at 4:54 pm #21809
    Anonymous
    Inactive

    If your materials have textures added, you could try to refresh them (alt+R on the texture node) and try to check if their location is in the proper verge project folder. But if the textures are not present, try to setup the materials again. This is inconvenient but it is sometimes helpful to reseting setups in the new releases.
    :-*

    2019-12-08 at 5:52 pm #21821
    illussimo
    Customer

    Hello Abin,
    Thank you for trying to help out.
    It is only in the browser that they don’t show up. In Blender 2.81 everything is visible and works fine. Everything is in the right folder, besides that the instanced objects I’m talking about have procedural textures or just a simple material with only a difference in colour.
    I think this is still something that has to be dealt with for the upcoming Verge3D update.

    2019-12-09 at 9:21 am #21834
    Anonymous
    Inactive

    did you try hard reload in browser (F12 + long click in reload button in chrome)? it removes cache, but yes, it is strange.Hmm, I always have similar stops in my work, each browser complains different ways…

    2019-12-09 at 10:49 am #21839
    Yuri Kovelenov
    Staff

    Hi Simone,

    this looks like a bug to me. Can you make a blend file with only books in it and attach here? We’d take a look. Thanks!

    Chief 3D Verger | LinkedIn | Twitter

    2019-12-09 at 3:48 pm #21848
    illussimo
    Customer

    Here is a file with the books.
    :bye:

    Attachments:
    You must be logged in to view attached files.
    2019-12-11 at 7:02 am #21875
    Yuri Kovelenov
    Staff

    Thanks! I’m reproducing that. We’ll try to fix this asap.

    Chief 3D Verger | LinkedIn | Twitter

    2019-12-11 at 7:05 am #21876
    Yuri Kovelenov
    Staff

    In fact, it does not work with Blender 2.80/Verge3D 2.17 either. Can you confirm it?

    Chief 3D Verger | LinkedIn | Twitter

    2019-12-13 at 9:15 pm #21942
    illussimo
    Customer

    I only know that it worked fine in 2.8 with 2.16.
    I switched to 2.81 when I started to use 2.17 pre2. 2.81 had quite some under the hood changes and improvements so I thought it had something to do with that. :unsure:
    I would like to publish the update of my Faun da Gamba app and everything works just fine also most instanced objects :good:, only the instanced objects with different materials don’t show up.
    Hopefully, it is something that can be fixed soon.
    :bye:

    2019-12-14 at 10:10 am #21947
    Yuri Kovelenov
    Staff

    okay, we’ll take a look at this. Thanks again!

    Chief 3D Verger | LinkedIn | Twitter

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.