Working on a Unity project on 2 PCs

>>61611499
Should ask >>>/vg/agdg, anyways if you are sharing assets too forget things like git and go for something svn-like. Perforce is widely used in the industry.

>>61611499
Setup a shared folder within the network and just work on separate classes and assets, then compile from time to time to test.

>>>/r9k/38685915

>>61611499
Git

>>61613350
Alternatively, Unity collaborate

>>61611499
ignore file

Tell me u don't use C#

svn if working alone, else git

I prefer git, but work I use perforce with 100+ ppl

>>61613979
Tell me you don't use JS

>>61611499
>what is a better engine to do this
engine has nothing to do with how you collaborate and share work.

if you want a quick shitty way, just sync a google drive folder and give your partner access. make a special folder for yourself for things you're currently working on, and make it read only.

Ideally, you will want to segregate things so that you can work on different parts of the game without stepping on one another's toes. This is true of any software project, and one of the reasons for why merging branches can be difficult.

Specific to unity, you may find it useful to use additive scene loading so that you can load in different game/level components incrementally. What this buys you is the ability to make a scene a "system" scene and a different scene a "level" scene. A programmer can modify the system scene in a separate project while a designer creates level scenes in a different project. They can then export the scene and related assets and import that back into the programmer project (or a central project) for testing. The system scenes loads a level scene on top. Such a strategy will probably want to read up on the DontDestroyOnLoad gameobject flag.

It's often useful to explore editor scripting, as well as scriptableobjects. A programmer can build productivity tools quickly inside the editor. It's a handy way to waste time while designers are dicking around.