Part 1: When source control, doesn't

Our team had a good work flow, good communication and knew where we needed to be and how to get there. Each member was able to do their task and achieve the goal set forth. As we worked towards this build we found a few issues with the way we were trying to implement but we were able to come together and figure those out. However what we were not prepared for was, well two things really, perforce not checking out and checking in our code files and somehow our project got opened with UE5.2. Now these might not seem like overly complicated problems but let me tell you... For some reason the code files not getting checked back in was more of a headache then dealing with  reverting changesets back to UE5.1. Trying to open the project would fail because the code failed because we didn't have all the files. When a member tired to edit the .build file to ensure we had all the modules we needed it wouldn't save and push. We were all up until well after midnight trying to fix this problem.

Part 2: Plugins and long hours

Once we identified our problems we set to work to ensure we could deliver our game. We spent a long time trying to get all the correct code files pushed and working. This part was not as straight forward as we would have liked. Unfortunately perforce and visual studio don't get on together, not with out some outside help but we'll get to that. In our sleep deprived states we probably were not thinking as clearly as we could have been. We would have one member try and check out all their files then push and the other members would pull. This worked some what but each member would miss a file or perforce would have an issues trying to push/pull it. Once we kinda had that figured out, at least enough to get it to each other, somehow the engine got it in it's mind that we wanted to use 5.2 despite none of us having it installed. This was a bit easier to fix thought, I just rolled back the uproject file back to a previous changset and it was good to go. Sadly I was doing that at a later time so it wasn't as smooth as all that but I figured it out. Now for the problems with the code files, I found a plugin for VS which is called P4VS it links to the repo and will ask you to check out a file when you try and edit it, it then records it in perforce and when you go to check in your changes they are all listed there. This was such an easy thing to set up I kind of surprised it's not mentioned. Maybe others aren't having these issues that our team our but if you do, the solutions isn't long hours it's simply plugins!

Me trying to figure out why nothing is working lol

Author: Dewayne Hicks

07/21/23