Sharing C++ LE Project

[Rick]

What is the best way to share LE C+ projects? Ideally we would want a source control for the VS solution, but something like google drive/dropbox for the LE stuff (maps/models/etc). However since the solution is a subfolder and google driver doesn't seem to let you decide what subfolders/files to NOT sync anytime you change locally it'll update the solution on google drive which isn't what you want because you want that controlled with bit bucket or some other source control.

 

This setup doesn't seem that great, but artists generally don't know source control and you generally don't want binary files in course control anyway.

 

How is anyone else setting this up?

[YouGroove]

Is community project starting again ?

http://www.leadwerks.com/werkspace/topic/8946-leadwerks-opengame-project/

Would be great.

[shadmar]

Github for both code and assets, it's really great once you get use to it. Best diff tools and branching I've ever used.

 

https://github.com/shadmar

[AggrorJorn]

Github or bitbucket. In combination with git or mercurial.

[Rick]

so you guys are using github/bitbucket for everything? All art assets and everything?

[AggrorJorn]

I do.

[shadmar]

For collaboration yes. Privately I use git and a NAS.

[Josh]

One solution in the future might be to use Steam Workshop to sync assets. It is possible to set the items up to be friends-only, private, or public. The artists could use that to easily distribute assets to the rest of the team.

 

It's really quite nice because if I have a map that uses textures, models, and other stuff from the Workshop I can just send the map to someone without including any files, and the editor automatically downloads the dependencies.

[cassius]

That's great for team workers.For me and my bad eyesight prefabs are easier to see in the asset browser without textures etc.