Skip to end of metadata
Go to start of metadata

Overview

The CRYENGINE SDK is provided in .zip archive format. There is no installation required, simply extract the .zip archive to a suitable location with a few advisories:

  • Don't run the SDK from the User folder (includes Desktop, Downloads, My Documents, etc).
  • If possible, run the SDK with administrator privileges to ensure you have enough system access for the engine to perform every task.
  • Don't use spaces in the path (example - c:\my stuff\cryengine).
  • Don't use non-ascii characters in the path (example - c:\mÿstúff\cryengine).

Steam - EaaS

Icon

In case you are downloading the SDK using a Steam subscription, you can skip the above steps. The Steam distribution will already be extracted in a folder on your computer.
You can locate this folder by right-clicking the CRYENGINE item in your Steam library list (filter on "All software"), going to the "Local files" tab, and pressing "Browse local files...".
This will open a Windows Explorer window in the location where the SDK was installed using the Steam distribution. 

Once that is done you should update the plugins for any DCC tools you may use. See Installing Exporter Plugins for more information.

Last step before you get started is to setup the Resource Compiler via the Settings Manager. This setting is used for the exporters to find the Resource Compiler of CRYENGINE to finish processing exported assets.

System Requirements

Icon

CRYENGINE 3.6 has a minimum system requirement of DirectX 11.

System Requirements for Developer

Operating System

Windows Vista SP1, Windows 7, Windows 8. (64bit only)

Processor

Intel Core 2 Duo 2GHz, AMD Athlon 64 X2 2GHz or better (multi-core processor is strongly recommended)

Memory

4 GB RAM (8 GB recommended)

Graphics Card

NVIDIA series 400, Radeon HD 6000 Series or better (DirectX 11 minimum)

System Requirements for End User

"End User", who only uses the game launcher without Sandbox has lower system requirements.

Operating System

Windows Vista SP1, Windows 7, Windows 8

Processor

Intel Core 2 Duo 2GHz, AMD Athlon 64 X2 2GHz or better (multi-core processor is strongly recommended)

Memory

2 GB RAM (4 GB recommended)

Graphics Card

NVIDIA series 400, Radeon HD 6000 Series or better (DirectX 11 minimum)

Additional Software Requirements

For 3.6, the following software is required:

For 3.5, the following software is required:

  • DirectX End-User Runtime (August 2009 and June 2010).
  • Visual C++ 2010 Redistributable Package (both x86 and x64).
  • Latest graphics card drivers.
Icon

In case you downloaded the SDK using Steam, the required DirectX and Visual C++ runtimes will be installed automatically when the application is first launched. However, it is advisable to update your graphics card drivers if you encounter problems. 

Notes on 32-bit Support

Icon

As of CRYENGINE 3.6, 32-bit Editor support is discontinued. Only the 64-bit Editor is supported.

 Click here to expand...

The SDK contains a 32-bit version of Sandbox but we highly recommend to use the 64-bit version for production since it does not suffer from memory limitations.
The 32-bit version is just provided as-is without any further support by Crytek. Using the 32-bit version of Sandbox might result in the application crashing when doing a lot of editing work on a level.

Running CRYENGINE On Different Platforms

PC (Windows)

  • In Bin32 you will find the 32-bit executables of CRYENGINE (GameSDK.exe) and Sandbox (Editor.exe, pre-3.6).
  • In Bin64 you will find the 64-bit executables of CRYENGINE (GameSDK.exe) and Sandbox (Editor.exe).
  • DCC exporters and additional tools are stored in the Tools directory.

Consoles

See the specific documentation area for each support console platform.

Windows and Hot Reload Issue

 Click here to expand...

The Last Access Time is the time a File or a Folder is accessed the last time. This helps identify document age and status. This is disabled by default in Windows Vista and Windows 7 by default as this can add to the overhead of Disk I/O and performance although with the newer hardware this can be anything close to negligible.

Enabling Last Access Time is recommended when running Sandbox in parallel to exporting assets from Max or Maya.

If you choose to enable the Last Access time in Windows 7, 2008, Vista or earlier versions you can either use FSUTIL (not available in Windows 2000) or from the Windows Registry.

Using FSUTIL (not for Windows 2000)

From the Command Prompt as an Administrator run the following command: (In Windows 7/Vista/2008, click Start – search for cmd.

Right-click and choose "Run as Administrator" to run Command Prompt with elevated privileges) then type the following to enable Last Access Time recording:

fsutil behavior set disablelastaccess 0

Later if you need to disable, run the following command:

fsutil behavior set disablelastaccess 1

From Windows Registry

1. Click Start – search "regedit" (Windows 2000/XP/2003 Start – Run – regedit) to launch Windows Registry Editor.
2. In the left-pane, navigate to the following registry key:

3. In the right-pane, double-click NtfsDisableLastAccessUpdate and set its value to 0. This key doesn't exist by default in Windows XP, 2003 and earlier, so in the right-pane right-click and select New – DWORD and name it as NtfsDisableLastAccessUpdate and set its value as 1.
4. Restart the system for the changes to take effect.

Source: http://msdn.microsoft.com/en-us/library/ff794679%28v=winembedded.60%29.aspx

Running the Evaluation Version

 Click here to expand...

The evaluation version of Sandbox is protected to avoid public abuse. Therefore, in order to use Sandbox, an evaluator must enter one of the provided License Keys to validate the Sandbox installation.

In order to enable communication to the CRYENGINE LicenseServer, port 25379 must be open either from the client or from your proxy.

If your network is secured by a proxy, you can make sure Sandbox connects through that proxy by setting the following console variables to file system.cfg, in the CRYENGINE install directory.

Obligatory:

net_proxy_ip
net_proxy_port

Optional:

net_proxy_user
net_proxy_pass
  • No labels