Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Numerical simulator mesh visualization
Forum Updated to NodeBB v4.3 + New Features

Numerical simulator mesh visualization

Scheduled Pinned Locked Moved Unsolved General and Desktop
4 Posts 3 Posters 351 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Renato Pol
    wrote on 6 Dec 2020, 16:18 last edited by
    #1

    Hi

    I am designing a visualizer for simulation meshes of 1-2 milion finite elements (either tets or quads).

    I was successful in adding each element to a scene, navigating etc using QGeometry rederization, Qt3DExtras etc. It worked fine and I could get QScreenRaycaster to work too.

    However, it did not scale, and gets very slow in around 200k elements.

    What would be the best design approach to this problem? I consider to set the whole mesh as a single QEntity, so I can optimize a lot on my side. However, I would have to port Ray Casting and a lot of nice Qt features to the user side, which will take significant dev time.

    Any suggestion before I dig into tons of coding?

    Thanks,
    Renato

    R 1 Reply Last reply 11 Dec 2020, 01:47
    0
    • R Renato Pol
      6 Dec 2020, 16:18

      Hi

      I am designing a visualizer for simulation meshes of 1-2 milion finite elements (either tets or quads).

      I was successful in adding each element to a scene, navigating etc using QGeometry rederization, Qt3DExtras etc. It worked fine and I could get QScreenRaycaster to work too.

      However, it did not scale, and gets very slow in around 200k elements.

      What would be the best design approach to this problem? I consider to set the whole mesh as a single QEntity, so I can optimize a lot on my side. However, I would have to port Ray Casting and a lot of nice Qt features to the user side, which will take significant dev time.

      Any suggestion before I dig into tons of coding?

      Thanks,
      Renato

      R Offline
      R Offline
      Renato Pol
      wrote on 11 Dec 2020, 01:47 last edited by
      #2

      @Renato-Pol hi - did anyone has a chance to help me on this?

      1 Reply Last reply
      0
      • J Offline
        J Offline
        JKSH
        Moderators
        wrote on 11 Dec 2020, 02:21 last edited by JKSH 12 Nov 2020, 02:24
        #3

        Hi @Renato-Pol, I don't have the experience with high-performance programming in Qt 3D, so I can't help you directly with your question.

        If you still don't get any responses here, you can try:

        • Subscribing to the Interest mailing list as asking there: https://lists.qt-project.org/listinfo/interest Qt engineers are active on that list.
        • Contracting KDAB: https://www.kdab.com/ They are an external consulting company who are heavily involved in the design and implementation of the Qt 3D module. Their services might be useful for your project.

        Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

        1 Reply Last reply
        0
        • G Offline
          G Offline
          gde23
          wrote on 11 Dec 2020, 08:20 last edited by
          #4

          I don't know about the Qt 3D rendering stuff. But if you are not tied to that I would suggest giving VTK a try. It has support for large data and typically performs pretty well.

          1 Reply Last reply
          0

          1/4

          6 Dec 2020, 16:18

          • Login

          • Login or register to search.
          1 out of 4
          • First post
            1/4
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved