Important: Please read the Qt Code of Conduct -

Numerical simulator mesh visualization

  • 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?


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

  • Moderators

    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: Qt engineers are active on that list.
    • Contracting KDAB: 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.

  • 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.

Log in to reply