Qt3D use cases in automotive and the problems with it: Difference between revisions
Pasikeranen (talk | contribs) (Created page with "Discussed problems of Qt 3D and 3D in general. Qt 3D is more a really good toolset for building 3D engines, it's not a full 3D engine out of the box. It allows one to impleme...") |
Pasikeranen (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
Qt 3D is more a really good toolset for building 3D engines, it's not a full 3D engine out of the box. It allows one to implement 3D engines with modern features. Qt 3D Studio is implementation of a specialised 3D engine on top of Qt 3D. | Qt 3D is more a really good toolset for building 3D engines, it's not a full 3D engine out of the box. It allows one to implement 3D engines with modern features. Qt 3D Studio is implementation of a specialised 3D engine on top of Qt 3D. | ||
Action to KDAB and TQtC: Make this point more clear in our documentation and material. | '''Action to KDAB and TQtC:''' Make this point more clear in our documentation and material. | ||
Also discussed the process of doing real time 3D: | Also discussed the process of doing real time 3D: | ||
Latest revision as of 14:20, 11 June 2018
Discussed problems of Qt 3D and 3D in general.
Qt 3D is more a really good toolset for building 3D engines, it's not a full 3D engine out of the box. It allows one to implement 3D engines with modern features. Qt 3D Studio is implementation of a specialised 3D engine on top of Qt 3D.
Action to KDAB and TQtC: Make this point more clear in our documentation and material.
Also discussed the process of doing real time 3D:
Start with high polygon model. Technical artist optimises the model for target HW. Most often this process involves creating a low resolution model, then baking the details of high detail model as normal map textures to that (as one example). Iterate this until the results run acceptably and look acceptable on the target HW and display. --> Requires ability to test on target HW.