OFPA ( One File Per Actor ) with Source Control that isn't Perforce

Hi there,

I’m on a project that’s using Plastic SCM ( Unity DevOps Version Control )
and will be starting a new map which needs OFPA.
I’ve read in the documentation that Changelist support is built into the editor and you must validate your changes before submitting to Source Control, you ‘should’ submit content through the editor if it’s OFPA content, and Changelist support is only available if Perforce is your source control provider.

So basically am I out of luck? Can I not use OFPA at all and/or will it be highly unstable? Has anyone attempted using OFPA with non Perforce Source Control?

Hi. we use SVN and have a map that’s OFPA - as long as you keep the ExternalActors and ExternalObjects folders under source control you should be fine - we exit out of UE before committing files.

2 Likes

Okay perfect, thank you! Appreciate the rapid response, too :slight_smile:

1 Like

I’m using Plastic as well. like you said, if the folders are already on source control there’s no problem, but if two people are adding actors to the same level, OFPR can make folders named the same, and then when you merge the branches, you get an evil twin merge conflict (folders or assets named the same and having the same directory).
so, this is still a problem but it’s not the end of the world.
@GarfSnacks have you had any problems since?

2 Likes

Oh man, that sounds quite annoying! Im sorry you’re having to deal with that.

I have actually switched studios since I first posted and didn’t run into that issue as I was the only one at the time dealing with the world. I’m back on P4 now

1 Like

We’ve moved to using sub-levels but i’m still not sure on the workflow to collaborate on a level / linear game world. going to post on here and linkedin, but do you have any advice?