4 ms·
I spent several minutes trying to understand those paragraphs, finding them incomprehensible. I figured maybe I was just too tired, but seeing your similar rea
by mkl 6y ago
I spent several minutes trying to understand those paragraphs, finding them incomprehensible. I figured maybe I was just too tired, but seeing your similar reaction makes me feel vindicated!
jcelerier, can you explain it?
- jcelerier 6y agoKuesa 3D Studio is a product allowing a team to integrate realtime 3D in an application, trying to create a smooth workflow for the communication between the designer and the developer, centered around the glTF 2.0 format. To give some insight on the technical aspect of things, one of the main reasons you would want to use Kuesa is to be able to easily integrate glTF content in a Qt and especially QtQuick app, and be able to access all the parts of what's provided in this glTF data in a reactive way through QML. e.g. here is some code example from the documentation: https://kdab.github.io/kuesa/kuesa-car-scene-example.html https://kdab.github.io/kuesa/kuesa-car-scene-example.html The main point is that Kuesa enable a workflow where someone sends you a glTF file with whatever name for animations, etc... You quickly introspect them through the provided glTF editor (part of Kuesa 3D Studio) and check that the rendering is correct with the chosen materials, envmap, etc (as designers extremely often expect things to look just like their beautiful Blender or 3DS renders :-)). Most importantly, you use that to devise what names were used for animations, materials, meshes, scenes, etc - basically which part of the asset will map to which feature of the program you're writing. Kuesa 3D Runtime (basically, the "core" execution engine that integrates with Qt and Qt3D) then provides the following: You load the glTF asset through something like Kuesa.GLTF2Importer { source: "my_asset.gltf" } and then you can start referring to the subparts of it and connect them to e.g. UI controls, external inputs, by using fairly simple code. e.g. you can have in your file defining the 3D scene: MyScene.qml: Scene3D { // ... Kuesa.AnimationPlayer { id: rightDoorAnimator sceneEntity: scene clock: Clock { } clip: "DoorRAction" // a glTF clip name } } and then a simple UI such as : MyUI.qml : Row { property var MyScene scene Button { onClicked: scene.rightDoorAnimator.running = true } } and likewise for all the common material properties, meshes, etc.
- bogwog 6y agoSo it's an app for viewing gltf models, and a library for loading/rendering gltf models in Qt?
- jcelerier 6y ago- The glTF viewer application is an helper to integrate the model in your own application - The library allow to load/render and interact with the model as it exposes glTF properties & subparts - Everything can be done in a rich Qt application, either full 3D or mixed 2D / 3D, using C++ or QML It also provides a nice PBR pipeline, various post-processing effects, etc.
- HelloNurse 6y agoLike VRML, more capable and better looking, but also more complicated and rather proprietary? Taking straightforward rendering of scenes with a 3D engine's general purpose lighting, material etc. systems as a baseline, what kinds of applications would find the kind of object model this library supports more useful than fancy 3D models and fancy shaders and algorithms?
- jcelerier 6y ago> Like VRML, more capable and better looking, hopefully ! > but also more complicated and rather proprietary? Kuesa Runtime is under AGPL license and provides a lot: https://github.com/KDAB/kuesa https://github.com/KDAB/kuesa > what kinds of applications would find the kind of object model this library supports more useful than fancy 3D models and fancy shaders and algorithms? There will be a webinar in two days in which questions can be asked, etc. - as I'm not sure I could provide as good answers as the ones you will get there: https://us02web.zoom.us/webinar/register/WN_mSYcLpsKSE-E3KUaVk3oyg https://us02web.zoom.us/webinar/register/WN_mSYcLpsKSE-E3KUa...
- nybble41 6y agoIs it possible to use the runtime with glTF2 files exported directly from Blender[1], i.e. without involving Kuesa 3D Studio? If so, are there any features of the runtime that can only be utilized in combination with Kuesa 3D Studio? For the features which could be utilized on on their own (if any), what are the advantages of working in Kuesa 3D Studio rather than exporting straight from Blender? [1] https://docs.blender.org/manual/en/2.80/addons/io_scene_gltf2.html https://docs.blender.org/manual/en/2.80/addons/io_scene_gltf...