VeriorPies / ParrelSync

(Unity3D) Test multiplayer without building
MIT License
4.67k stars 323 forks source link

[BUG] Creating clone doesn't copy everything and the cloned project cannot be opened. #96

Closed gbradburn closed 1 year ago

gbradburn commented 1 year ago

I am trying to create a clone of a multiplayer project for testing. I get no errors when creating the clone but the clone is missing most of the folders from the original project and Unity Hub won't let me add it because it says it's not a valid project.

To Reproduce Steps to reproduce the behavior:

  1. ParrelSync Clones Manager
  2. Add new clone
  3. Wait for it to finish creating the clone
  4. Click Open in New Editor
  5. Unity Hub opens but the clone doesn't appear. Trying to add it gives the error that it can't be added because it's not a valid project.

Expected behavior A valid clone of the project should be created.

Screenshots/Video image

Enviroment (please complete the following information):

Additional context Add any other context about the problem here ParrelSync log.txt e.

MrPatben8 commented 1 year ago

Experiencing the same issue on 2021.3.18f1

MrPatben8 commented 1 year ago

I did some digging. Does your project happen to be on a external drive or a non NTFS drive? It seems only NTFS drives are required to support the symbolic links that are used for the clones.

gbradburn commented 1 year ago

Thanks for digging. No, my project is on an internal SSD.

MrPatben8 commented 1 year ago

Is the SSD your C drive? And is it formatted as NTFS? I fixed my issues by moving the project to my C drive. In any case the issue certainly seems to be because windows can't creat a symbolic link to your project. Hope you can get it sorted

gbradburn commented 1 year ago

Hmm, the project drive (F) in my case is actually exFAT, not NTFS.

MrPatben8 commented 1 year ago

Ah! Try moving it to your C drive (or any other NTFS drive) and see if that works.

gbradburn commented 1 year ago

I think my D drive is NTFS but it's not an SSD :( I'll give that a try. I guess I can close this "bug" since we now know what the issue is.