Split quick2d vs qt3d rendering in two threads

[dzimiwine]

Hi,
I am developing a 3D model viewer/mesh optimizer application with QML Quick and Qt3D. Some of the files are very very big CAD files, the fps may drop as few as 4 frames per second. User should then be able to perform some actions (through menus and toolbars) to reduce the number of triangles. The problem is that my entire application will likely be rendered at 4 fps (actions, menus, buttons, viewer). Is there a easy way to decouple Quick 2D vs Qt3D rendering?

Regards

[dzimiwine]

Any help? please. It is a bit a blocker for me as I wonder if I should go with QML or OpenGL/C++ old fashion.

[SGaist]

Hi,

Since you're using Qt3D which is pretty new, I'd recommend asking this to the interest mailing list. You'll find there Qt3D's developers/maintainers (this forum is more user oriented)

[dzimiwine]

@SGaist Thanks