This page has been translated automatically.
Click here to view the original English version instead.
Unigine Basics
1. Introduction
1.1. What is an 'Engine'? How Games and 3D-Applications Are Made?
1.2. Getting Started with UNIGINE
1.3. Getting to Know UnigineEditor
1.4. Content in Your Projects
2. Managing Virtual Worlds
2.1. World Structure and Built-In Objects
2.2. Instancing Objects
2.3. World Settings
3. Preparing 3D Models
3.1. Scene Geometry
4. Materials
4.1. Materials Basics
4.2. Working With Materials in Editor
4.3. Textures in Materials
4.4. Creating Your Own Materials
4.5. Working with Texture Editor
5. Cameras and Lighting
5.1. Cameras
6. Implementing Application Logic
6.1. Basics
6.2. PROJECT1: ArchViz
6.3. Working With Components in Editor
7. Making Cutscenes and Recording Videos
7.1. Animations With Tracker
7.2. Making Videos With Video Grabber
8. Preparing Your Project for Release
8.1 Building Your Application
8.2. Packing Your Files
8.3. Launcher Configuration
8.4. Removing Unused Assets
8.5. Copying User Files
8.6. Practice
9. Physics
9.1. Built-In Physics Module
9.2. Collision Detection and Raycasting
10. Optimization Basics
10.1. Performance Profiling Tools
11. PROJECT2: First-Person Shooter
11.1. Assembling a First-Person Setup With Controls
11.2. Shooting Implementation
11.3. Adding Visual Effects
11.4. GUI for Crosshair and Current Game Stats
11.5. Adding Enemies With AI
11.6. Health and Damage
11.7. Controlling the Game Process
11.8. Assembling the Final Build
12. PROJECT3: Third-Person Cross-Country Arcade Racing Game
12.1. Assembling the Vehicle
12.2. Setting Up The Camera
12.3. Implementing Vehicle Physics
12.4. Implementing Controls
12.5. Creating a Landscape
12.6. Implementing Gameplay
12.7. Assembling the Final Build
13. PROJECT4: VR Application With Simple Interaction
13.1. Developing VR Applications
13.2. Creating an Application Using the Template
13.4. Assembling the Final Build
14. Conclusion

Copying User Files

Sometimes you may want to add some files stored outside your project to the build (e.g. end-user agreement, etc.). User files are added to the build folder by filling in the following table:

  • From (Absolute Path) — an absolute path to a source file or folder. Folders can be specified using wildcards.
  • To (Relative Path) — path to the destination folder that is relative of the Build Folder. It can be a name of the folder into which the file or files are copied, or folder name + file name (if you need to rename the copied file).
Last update: 2024-12-13
Build: ()