# CGI Studio 3.3.0

# Candera V3.3.0

Release Date: November 2016  
  
To keep backwards compatibility for any interface change in the public API the old interface has been kept and marked as deprecated. The deprecated interfaces will be removed in future versions. Compiler warnings will be generated when using a deprecated interface through the usage of Candera Macro CANDERA\_DEPRECATED\_3\_3\_0.

# 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](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_material.html "The class Material describes the color attributes of an object's surface and is primarily used for li...") 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.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### Reduction of glGetUniform calls on Shader Upload

By improving handling of [Shader](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_shader.html "The class Shader is an Appearance component representing a graphical processing unit (GPU) program...") Uniforms, the number of calls to glGetUniform during shader uploading was significantly reduced.

<div class="contents" id="bkmrk--0"><div class="contents"><div class="textblock">---

</div></div></div>#### Introduction of LoadingHint for DeviceObject.

Version 3.3.0 introduces a LoadingHint for the [DeviceObject](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_device_object.html "DeviceObject is the pure abstract base class for all objects which are able to upload or unload itsel..."). Loading hints can e.g. trigger warnings when uploading while rendering, or force unloading from all contexts.

<div class="contents" id="bkmrk--1"><div class="contents"><div class="textblock">---

</div></div></div>#### New methods for NodeListener

New methods have been added to [NodeListener](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node_listener.html "A NodeListener defines hooks that are called when certain Node functions are triggered, e.g. when a Node's transformation changes. In order to register a NodeListener to a Node simply derive from NodeListener and override pure virtual functions with custom code.") class. These are:

<div class="contents" id="bkmrk-candera%3A%3Anodelistene"><div class="contents"><div class="textblock">

