Candera V3.3.0

• Candera/FeatStd CMake Build System Changes
• Candera Engine 3D
• Candera Engine 2D
• Candera Base
• Candera Scripting
• Candera System
• Candera Device
• Candera Transitions
• TextEngine
• Candera Behavior
• Migration Guide

Candera/FeatStd CMake Build System Changes

---

 

Candera Engine 3D

Changed Light Specular Color to White

Changed default specular light color to White due to feedback from designers. Material default specular color is black anyway, so no specular highlight will occur by default. But if user (designer, technical artist) changes material specular color, an immediate change of appearance will be visible.

Reduction of glGetUniform calls on Shader Upload

By improving handling of Shader Uniforms, the number of calls to glGetUniform during shader uploading was significantly reduced.

Introduction of LoadingHint for DeviceObject.

Version 3.3.0 introduces a LoadingHint for the DeviceObject. Loading hints can e.g. trigger warnings when uploading while rendering, or force unloading from all contexts.

New methods for NodeListener

New methods have been added to NodeListener class. These are:

Candera Engine 2D

Introduction of LoadingHint for DeviceObject2D.

Version 3.3.0 introduces a LoadingHint for the DeviceObject2D. Loading hints can e.g. trigger warnings when uploading while rendering, or force unloading from a context.

New methods for Node2DListener

New methods have been added to Node2DListener class. These are:

TextNode2D cloning strategy

TextNode2D adopts the unified cloning mechanism, with the introduction of DeepTextNode2DCloneStrategy.

For more information see Unified Cloning Interface, Tree Cloning Strategies and Tree Cloner

Improved Pixel Accuracy

Scissoring is now utilized on platforms that support it. This improves pixel accuracy in 2D rendering when a dirty area or a camera scissor is used.

---

Candera Base

Renderer2D3D

A new renderer has been added. It renders the cameras interleaved in order of their sequence-number. This means that 3D-cameras can be rendered between two 2D-cameras and vice versa. The interleaved renderer however, has the requirement that buffer swapping and clearing needs to be done by the according Cameras directly. Therefore auto clear and auto swapping becomes deprecated. Please see the Migration Guide.

DXT image formats

New compressed formats support in Bitmap is avaiable on selected platforms: Dxt1CompressedRgbFormat, Dxt1CompressedRgbaFormat, Dxt3CompressedRgbaFormat, Dxt5CompressedRgbaFormat.

---

Candera Scripting

Lua Update.

Lua has been updated to version 5.3.3.

New Script Callbacks.

This version adds a new callback:

Time interface.

This version adds a new interface to get time information in Lua.

Added uniform functions.

This version adds new functions to Lua to access uniforms through Candera's shader parameter setter.

---

Candera System

Update System

This release adds an update system where entities can be registered to receive any of a series of update calls.

Controller System

This release adds a controller system which offers an abstract interface that the user can implement and attach to entities to receive update calls.

---

Candera Device

---

 

Candera Transitions

New Default Transition Types

The transition framework now supports Cut, Fade, Slide and Scale transitions.

Transition Request Handles

Transition requests can now be assigned a handle allowing creation of multiple requests at once. This is a requirement for courier

---

TextEngine

TTC font iterator.

A function to iterate over the style names of the font faces contained by a TTC font was introduced in the Font.h interface. Additional functions to retrieve the font style name and the font family name of the current font set up are available.

---

Candera Behavior

Added support for Behaviors.

Behaviors have been added to support application development with considering the hierarchy of the scene graphs. Behaviors are small application building blocks that allow the user to create their own application handling. Being similar to Widgets Behaviors have the advantage that they can rely on hierarchical information, as every Behavior has to be attached to a node in the scene graph. By design they can be implemented in such a way that one behavior can even be reused for both 2D and 3D, if no special functionality of the Node below has to be used. Behaviors also support event handling through mechanisms for event routing (to other behaviors) and having a base interface (Behavior::OnEvent) to handle events.

---

Migration Guide

Following an overview about interface changes between Candera V3.2.2 and Candera V3.3.0.