If you’re working with large environment modular pieces, you often want to use a large grid snap setting (500, 1000, etc)…however, using play-from-here with this can cause the player to spawn…not where the mouse clicked.
I can’t tell for sure, but the player might be spawning with the grid-snap restriction which can (but not always will) cause the player to spawn inside collision or otherwise fail to spawn correctly, which seems to trigger the spawning of a default controller at 0,0,0 instead.
The easiest way to test this is to use a new FPS-with-blueprints project, since that default map exhibits the problem with the 500/1000 spacing snaps. This is in 4.6, btw.
It’s easy enough to work around this by toggling snapping on/off when using play-from-here, but I figured you guys might like to know. Also, since I haven’t seen any posts about this before, so others might appreciate the google-result if they run into the same problem…it sure confused the heck out of me for a few minutes.