This page has been translated automatically.
Video Tutorials
Interface
Essentials
Advanced
How To
Basics
Rendering
Professional (SIM)
UnigineEditor
Interface Overview
Assets Workflow
Settings and Preferences
Working With Projects
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Lighting
Sandworm
Using Editor Tools for Specific Tasks
Extending Editor Functionality
Built-in Node Types
Nodes
Objects
Effects
Decals
Light Sources
Geodetics
World Nodes
Sound Objects
Pathfinding Objects
Players
Programming
Fundamentals
Setting Up Development Environment
Usage Examples
C++
C#
UnigineScript
UUSL (Unified UNIGINE Shader Language)
Plugins
File Formats
Materials and Shaders
Rebuilding the Engine Tools
GUI
Double Precision Coordinates
API
Animations-Related Classes
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
VR-Related Classes
Content Creation
Content Optimization
Materials
Material Nodes Library
Miscellaneous
Input
Math
Matrix
Textures
Art Samples
Tutorials

Git

The VCSIntegration Plugin provides Git integration. It tracks changes made to assets in UnigineEditor and updates their statues in the repository automatically via the Git client.

Notice
Within this article, we will use TortoiseGit as the client for Git. The plugin supports integration with TortoiseGit 2.10 and later.

Setting Up Environment#

For VCSIntegration Plugin to operate with Git correctly, you should prepare the environment:

  1. Make sure git and git-lfs are installed on your computer. If the plugin can't locate a Git executable (git.exe is unavailable), it will provide you with the error message. The same will be displayed in the console. In this case, install the client and proceed with setting up the environment.
  2. Add the path to the git.exe file to the PATH environment variable. You can do that as follows:

    1. Type Advanced System Settings in the search bar next to the Start button and click on the matching option.

    2. In the window that opens, click Environment Variables...

    3. Select the system variable PATH from the list and click Edit...

    4. In the window that opens, click New, add the path, and click OK. By default, it will be C:\Program Files\Git\cmd.

Now you can configure your project to use the VCSIntegration plugin and allow tracking changes.

Plugin Operation#

Adding New Asset#

The user imports a new asset pedestal.fbx to the data directory. The new FBX asset, its metadata, and all runtime files with their metafiles will be displayed in the Git Commit. All files will have the Added status.

Renaming Asset#

The user renames an asset from cube.png to sphere.png. The texture asset and its metadata with the new name will show up as Renamed in Git Commit. The previous names of the files will be displayed in the parentheses right after the new names.

The status of the runtime file metadata will be set as Modified.

Moving Asset#

The user moves a non-native asset helicopter_simple.fbx from one directory to another. The asset and its metadata added to the new directory will be displayed in Git Commit with the Renamed status. The previous paths to the files will be displayed in the parentheses right after the new paths.

Deleting Asset#

The user deletes a non-native asset helicopter_simple.fbx. The asset, its metadata, and all runtime files with their metadata will have the Deleted status within Git Commit.

Changing Asset Import Parameters#

When an asset is re-imported with new parameters, its runtime files and metadata will have the Modified status in Git Commit. The asset itself remains unchanged.

Last update: 2024-06-24
Build: ()