Looking for tips and best practices when One File Per Actor OFPA. The ExternalActors folder can get quite large and if you forget to disable Auto Save can be a huge productivity destroyer.
Also attempting to rename existing ContentBrowser folders containing OFPA assets is a huge hassle. References are still maintained to the old folder and it seems you need to manually delete the old folder as well as its corresponding folder in ExternalActors on the desktop.
Considering the above should you try and always disable OFPA unless using version control and working as part of a shared team?
Or if there are other advantages to OFPA outside of granular version control, should it be enabled at a project level? Or should it instead be enabled at an actor level?
The feature is really only for developing with a team. If you are not, you do not need it.
If you have to rename folders/thing/references, you also do not need your team to have the old project files, you need to force them to do a pull of the latest code base with the correctly named folders/references.
Otherwise you are literally just asking for trouble…
The only advantage to ofpa is that your team can work on multiple things and the reference is updated for everyone instead of locking people out of what you are working on.
Personally, my team just uses git.
The engine’s idea of version control is (at least was, on 4.25) pityful.
On a small team (sub 15 i’d say) there isn’t enoug people to even justify 2 working on the same level/thing and locking each other out…