Advanced Search
Search Results
1387 total results found
Use Specialized Shaders
Texture Cache Use Shaders that are customized to fit exactly your special situation. Reference shaders are full featured and functional code examples to demonstrate the interoperability with Candera. They are not optimized for performance. A great performanc...
Carefully Design your Lighting
Use Texture Compression Per-vertex lighting is less expensive than per-fragment lighting. Use as few lighting sources as possible (usually one light source is enough). Use simplified, tailored lighting calculations. Use light ranges to reduce the ill...
Optimize Shader Program Coding
Avoid if-else Constructs in the Shader The use of if-else statements for non-constant variables (attributes, varyings and local variables) should generally be minimized or avoided in shaders, as they might lead to synchronization penalties due to different pr...
Prerequisites
CMake In order to build CGI-Studio Applications, the Meta build system CMake needs to be installed with at least version 3.19.0 CMake is able to create the build system for the development IDE of choice, e.g.: Visual Studio (multiple versions) GC...
Build Process
Description The following chapters provide some information about build process aspects. Using CMake for Building Courier resp. Courier Applications General Setup Courier including it's sample applications provides a complete cmake environment for targeti...
Platform Configuration
Description Some platform specific topics are described here. Platform Definition A Courier platform definition describes the complete setup for a dedicated platform. This comprises the implementation of the various platform interfaces defined in Courier::...
Introduction
CGI Studio provides an integrated development environment based on Visual Studio for widget and application layer development, located at: <cgi-studio-root>/cgi_studio_player In the cgi_studio_player directory, 4 different projects are define...
Building CGI Panel
The CGI Panel is a C# project which provides a graphical interface which supports the control of scenes and animations by managing the flow of the Player. Building CGI Panel Usually there is no need to build the CGI Panel on your own, since the executable i...
Building Player and Widgets
Building Player and Widgets The Player executable used by CGI Panel collects following components: Candera Engine including Candera Device Platform Player as a demo application for loading assets and displaying / manipulating content: <cgi_studio_ro...
Activating Additional Behaviors for Player
To include the behaviors part of CGI Studio in the Player, simple enable the CMake option CGIAPP_ENABLE_ADDITIONAL_BEHAVIORS before generating the CGI Application solution with CMake. The CMake option CGIAPP_ADDITIONAL_BEHAVIOR_PATH is already preconfigured ...
Building SCHost for SceneComposer
To make the same set of widgets available for SceneComposer, as they are for the Player, a new SCHost.dll needs to be created and deployed to SceneComposer. Enable COURIER_ADD_SCHOST_PROJECT in the CMake project in order to add the SCHost project...
Customizing Widgetset Generation
Customizing Widgetset Generation For adding your own behaviors and widgets to the default widget set, it is required to specify them in the widget set definition (WidgetSet.cpp), which is finally accessed by SceneComposer to provide all exported behaviors and...
Candera Version Validation
To ensure, that an application like the Player always refers to the proper Candera version, following CMake configurations can be used: <CANDERA_DIR>/CgiStudioCanderaConfig.cmake: This file specifies the actual version of Candera, e.g.: set(CGI_CANDERA_VERS...
Using Player on 64 bit Systems
For Player, the CMake project generator should be of type Win64 (e.g. Visual Studio 15 2017 Win64) and it should be built with the "COURIER_PLATFORM_CONFIG" setting set to "x64". This is the only way to build a SCHost.dll that can be used in SceneComposer
Debugging Hints
Debugging Player For debugging the Player set "Player" as startup project in the Player solution and start debugging. With CMake, the required Debugging configurations are preconfigured as following: Debugging Widget Life Cycle in SceneCompos...
Select Features
CMake feature switches have been renamed for V3.x releases, see Change Log Select Candera Features Build settings for the Candera Engine are specified by the following CMake variables: Name Description Possible values ...
3rd Party Software: FreeType2 Configuration
3rd party software FreeType2 is used by the Candera Engine and can be configured in CMake like this: Name Description Possible values FREETYPE2_CUSTOMIZE Enable or disable FreeType2 customization. ON/OFF FREETYPE2_FORCE_DEFAULT_CONFIG ...
Candera Device Packages
Supported Device Packages Candera provides device implementations for following device types: Name Description Possible values Other proprietary devices Can be provided upon special request ON/OFF Device-Specific...