-
Notifications
You must be signed in to change notification settings - Fork 332
Troubleshooting & FAQs
Yes, you can.
Yes, it should. If the cloned projects are inside the folder with version-control, ignore it (cloned project folders are placed right next to the original project folder).
Take git as example, you may want to add something like *_clone_[0-9]*/
to your .gitignore
Saving assets directly from the clone editors is not recommended since it may be overridden by other editor instances. By default, asset serialization is being disabled on all clone instances and changes can only be made from the original project editor. This feature can be disabled from the preferences window if needed.
Changes need to be saved to the disk to be reflected in the clone editor, to make sure this happens:
- In the Original Editor: Do "File -> Save" and "File -> Save Project".
- In the Clone Editor: Manual refresh by pressing "Ctrl + R" or Enabled "Auto Refresh" in "Edit->Preference->General" (which is enabled by default)
-
Make sure your project folder is being placed on a file system that supports the symbolic link. For example: NTFS
(Some file system commonly used in external storage, such as exFat, FAT32, doesn't support symbolic links) -
Make sure the project path length won't exist 260 characters, as this is the default Windows limitation.
-
Check project path to ensure there's no space/parenthesis in the paths (related issue #95)
ParrelSync is determining the clone running status by checking the Temp/UnityLockfile
file.
However, in some cases(ex: Unity crash), the Temp/UnityLockfile
won't be cleaned up.
If this happened, try deleting the Temp
folder to reset the clone running status.
This is a known issue before ParrelSync 1.5.0, please update to a newer version (>=1.5.0) if this happens to you.
The "Packages" folder will only be synced at the clone project launched. If you have made changes to the packages, please close and re-opened the clone projects.
There's a Sync Packages Folder
in the clone manager window, click it to manually trigger the package sync.
This is a known issue about .NET Standard 2.0 capability, please update to a newer version (>=1.5.3) if this happens to you.
Please refer to this issue: https://github.com/VeriorPies/ParrelSync/issues/61