UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Landscape Tool
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Programming
Fundamentals
Setting Up Development Environment
Usage Examples
UnigineScript
C++
C#
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine Tools
GUI
Double Precision Coordinates
API
Containers
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Objects-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
IG Plugin
CIGIConnector Plugin
Rendering-Related Classes

SDK Browser Issues

This section provides information on typical errors displayed in SDK Browser and explains how to fix them.

Activation Issues#

Applications built with the Evaluation kit require SDK Browser installation and SDK activation on each PC. This limitation is only valid for the Evaluation kits.

Please, use an individual account per person to avoid the warning.

Browser Errors#

Settings and issues that may cause errors:

  • Unstable internet connection. This may cause repeated logging off. However, if you are in the middle of downloading something via SDK browser, it will be paused and continue downloading as soon as internet connection is resumed.

    or

    If you have continuous problems with the internet connection, you may consider using a fixed license.
  • The connection error may also be caused by wrong date and time settings. Check that you have actual date and time set.
  • A certain application may block communication between SDK Browser and Editor. To check if this is the issue, boot into a safe mode (for example, Windows 10 safe mode (with Networking)) and try to run SDK Browser and Editor. SDK Browser can load a little bit slower here, please wait. If there are no errors, that would mean that some application running in normal Windows boot is blocking communication between SDK Browser and Editor.

UNIGINE logs errors to the console and the main log file (stored in <UserProfile>/AppData/Local/Unigine_SDK_Browser for Windows or .local/share/Unigine_SDK_Browser for *nix systems), so you can check there for more information.

If your problem still exists, address the support.

Last update: 2020-04-10