Using Tortoise SVN causes the engine's source control to be inconsistent

If a user decides to use Tortoise SVN, the error messages given for needing to have things checked out is inconsistent.

If there is a blueprint which references another blueprint, and the referenced blueprint has multiple children, compiling the referenced blueprint while the others are not checked out will give errors that the referencing blueprint and all children need to be checked out. If the user hits compile again, it'll simply repeat that the referencing blueprint needs to be checked out multiple times but never mention the children. If the user goes to select 'Check Out Modified Files' after this, it is grayed out which shouldn't be the case.

This issue also occurs with Perforce instead of Tortoise SVN in 4.8.1 (CL#2591939) but does not occur on 4.9 Main (CL#2604445)

1. Download Tortoise SVN ([Link Removed])
2. Follow the following tutorial to set up TortoiseSVN ([Link Removed])
3. With your newly created project from the tutorial, set up source control under Subversion by providing the repository directory and a username
4. create a 2 new blueprints of the actor class (Named BP1 and BP2)
5. Create a few child blueprints of BP2 (About 10)
6. In BP1, on BeginPlay, make a Spawn Actor By Class node and set it to spawn BP2
7. If any of the blueprints aren't checked out at this point, check them out and then save them all and check them back in.
8. Check out BP2
9. Open BP2 in the blueprint editor and attempt to compile it
10. Notice that you are told that multiple files need to be checked out
11. Go back to the main editor and under source control, attempt to select 'Check Out Modified Files'
Result: Check out modified files is grayed out
Expected: Check out modified files should be usable to check out anything needed to compile BP2 or these files should not be needed to be checked out.

Source Control submit freeze