Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-6370

FIWARE.Request.Tech.WebUI.XML3D.Texture 3d-ui-xml3d

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Andrea sent a message using the contact form at http://catalogue.fiware.org/.

      Hello,
      i want to report an abnormal behavior using the 5.1 version of XML3D.
      Visualizing an object with texture using the XML3D version 4.9 the object is
      correct, switching to XML3D version 5.1 (same object) the texture is wrong.
      Is there any solution to solve this problem?
      Thank you
      Andrea

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: andrea.beretta@desamanera.com]

        Activity

        Hide
        cschlinkmann Christian Schlinkmann added a comment -

        The issue has been emailed:

        • Time sent: 14/Apr/16 9:35 AM
        • To: andrea.beretta@desamanera.com
        • with subject: *(HELP-6370) [Fiware-tech-help] [3D-UI-XML3D] Texture 3d-ui-xml3d *

        Hi Andrea,

        XML3D 5.0 was a major release that isn't backwards compatible with 4.x. You can find more information about what needs to be done to convert your scene in our Github Wiki:

        https://github.com/xml3d/xml3d.js/wiki/Migrate-to-XML3D-5.0

        I would recommend doing this because all future releases will be based on 5.0 (like 5.1 is). If your models use the XML3D asset format you can either convert them manually (it's just a bit of find/replace in this case), re-export them with assimp2xml3d v0.2 which exports XML3D 5.0 or use them in a different format such as STL:

        https://github.com/xml3d/xml3d.js/wiki/Converting-models-to-XML3D

        If you've already done all this and the problem is still there then please let me know and we'll look at some other possible causes. In this case it would be useful for me to see the model and the materials that aren't working properly.

        Regards,
        Christian

        Show
        cschlinkmann Christian Schlinkmann added a comment - The issue has been emailed: Time sent: 14/Apr/16 9:35 AM To: andrea.beretta@desamanera.com with subject: *( HELP-6370 ) [Fiware-tech-help] [3D-UI-XML3D] Texture 3d-ui-xml3d * Hi Andrea, XML3D 5.0 was a major release that isn't backwards compatible with 4.x. You can find more information about what needs to be done to convert your scene in our Github Wiki: https://github.com/xml3d/xml3d.js/wiki/Migrate-to-XML3D-5.0 I would recommend doing this because all future releases will be based on 5.0 (like 5.1 is). If your models use the XML3D asset format you can either convert them manually (it's just a bit of find/replace in this case), re-export them with assimp2xml3d v0.2 which exports XML3D 5.0 or use them in a different format such as STL: https://github.com/xml3d/xml3d.js/wiki/Converting-models-to-XML3D If you've already done all this and the problem is still there then please let me know and we'll look at some other possible causes. In this case it would be useful for me to see the model and the materials that aren't working properly. Regards, Christian
        Hide
        cschlinkmann Christian Schlinkmann added a comment - - edited

        Forgot to evolve this to Answered. No response from original reporter yet.

        Show
        cschlinkmann Christian Schlinkmann added a comment - - edited Forgot to evolve this to Answered. No response from original reporter yet.

          People

          • Assignee:
            cschlinkmann Christian Schlinkmann
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: