I created an SVN server on my Debian server, set the correct settings, and connected to it with Unreal Engine.
Then I commited the content into my server using Tortoise SVN (I couldn’t from Unreal Engine, it was written “Couldn’t checkin…”)
Now I want to check in the assets I edit, so I select a blueprint, I click “Check Out” but it writes me “Couldn’t check out this asset”.
How can I fix that?
Also I’m new to SVN and Unreal Engine, do you think I should better use Unreal Engine source control system or Tortoise SVN? It looks easier to me to use Tortoise, I just right click then commit or update. What is better in UE source control system?
I have the same issue. When you check the Source control log is this what it says:
Error svn: warning: W165001: Lock blocked by pre-lock hook (exit code 1) with output:
Error Usage: svnHookDude SCRIPT-MODE [ARGS...]
Error Run the Subversion repository hook processing activities for
Error SCRIPT-MODE (which is the name of a Subversion hook: "start-commit",
Error "pre-revprop-change", "post-commit", etc.). ARGS is the set of
Error arguments that would be passed to the relevant Subversion hook.
Error Supported script modes:
Error ERROR: Not enough hook arguments
If so, my workaround is as follows:
- Using TortoiseSVN use the “Get Lock” command on the asset you want to Check Out. Make sure you enter a description as to why you are locking, as this is what is causing the issue.
- Refresh the asset in the UE4 Editor it will say you have Checked Out the asset. You can Check In from the Editor without issue.
I am not sure if this is a bug with the server I am using (Cloudforge hosting) or UE4 Editor, but a simple way to fix it would be to allow us the ability to add a description as to why we are Checking Out when we try a Check Out from the UE4 Editor.
Thank you for your report. We have assigned this issue to a member of our support staff, and they will begin investigation as soon as possible. If we are unable to reproduce the issue, or we need additional information, our staff member will comment here with additional questions. Otherwise, we will post an ‘Answer’ once we have logged the issue in our bug database or we have a solution for it.
In the meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide.
I have been assigned to assist you with your SVN report. Please let us know if the solution jaragoondoo provided works for you or if you are still experiencing this potential bug. Thank you!
Actually I had a little problem with my dedicated server and I moved my SVN to Cloudforge and followed a tutorial on the wiki.
I can’t check if the solution jaragoondoo provided works yet, I’ll probably get my server in a few weeks.
I will still validate his answer for future readers, if his solution worked for him it may works for others.
any news on that? Is this still broken?
This error is from last year. With the number of changes that have occurred since this date, it is highly likely that errors that are seen are not related to this specific bug. If you are experiencing a P4/SVN error, please open a new bug report thread with what is occurring along with what steps we can take to reproduce the error on our end. I am closing this thread as outdated.