Monday 29 July 2013
The CryEngine Sandbox Folder Structure
1. The Bin folders contain executables used to run the game. The number refers to OS bit size. 64 bit OS users should use bin64.
2. The engine folder contains those files that are related to the game engine eg shaders.
3. The Game folder contains .pak files which are compressed archives containing all of the files that make up the game environment including animations, assets, sounds, particles and textures. These .pak files can be extracted and the files contained within can be edited.
4. Config or .cfg files are used to setup the cryEngine SDK configuration on load. Of note are system.cfg which is the default location for config settings and user.cfg which can contain cvars that will be loaded on opening the editor.
5. The dump and log files contained in the sdk folder can be used for debugging in case of errors.
10 Tips and Tricks for the Sandbox User Interface
1. Top left shows the viewport rendering mode and options. Most of the time Perspective mode is the most useful. Others include wireframe, labels, show safe frame.
2. Most functions can be found in 2 or 3 different places around the editor.
3. The top right displays the current viewport resolution. It contains both common monitor resolutions and the option of a custom setting.
4. The filter bar on the top right can be used to display on certain entities to enable us to work on them more easily.
5. On the lower bar we can 'lock selection', change object coordinates or change the speed of the viewport camera zoom. The terrain clipping toggle allows us to choose whether the camera can pass through terrain or collide with it. The AIPhysics turns on the physics for active entities such as animated fish. GoTo position sets the exact current camera position.
6. Movement is best accomplished using WASD and the mouse.
7. Generating a player is achieved using ctrl-g. The user can then set noclip settings using F3.
8. The console is a powerful tool that lets us input exact commands to perform a huge variety of actions. Double clicking on the console shows a list of available valid commands.
9. The most commonly used feature of the editor is the rollup bar on the right. This allows us to create and edit the properties of the entities that make up our game. It contains a number of tabs that let us create, modify or hide objects. It also contains the layer tab for layer management.
10. The most important interface feature is found in the tools and view menus at the top of the screen. All configuration and shortcut objects can be viewed and modified here.
2. Most functions can be found in 2 or 3 different places around the editor.
3. The top right displays the current viewport resolution. It contains both common monitor resolutions and the option of a custom setting.
4. The filter bar on the top right can be used to display on certain entities to enable us to work on them more easily.
5. On the lower bar we can 'lock selection', change object coordinates or change the speed of the viewport camera zoom. The terrain clipping toggle allows us to choose whether the camera can pass through terrain or collide with it. The AIPhysics turns on the physics for active entities such as animated fish. GoTo position sets the exact current camera position.
6. Movement is best accomplished using WASD and the mouse.
7. Generating a player is achieved using ctrl-g. The user can then set noclip settings using F3.
8. The console is a powerful tool that lets us input exact commands to perform a huge variety of actions. Double clicking on the console shows a list of available valid commands.
9. The most commonly used feature of the editor is the rollup bar on the right. This allows us to create and edit the properties of the entities that make up our game. It contains a number of tabs that let us create, modify or hide objects. It also contains the layer tab for layer management.
10. The most important interface feature is found in the tools and view menus at the top of the screen. All configuration and shortcut objects can be viewed and modified here.
Subscribe to:
Posts (Atom)