- [Candera::NodeListener::OnNodeAdded](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node_listener.html#a4d01c50508f145a5d57fe736621756a1): this is invoked whenever a parent is set for the node;
- [Candera::NodeListener::OnChildAdded](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node_listener.html#a295d6454aefa42188ebc02fc9e50f3d7): this is invoked whenever a child node is added to the node;
- [Candera::NodeListener::OnChildRemoved](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node_listener.html#a1114fc91be13375eb9c699adabb0c735): this is invoked whenever a child of the node is removed.

---

</div></div></div>

# Candera Engine 2D

#### Introduction of LoadingHint for DeviceObject2D.

Version 3.3.0 introduces a LoadingHint for the [DeviceObject2D](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_device_object2_d.html "DeviceObject2D is the pure abstract base class for all objects which are able to upload or unload its..."). Loading hints can e.g. trigger warnings when uploading while rendering, or force unloading from a context.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### New methods for Node2DListener

New methods have been added to [Node2DListener](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node2_d_listener.html "A Node2DListener defines hooks that are called when certain Node functions are triggered, e.g. when a Node's transformation changes. In order to register a Node2DListener to a Node simply derive from Node2DListener and override pure virtual functions with custom code.") class. These are:

<div class="contents" id="bkmrk-candera%3A%3Anode2dliste"><div class="contents"><div class="textblock">

- [Candera::Node2DListener::OnNodeAdded](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node2_d_listener.html#a8ebb0afc488f8da128041dc11d9ceb80): this is invoked whenever a parent is set for the node;
- [Candera::Node2DListener::OnChildAdded](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node2_d_listener.html#ab9e9d94d5a50c6e08def26e7e42d5d9e): this is invoked whenever a child node is added to the node;
- [Candera::Node2DListener::OnChildRemoved](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node2_d_listener.html#a1acb5635774ed5caa1cfc955bc1d0d67): this is invoked whenever a child of the node is removed.

---

</div></div></div>#### TextNode2D cloning strategy

[TextNode2D](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_text_node2_d.html "TextNode2D is a RenderNode that renders text using the attached BitmapBrush effect.") adopts the unified cloning mechanism, with the introduction of [DeepTextNode2DCloneStrategy](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_deep_text_node2_d_clone_strategy.html "This is the default clone strategy for deep cloning TextNode2d See DeepNode2DCloneStrategy for rules...").

For more information see <span style="color: rgb(230, 126, 35);">[Unified Cloning Interface](https://doc316en.candera.eu/link/977#bkmrk-unified-cloning-inte)</span>, <span style="color: rgb(230, 126, 35);">[Tree Cloning Strategies](https://doc316en.candera.eu/link/977#bkmrk-tree-cloning-strateg)</span> and <span style="color: rgb(230, 126, 35);">[Tree Cloner](https://doc316en.candera.eu/link/977#bkmrk-tree-cloner)</span>

<div class="contents" id="bkmrk--0"><div class="contents"><div class="textblock">---

</div></div></div>#### 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 <span style="color: rgb(230, 126, 35);">[Migration Guide](https://doc316en.candera.eu/link/849#bkmrk-page-title)</span>.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### DXT image formats

New compressed formats support in [Bitmap](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_bitmap.html "A 2-dimensional bitmap that can be used as a texture, background or sprite. A bitmap pointing to a va...") is avaiable on selected platforms: Dxt1CompressedRgbFormat, Dxt1CompressedRgbaFormat, Dxt3CompressedRgbaFormat, Dxt5CompressedRgbaFormat.

---

# Candera Scripting

#### Lua Update.

Lua has been updated to version 5.3.3.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### New Script Callbacks.

This version adds a new callback:

<div class="contents" id="bkmrk-fixedupdate"><div class="contents"><div class="textblock">

- [FixedUpdate](http://dev.doc.cgistudio.at/APILINK/group___lua_tutorial.html#LuaTutorialFunctionsCalledByCandera)

---

</div></div></div>#### Time interface.

This version adds a new [interface](http://dev.doc.cgistudio.at/APILINK/group___lua_binding_gobal_data_structures.html#CanderaLuaCanderaTime) to get time information in Lua.

<div class="contents" id="bkmrk--0"><div class="contents"><div class="textblock">---

</div></div></div>#### Added uniform functions.

This version adds new [functions](http://dev.doc.cgistudio.at/APILINK/group___lua_binding_shader_param_setter.html) to Lua to access uniforms through Candera's shader parameter setter.

---

# Candera System

#### Update System

This release adds an [update system](http://dev.doc.cgistudio.at/APILINK/group___update_system.html) where entities can be registered to receive any of a series of update calls.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### Controller System

This release adds a [controller system](http://dev.doc.cgistudio.at/APILINK/group___controller_system.html) 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.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### 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](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_behavior.html "Behaviors are small re-usable functional blocks that communicate via events. Behaviors are based on W...") 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](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_node.html "The class Node is an abstract base class for all scene graph nodes. Each Node defines a local coordin...") 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](http://dev.doc.cgistudio.at/APILINK/group___behavior_base.html#ga70f74ac5da12a27f11a28e55b2aab429)) to handle events.

---

# Migration Guide

Following an overview about interface changes between [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") V3.2.2 and [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") V3.3.0.

<div class="contents" id="bkmrk-description-candera-"><div class="contents"><div class="textblock"><table class="doxtable"><tbody><tr><th>Description</th><th>[Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") V3.2.2</th><th>[Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") V3.3.0

</th></tr><tr><td>RenderTarget Changes due to [Renderer2D3D](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer2_d3_d.html "The class Renderer2D3D is responsible of the rendering with 2D- and 3D-cameras. The cameras are rende...").</td><td>void RenderTarget::SetAutoSwapEnabled(bool enabled);   
bool RenderTarget::IsAutoSwapEnabled() const;   
void RenderTarget::SetAutoClearEnabled(bool enabled);   
bool RenderTarget::IsAutoClearEnabled() const;   
void RenderTarget2D::SetClearMode(const SharedClearMode2D::SharedPointer&amp; clearMode);   
SharedClearMode2D::SharedPointer RenderTarget2D::GetSharedClearMode() const;   
void SetClearMode(const SharedClearMode::SharedPointer&amp; clearMode);   
SharedClearMode::SharedPointer GetSharedClearMode() const;   
</td><td>Use corresponding [Camera](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera.html "A Camera provides Modelview and Projection matrices. Camera is a Transformable.&#42; The eye point is set...") and [Camera2D](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html "A camera defines the view to the scene. At least one Camera2D has to be added to a 2D scene graph and...") settings.   
  
void [Camera2D::SetClearColorEnabled(bool isEnabled)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#a6b5cc304f150b5a9acc20471362ac121);  
bool [Camera2D::IsClearColorEnabled()](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#aec722b464408d247509e7abfb43a1856);  
void [Camera2D::SetSwapEnabled(bool isEnabled)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#aa42862f6adf1211128094f5c27f02c5f);  
bool [Camera2D::IsSwapEnabled() const](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#a018101ef5b70de5330972e594d2bea18);  
void [Camera2D::SetClearColor(const Color&amp; clearColor)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#a2d3d31a572091262dac11dca58050fed);  
const [Color](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_color.html "Represents a color by its red-, green-, blue- and alpha-value. Provides color arithmetic functions an...")&amp; [Camera2D::GetClearColor()](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera2_d.html#a6d6640eeb2afc9ddb2842618e0c23806);  
void [Camera::SetClearMode(const ClearMode&amp; clearMode)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera.html#a0bc080835de611ca1f15dac9346f6b00);  
const [ClearMode](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_clear_mode.html "Describes how a viewport is cleared. The color buffer may be cleared using a given color...")&amp; [Camera::GetClearMode()](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera.html#a0ebc0d670014f34b21de83209a584ea6);  
void [Camera::SetSwapEnabled(bool enable)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera.html#a4d8422ed9703ddb9e0803eae61fe0bc6);  
bool [Camera::IsSwapEnabled() const](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_camera.html#a17eb537a7eef7ac43e993eb838439c47);  
  
\\ Use dedicated clear and swap cameras if you don't want to manage clearing and swapping on dynamic camera configurations.

</td></tr><tr><td>RenderDevice Changes due to LoadingHint</td><td>static bool RenderDevice::UploadBitmapTextureImage(BitmapTextureImage&amp; textureImage, UInt unit);  
static bool RenderDevice::UploadCubeMapTextureImage(CubeMapTextureImage&amp; textureImage, UInt unit);  
static bool RenderDevice::UnloadBitmapTextureImage(BitmapTextureImage&amp; textureImage);  
static bool RenderDevice::UnloadCubeMapTextureImage(CubeMapTextureImage&amp; textureImage);  
static bool RenderDevice::UploadVertexBuffer(VertexBuffer&amp; vertexBuffer);  
static bool RenderDevice::UnloadVertexBuffer(VertexBuffer&amp; vertexBuffer);  
static bool RenderDevice::UploadShader(Shader&amp; shader);  
static bool RenderDevice::DeleteShader(Handle vertexShaderHandle, Handle fragmentShaderHandle, Handle programHandle);  
static bool RenderDevice::UploadRenderBuffer(RenderBuffer&amp; renderBuffer);  
static bool RenderDevice::UnloadRenderBuffer(RenderBuffer&amp; renderBuffer);  
static bool RenderDevice::UploadDirectTextureImage(DirectTextureImage&amp; textureImage, UInt unit);  
static bool RenderDevice::UnloadDirectTextureImage(DirectTextureImage&amp; textureImage);  
</td><td>static bool [Renderer::UploadBitmapTextureImage(BitmapTextureImage&amp; textureImage, UInt unit, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#afc8c92907dac23b2d0f6d7ace2ed64ae);  
static bool [Renderer::UploadCubeMapTextureImage(CubeMapTextureImage&amp; textureImage, UInt unit, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#a59b819d0e19ce1e56105da25999ab139);  
static bool [Renderer::UnloadBitmapTextureImage(BitmapTextureImage&amp; textureImage, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#a0fcfef360c89485f977a6882a69e1d05);  
static bool [Renderer::UnloadCubeMapTextureImage(CubeMapTextureImage&amp; textureImage, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#adf9d2ae1de55a40677784ec4e259db80);  
static bool [Renderer::UploadVertexBuffer(VertexBuffer&amp; vertexBuffer, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#aa0e950c62b2f79e25dfd3e725a35ec5c);  
static bool [Renderer::UnloadVertexBuffer(VertexBuffer&amp; vertexBuffer, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#a208a8ac3c92d3c666da733cc9ed52057);  
static bool [Renderer::UploadShader(Shader&amp; shader, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#a908a2f56a50792c3b306be6a71bbb157);  
static bool [Renderer::DeleteShader(Handle vertexShaderHandle, Handle fragmentShaderHandle, Handle programHandle, const Char\* shaderName, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#a56334d2791c9d8cd2907a80c089dda40);  
static bool [Renderer::UploadRenderBuffer(RenderBuffer&amp; renderBuffer, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#aa0d386d42fe57b9eac5e9b16fb5c3da8);  
static bool [Renderer::UnloadRenderBuffer(RenderBuffer&amp; renderBuffer, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#aaa25ad5a851c68afaa0d3f11ee9762f0);  
static bool [Renderer::UploadDirectTextureImage(DirectTextureImage&amp; textureImage, UInt unit, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#ab08d054cebb93cc923b1336250bad2c4);  
static bool [Renderer::UnloadDirectTextureImage(DirectTextureImage&amp; textureImage, DeviceObject::LoadingHint loadingHint)](http://dev.doc.cgistudio.at/APILINK/class_candera_1_1_renderer.html#ae65db2e46fef51c8b5c9e57fbb5644b5);

</td></tr></tbody></table>

---

</div></div></div>

# Courier V3.3.0

#### Release Info

<div class="contents" id="bkmrk-release-date%3A-novemb"><div class="contents"><div class="textblock">

- Release Date: November 2016

</div></div></div>#### Visualization Changes

<div class="contents" id="bkmrk-asynchronous-loading"><div class="contents"><div class="contents"><div class="textblock">

- Asynchronous Loading Changes
- Candera Transitions for Courier

---

</div></div></div></div><span style="color:rgb(34,34,34);font-size:1.666em;font-weight:400;">Asynchronous Loading Changes</span>

Asynchronous loading of views has been improved to allow more views to be loaded asynchronously. Due to this, the interface has been changed in the following way:

<div class="contents" id="bkmrk-courier%3A%3Aiviewhandle"><div class="contents"><div class="textblock">

1. Courier::IViewHandler::SetCurrentLoadingViewScene and Courier::IViewHandler::GetCurrentLoadingViewScene are no longer used and were made deprecated. [Courier::IViewHandler::SchedulePartialLoad](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_i_view_handler.html#ac53195830ab886297a1779250cb85176) can be used instead to set the views for asynchronous loading.
2. Two new values have been added to the protected [Courier::ViewScene::LoadState](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_view_scene.html#ac4bdd412321fee4b195021b9616c8f86) enumeration type. These are SynchronousLoadState and AsynchronousLoadState and are further used for asynchronous loading handling inside [Courier](http://dev.doc.cgistudio.at/APILINK/namespace_courier.html).
3. Courier::ViewScene2D::SetUploadNode2DTraverser and Courier::ViewScene3D::SetUploadNodeTraverser were made deprecated as new member methods (not static) were added instead. These are [Courier::ViewScene2D::UploadNode2DTraverserSet](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_view_scene2_d.html#a870d2d5a61042fc91c740e58dfe66747 "Allow using an own implementation of an UploadNode2DTraverser by overwritten the method UploadNode2DT...") and [Courier::ViewScene3D::UploadNodeTraverserSet](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_view_scene3_d.html#a17a43b7c993705b8227ee1af54b44250 "Allow using an own implementation of an UploadNodeTraverser by overwritten the method UploadNodeTrave...").

</div></div></div>#### Candera Transitions for Courier

The [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") Transitions have been integrated into [Courier](http://dev.doc.cgistudio.at/APILINK/namespace_courier.html). New [Courier](http://dev.doc.cgistudio.at/APILINK/namespace_courier.html) messages have been added for handling [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") Transitions. These are:

<div class="contents" id="bkmrk-courier%3A%3Acanderatran"><div class="contents"><div class="textblock">

- [Courier::CanderaTransitionRequestMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_request_msg.html) / [Courier::CanderaTransitionResponseMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_response_msg.html) - Messages used for creating transition request fragments (Activate, Deactivate, Finish);
- [Courier::CanderaTransitionControlFlowReqMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_control_flow_req_msg.html) / [Courier::CanderaTransitionControlFlowResMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_control_flow_res_msg.html) - Messages used for indicating beginning or ending composing a request;
- [Courier::CanderaTransitionIndMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_ind_msg.html) - Notifies start and finish events for [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") Transitions;
- [Courier::CanderaTransitionFragmentIndMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_fragment_ind_msg.html) - Notifies start and finish events for [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") Transitions Fragments.

</div></div></div>Also, two new methods have been added to [Courier::IViewHandler](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_i_view_handler.html) and hence to [Courier::ViewHandler](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_view_handler.html): ExecuteCanderaTransitionReqAction and ExecuteCanderaTransitionControlFlowAction. These are further called by [Courier::ViewFacade](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_view_facade.html) when [Courier::CanderaTransitionRequestMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_request_msg.html) and [Courier::CanderaTransitionControlFlowReqMsg](http://dev.doc.cgistudio.at/APILINK/class_courier_1_1_candera_transition_control_flow_req_msg.html) messages are sent.

---

# FeatStd V3.3.0

# FeatStd Events

Version 3.3.0 introduces Events. [Event](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_event.html "Event serves as a base class for user derived events.") serves as a base class for user derived events that are dispatched via an [EventSource](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_event_source.html "Event Source for dispatching events.") to registered EventListeners.

---

# FeatStd Util

#### Simple State Machine

New classes [FeatStd::StateMachine](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_state_machine.html "Use the StateMachine class to define a top state machine or a sub state machine. Each activation will...") and [FeatStd::HistoryStateMachine](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_history_state_machine.html "Use the HistoryStateMachine class to define a top state machine or a sub state machine. A HistoryStateMachine will remember its last internal state. The init state will be only set for the first activation. Afterward the history state will be used.") have been added which allow the composition of a simple state machine.

---

# FeatStd Monitor

#### Logging Memory Pools

FeatStd Monitor supports tracing of memory allocation behavior (alloc/free) now. It supports writing the trace into a file and load this file into the Analyzer afterwards.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### Monitor: CMake flags

The new logging feature provides two CMake flags:

<div class="contents" id="bkmrk-name-description-pos"><div class="textblock"><table border="1" cellpadding="5" cellspacing="0"><tbody><tr bgcolor="#d4d4d4"><th>**Name**</th><th>**Description**</th><th>**Possible values**</th></tr><tr><td>MONITOR\_MEMORYPOOL\_BINARY\_LOGGING\_ENABLED</td><td>Activates the Memory Pool activity logging.</td><td>positive integer</td></tr><tr><td>MONITOR\_MEMORYPOOL\_BINARY\_LOGGING\_FILENAME</td><td>Location where the log-file will be generated. The extension has to be \*.membin.</td><td>file path</td></tr></tbody></table>

</div></div>---

# Analyzer V3.3.0

# Scene Analyzer

A filter functionality has been added to filter a logfile before it is loaded into the Analyzer.   
This filter includes:

<div class="contents" id="bkmrk-deselect-recorder-%28r"><div class="textblock">

- Deselect recorder (Recorder-ID as well as recorder annotation name is supported)
- Timespan
- Hitcount of a recorder

</div></div>---

# MemoryPool-Analyzer Module

A new module for the Analyzer is available now. This module is used in conjunction with memory pools.  
It is possible to trace the behavior of the memory pools (alloc/free) and load it into the Analyzer.   
The Analyzer provides different statistics and analysis functionalities.  
This includes:

<div class="contents" id="bkmrk-memory-over-time-gra"><div class="textblock">

- Memory Over Time Graph
- Snapshot information at selected timestamp
- Memory information listed in tabluar form
- Analysis tools for troubleshooting and typical memory issues

<dl class="see"><dt>**See also:**</dt><dd><span style="color: rgb(230, 126, 35);">[MemoryPool-Analyzer module documentation](https://doc316en.candera.eu/books/analyzer/chapter/memory-analyzer-overview)</span></dd></dl></div></div>---

# SceneComposer V3.3.0

# SceneComposer Usability Improvements

#### Start Screen

A "Start Up" panel was added (Mantis 7202 &amp; Mantis 7366). This panel is opened first when the application is launched and allows the user to:

<div class="contents" id="bkmrk-see-informations-abo"><div class="contents"><div class="textblock">

- see informations about the current platform
- see the list of Recent solutions and to allow loading them
- allow the creation of a new solution based on a template

</div></div></div>In this start screen a welcome page is offered to the user, with multiple friendly functions.

<div class="contents" id="bkmrk-see-also%3A-startup-pa"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Startup Panel](https://doc316en.candera.eu/link/9#bkmrk-startup-panel)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Scene Transition Editor

The new added feature of scene transition editor allows the definition of transitions on a per scene basis and test these transitions directly in SceneComposer's display preview. The user can use the editor to set the transitions to or from a scene just by dragging and dropping effects onto the scene list. Additionally, the transition framework was extended to support cut, fade, slide and scale transitions or combinations of these effects by default. Transitions are also integrated in the behavior system, which allows the user to add interactive controls to the application from the start. (Mantis 7355).

<div class="contents" id="bkmrk-see-also%3A-transition"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Transitions](https://doc316en.candera.eu/books/scene-design/chapter/transitions)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Scripting Improvements

Since this version on, a new category is available under "Import" menu: "Import Scripts". This operation is possible due to the implementation of a script importer. After every validation of a given script, a specific information is displayed in the Output. In this way the user is aware about the fulfillment of the process. Any script can be saved in any state (with errors or not), but it can be validated only on the solution opening or when pressing F8 (Mantis 7267 &amp; Mantis 7490).

<div class="contents" id="bkmrk-see-also%3A-import-scr"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[How to Import Resources](https://doc316en.candera.eu/books/import-of-resources/page/how-to-import-resources)</span> in SceneComposer User Manual
- <span style="color: rgb(230, 126, 35);">[Scripting](https://doc316en.candera.eu/books/scripting)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Camera Look-At Node

A new property was added on Camera: Look-at node. When this property is set the camera is automatically oriented towards the look-at-node. Up direction and look-at direction are not shown anymore in property grid. Look-at direction is discarded (Mantis 6819).

<div class="contents" id="bkmrk-see-also%3A-camera-man"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Camera Manipulation](https://doc316en.candera.eu/link/133#bkmrk-camera-manipulation%C2%A0-0)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Extended Control Functionality

Auto-expand: when the control is dragged and dropped, the control node will not be created. Instead, the content of the control will be directly inserted into the scene, without creating an intermediate group that replaces the control. Behaviors and widgets will still be expanded. A flag to mark controls as auto-expandable was provided (Mantis 7044).

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">---

</div></div></div>#### Export SCL Files

The functionality of FTCCMd.exe was extended. Due to this, it is provided support for exporting SCL files from FTCCmd.exe (Mantis 7794).

<div class="contents" id="bkmrk--0"><div class="contents"><div class="textblock">---

</div></div></div>#### Importers Textual Meta-Info

Since now on the importers support author and file meta-info. Only "Title", "Author", "Description" and "Filename" are added in the description field of the imported FBX Scene or imported Photoshop scene (Mantis 7368).

<div class="contents" id="bkmrk--1"><div class="contents"><div class="textblock">---

</div></div></div>#### Add to Animation Group

In the context menu of any animation a new option is available: "Add to Animation Group..." This allows the user to choose an "Animation Group" item and to add the animation to it (Mantis 7044).

<div class="contents" id="bkmrk--2"><div class="contents"><div class="textblock">---

</div></div></div>#### Extended Control Functionality

Auto-expand: when the control is dragged and dropped, the control node will not be created. Instead, the content of the control will be directly inserted into the scene, without creating an intermediate group that replaces the control. Behaviors and widgets will still be expanded. A flag to mark controls as auto-expandable was provided (Mantis 7044).

At the same time the control functionality was extended by providing support to add default content to anchors (Mantis 7617).

<div class="contents" id="bkmrk--3"><div class="contents"><div class="textblock">---

</div></div></div>#### Export SCL Files

The functionality of FTCCMd.exe was extended. Due to this, it is provided support for exporting SCL files from FTCCmd.exe (Mantis 7794).

<div class="contents" id="bkmrk--4"><div class="contents"><div class="textblock">---

</div></div></div>#### Refresh Reference Files

If a SCL is used in a solution and the SCL is exported to the same location where the reference is used from, the modified SCL shall be automatically detected by the application and the user is notified through a dialog box. The user can choose if the application should be reloaded or not. In this way the modifications are imported. If the user chooses not to reload the solution, the SCL reference is marked as outdated (Mantis 7333).

<div class="contents" id="bkmrk-see-also%3A-reusable-s"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Reusable Solution Libraries](https://doc316en.candera.eu/link/47#bkmrk-page-title)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Importers Textual Meta-Info

Since now on the importers support author and file meta-info. Only "Title", "Author", "Description" and "Filename" are added in the description field of the imported FBX Scene or imported Photoshop scene (Mantis 7368).

<div class="contents" id="bkmrk--5"><div class="contents"><div class="textblock">---

</div></div></div>#### Timeslider Improvements

To make the work with the timeslider easier, since now on when double clicking a key frame in both "Animation Timeline" and "Animation Value", the marker will be instantly moved at this key (Mantis 7387). At the same time, the timeslider can be moved by using "Move marker to selected keyframe" option from the context menu of any keyframe available in "Animation Timeline" or "Animation Values" panels (Mantis 7388). Edit Value - edit keyframe popup dialog - is now a context menu item and is not triggered anymore via double click.

<div class="contents" id="bkmrk-note%3A-when-a-shortcu"><div class="contents"><div class="textblock"><dl class="note"><dt>**Note:**</dt><dd>When a shortcut is modified in order for the changes to be visible in SceneComposer, the next file must be regenerated (deleted and automatically recreated): 

```
	%userprofile%\AppData\Roaming\FTC.Launcher\v3.2.2.2\ShortcutProfiles\Default Profile
```

</dd></dl><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Timeline Editor](https://doc316en.candera.eu/link/21#bkmrk-page-title)</span> and
- <span style="color: rgb(230, 126, 35);">[Animation Values - Keyframes](https://doc316en.candera.eu/link/20#bkmrk-page-title)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Remove AutoSwap and AutoClear in 2D/3D from RenderTarget

AutoSwap and AutoClear options (on RenderTargets) were simplified and they became only SceneComposer features. Auto-Clearing was simplified and when enabled, only a property for choosing the clear color becomes available. These properties are not serialized into the asset - they will not be available into Player (Mantis 6831).

<div class="contents" id="bkmrk--6"><div class="contents"><div class="textblock">---

</div></div></div>#### Interleaved Rendering of 2D and 3D Cameras

Rendering in SceneComposer is no longer done separately (2D and then 3D). Now, cameras are interlevead. This means that sequence numbers are global, and not category-specific (2D or 3D). A consequence of this is that Render Targets Panel / Camera Sequence Editor shows interleaved 2D and 3D cameras - it shows effective rendering order (Mantis 6828).

<div class="contents" id="bkmrk--7"><div class="contents"><div class="textblock">---

</div></div></div>#### Saving Asset Location

Together with values as "Shader Compiler Type", "Float Number Format" and "Custom ID", the "Asset Location" value can be saved in a specific user defined "Asset Profile" (Mantis 7227).

<div class="contents" id="bkmrk-see-also%3A-save-an-as"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>

- <span style="color: rgb(230, 126, 35);">[Save an Asset Profile](https://doc316en.candera.eu/link/87#bkmrk-saving-asset-profile)</span> In SceneComposer Manual

</dd></dl>---

</div></div></div>#### Minor Improvements

<div class="contents" id="bkmrk-control-integration%3A"><div class="contents"><div class="textblock">

- **Control Integration:** The "composite" category was renamed "control". This renaming was done only in UI. The underlying structures (users will notice in SCML) are still named "Composite" (Mantis 7348).
- **Collapsed Categories:** In the "Properties" panel, both categories "General" and "Asset" are collapsed by default because, usually, such categories are not required (Mantis 4119).
- **Navigation Between Items:** Inside the "Generate Asset Library" dialog it is possible to navigate between items by using the "Tab" key. The Combobox border was changed to make it always visible when in focus (Mantis 7255).
- **New Label:** "Item Definition" label from "Add New Render Target" dialog has been changed to "Render Target Template" (Mantis 7244).
- **Default Panels:** When starting SceneComposer the following panels are hidden by default: [Candera](http://dev.doc.cgistudio.at/APILINK/namespace_candera.html "&#91;DataBinding&#95;RefTypeSample&#93;") Logging, Render Order Bins, Appearance Editor, Shader Editor, Scripting Editor, SCML Editor (Mantis 7347).
- **Automatically Created:** The steps to created display and render target are removed from the new solution wizzard. These shall be automatically created (Mantis 7430).
- **Re-enabled Properties:** Initially Depth Clear and Stencil Clear were disabled for 3D cameras, now they are no longer disabled (Mantis 6831).
- **Set Pivot:** Center pivot option is now available for 2DNodes (Mantis 7650).
- **Plugins Info:** The plugins can be specified in the plugins.config.xml file (Mantis 7457).
- **Limited Editing:** Since now on, the appearance templates cannot be edited with drag and drop (Mantis 7349).
- **Type Ahead on Shader:** The "Type ahead" was added in the "Add New Shader Program" dialog. When the user types a letter, the first shader starting with that letter is highlighted (Mantis 7054).
- **Calculator Integration:** A calculator is available for all the properties of type int, float, and sbyte properties where the user has to enter a number (Mantis 5578).
- **Dragged Camera:** The cameras obtained as results after a search operation can be dragged and dropped into camera groups (Mantis 7046).
- **Open in File System:** An "Open in File System" context menu option was added on the top level solution in the "Solution Explorer" panel (Mantis 7237).
- **Create Templates:** An "Add Template" command was added for each category from Templates panel (Mantis 7051).
- **Add to Animation Group:** In the context menu of any existing animation, an "Add to Animation Group..." option is available (Mantis 7044).
- **Description for Nodes:** A new "Description" field is available on nodes (Mantis 7272).
- **New Checkbox:** An "Add Camera and Light" checkbox was added in the "Add New Scene..." dialog (Mantis 7239).
- **Shader Template:** When creating a new shader, a predefined template is offered to the user in the "Shader Editor"(Mantis 7241).

---

</div></div></div>