Kuesa 3D 1.2

Kuesa 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

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.

( 2000$ for those of us that are confused by decimals as positional separators!)

That's for the runtime? There's a confusing distinction between runtime and 3D Studio so I'm still none the wiser.

But to be honest the whole product description confuses me. I'm probably not the target market although it's hard to tell.