Table of Contents

For Evaluators & Leasers

Overview

This section provides information on the evaluation version of the SpeedTree SDK given to evaluators and lease clients.


Evaluation Keys

The evaluation version of the SpeedTree SDK requires the use of an evaluation key. This key expires at a preset time, usually 30 days from initial issue. Using the Windows version of the SDK, the key can be passed in with a function call (more below).

Lease clients use the evaluation version of the SpeedTree SDK (i.e. they have limited internal source code) however, they receive recurring year-long evaluation keys until publication. Contact IDV for more information on lease licenses.


Authorizing

To authorize the evaluation libraries within your source code, use the CCore::Authorize() function (in namespace SpeedTree), which is passed the evaluation key string. In a vanilla SDK source distribution, the reference applications will not build until a valid key is entered in CCore::Authorize(), located in MyApplication.cpp (the source issues an #error directive until it is edited). Full versions of the SDK do not require an evaluation key or a call to CCore::Authorize().

If a key is invalid, no SRT files can be loaded, nor will the grass or terrain subsystems function. It is recommended, when integrating SpeedTree into your application, that you print the CCore::GetError() result on failed loads as it will remind you that your key has expired and what the expiration date was. Failed loads can lead some developers to look for bugs when the failure could be a simple key expiration.

Upon becoming a full customer, the source code to the full SpeedTree SDK is made available, as well as libraries built without evaluation key checking. If you are a full customer and your application still reports that it needs an evaluation key, then you are most likely still using the evaluation version (this happens more than you might think!). Switching to the full libraries (to which you will have source) will solve this problem. They are completely unrestricted.


Build Types

Numerous builds are included with the evaluation installer, including VC9, VC10, DLLs, static libraries, multithreaded builds, debug multithreaded, multithreaded DLL, etc. If you need an evaluation build type not found in our standard evaluation kits, you can request a special build from our support team.