What is the point of not having auto fix up redirectors?
When you move folders inside your content folder, you have to use the function "FIx up redirectors". But why not fix those in the first place, when initially moving folders? It seems this could improve usability and there seems no advantage in not having this happen automatically.
Imagine you are working on some huge game with many coworkers and you are using svn. Now you need to move object to some other folder, but some of you coworker already used this object in some levels that they are working on right now. If you move it, it will get lost in their levels. But if you move it and leave redirector... then theyr level will just look at redirector and find the stuff where you moved it (and committed of course). If you fix redirector... you need to crawl through all levels it was in. (or if you have material... you need to crawl through all meshes you used this material etc.) and the commit it to server. So if anyone else is working on this level (material....) you will create branch split in backup server. So redirector will keep all in order without needing to recommit all stuff it was used in. I personally fix them and recommit all I changed (but i do it in time i know no one else is touching the files)
Its not meant to be used in single user project, but rather in team environment. Hope this clarifies the stuff.
answered Jan 29 '18 at 03:57 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here