Problems With Perforce - RH

“Problems With Perforce”

Author: Ryan Hewitt

Posted on 08/15/2024

The biggest issue I faced this week was getting Perforce to work. Installing the PaperZD plugin and trying to get that to be submitted through Perforce rather than having each person install PaperZD to their local engine was a challenge. There were further issues with trying to get the file structure fixed and having everyone be on the same page.

In order to install PaperZD to our specific project so it could be sent through Perforce, you have install it to the Engine version your project is on and move the plugin folder over to a new Plugins folder in your project files. This would work on it's own, however we were having issues building because of a missing module. This leads to a common issue we had where certain C++ files didn't get updated because they were never checked out. Eventually we figured out that you need to check out the file first and submit it through Perforce so everyone else can get the change. We spent hours today pushing, pulling, generating solutions, cleaning, and rebuilding. We have to clean and rebuild seemingly every time we pull from Perforce, otherwise the dll file for PaperZD cannot open for whatever reason. Changing the file structure was a mess because we had to move and delete files just to get them organized into Public and Private folders, then the header files include paths were all messed up so we had to fix that too.