[=;433659]
I’ve never used Unity - but by the sounds of it, the alternative going by their method is the have an additional file associated with every file in the content folders? Each time you moved something, you’d have to rebuild the DDC as well which can take hours on some projects.
[/]
No, every time you move something, nothing happens.
[=;433659]
Perforce,
[/]
Merging of binary files is not related to the issue in any fashion.
[=;433659]
- I decide I want to move a Particle System or Material referenced by that level, so I move it. Without a Redirector, I would also have to check out the Level as well,
[/]
That’s completely incorrect and you don’t understand how that works.
You won’t need to checkout or even touch the level. When material is not referenced by path, but by guid, level doesn’t care where that material is.
So you can check out local copy, move things around as you’d like, and your level will not be changed in any way. The only change you’ll have to checkin “material was moved from location A to location B”. That’s it. The level will file remain completely unchanged.
Redirector’s however, are a good way to pollute repository with junk information.
You’re trying to guess how it would work based on your understanding of the unity asset system. Your understanding of the system is incorrect, because you never worked with unity. Either read “Asset Management” portion of blog post I linked, or give unity a whirl.
[=;433659]
As much as I’m an Unreal fanboy, there’s a genuine reason for their existence.
[/]
The reason for their existence is “the system originally used paths 10 years ago, and when we started to move things around, we needed a workaround that would prevent paths from immediately breaking”. That’s not a very good reason and the system doesn’t have any benefits.