OMSI will happily follow symlinks when you load your map into the Editor or main game, but when you navigate to an object that you haven't placed before it will just refuse to add it. The only (rather major) issue that I've found is that the OMSI editor won't resolve symlinks when adding objects/splines. SourceTree doesn't get annoyed when I switch OMSI installs either as the project directory doesn't move. For a map project you could store not just the map but all the dependencies in source control too. I can therefore store not just one directory but Fonts, Sceneryobjects and Splines, alongside source material. git directory and that which you can see in the repository on GitHub. Take for example British Road Detailing Pack 2, which is stored in W:\Nathan\GoogleDrive\Dev\OMSI\British-Road-Detailing-Pack\. Once you've installed SourceTree we can link our repository.įor my projects, I store the files in a project directory outside of my OMSI installs, and symlink/copy files across when I need them in an OMSI install. For this tutorial, we will use Sourcetree other alternatives are available and will have a similar process of setting up. Now you need to set up the Git client that will do all the work on your machine. You'll probaby want to set it to private as well. So the steps below will be for the GitLab option.Īfter you've signed up to GitLab click the 'New Project' button, name it what your maps OMSI folder name is called. Personally, I use GitHub but it's a paid service unless you want your repository to be public, for most people GitLab should work fine. But you can always revert changes anyway with Git. Make sure to be careful with multiple installs. Warning: If you have multiple OMSI installs, when you switch Git may freak out. We'll be using Git for this, other alternatives like SVN are available though. Version control systems act as a time machine for your project, with a couple of clicks you can revert to an older version.
0 kommentar(er)
