Source control login Perforce doesn't works
Yesterday, I installed P4admin and p4V (perforce). My goal was to log in through the Source control login from UE4 to my local Perforce Server. But the issue i'm encountering is that I get this error each time : " Error Failed to connect to source control. Check your settings and connection then try again. " Or "Error Workspace 'MyProject' does not map into this project's directory."
By the way, my perforce server works great, I can log in without any issues from p4v. So, then, I tried to log in from Visual Studio to my Perforce Server with Source Control Login... And guess what, it works... =_= (The informations filled are the same as UE4 Source control login) :
To resume, when I fill the Workspace field on UE Source Control, I get this error: "Error Workspace 'MyProject' does not map into this project's directory." When I don't, I get this one : " Error Failed to connect to source control. Check your settings and connection then try again. " And I never see any available workspaces from the select list. Meanwhile, I can log in from Visual studio.
I'm loosing hope, I'm tired and I don't understand why it doesn't work, I'm trying to fix it since yesterday. Is something wrong with my UE4 version maybe (4.7.4)?
Oh, thank you for reading and for your replies :)
Have a good day.
asked Apr 05 '15 at 07:29 PM in Using UE4
This is because your UE4 project files and your perforce workspace must be the same directory!
For example: If your workspace is at: C:/UE4Projects/MyGame/
Then your .uproject file must be at C:/UE4Projects/MyGame/MyGame.uproject
And you have to use this .uproject file and connect to this workspace.
This one is most likely caused by an offline perforce server.
You can install the perforce server on your local machine but your mates will not be able to submit / checkout etc.. if your machine is offline or the perforce server is offline.
There is a free perforce hosting: https://www.assembla.com/repositories/perforce
answered Apr 05 '15 at 08:56 PM
Sorry to revive an old thread, but I got the same exact issue and in my case it's intentional. Since I don't have enough space to have my whole workspace (containing multiple projects), I put one of the project in a symlink directory. My workspace is in a directory inside C: but the project is actually in a directory in the D: drive. This causes a bug inside unreal like Azarus said where UE4 project files and the perforce workspace aren't in the same directory.
I've searched everywhere for a solution and at the moment the only thing I could do is create a new workspace...but it's really not ideal. As we are setup right now, each person has only one workspace and we want to keep it that way (we have a max workspace amount available).
Is there any other solution ? Thanks
answered Oct 17 '18 at 03:00 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here