Search the Community

Hello, I am working to establish an effective pipeline for landscape creation for our work environment(Using Unigine 2.7.1). We use P4V for source control and have run into an interesting hiccup regarding read-only files. After landscape generation, the landscape and world look fine on my local machine. However upon pushing the files to the P4V Database, my local files become read-only unless I check them out from P4V. This is where we ran into the hiccup. Once the local .uts and .utsh files are pushed to the Database and marked Read-only, upon startup of the level, the engine fails to load them properly. I tested several cases and it appears that it requires write permission in order to properly load the .uts and .utsh files and display the landscape. This is true for all PC's that sync the world and landscape content to their local files. Each needs to check-out the files, flagging them as write-enabled, in order to load the landscape. This was also able to be replicated without using P4V, by simply using Windows Explorer to mark the .uts and .utsh files as read-only. Naturally we would like to avoid this file check-out clutter in our process, however I understand that this may be a misunderstanding as I am still learning Unigine. I'm interested in any thoughts that could help or shed light on the situation with .uts and .utsh file types. Thank you!