[Bug] Enabling Physics Sub-Stepping modifies Character spawning

Development World Creation
, , , , ,
1

Hi, I’ve noticed something pretty curious: enabling Physics Sub-stepping in Project Settings → Physics causes the characters (it’s a local multiplayer context) not to always be spawned at Player Starts as it had done before enabling that, now they sometimes are spawned in places near the PlayerStarts (there are 4 players and 4 Player Starts, and until then, in this 4.1 build, the characters where spawning each one at each player start nicely).

Could you please fix this bug?

2

As what gets modified seems to be just the X value of the characters location, I’ve done this is Begin Play: “Set Actor Location” to the same location but with X=0.

Nothing changes: after enabling Sub-stepping, at spawn time the X value of the characters’ Location sometimes is set to -64 (checked out with Alt+S or Simulate) instead of the expected 0 (it can happen to any character, sometimes happens to ones and other times to other ones, it’s a bit random).

3

OK, so I’ve solved this placing the characters at their PlayerStarts at BeginPlay with Set location.

Nevertheless, if you want (Epic) you can still check why enabling Sub-stepping caused that -64 unit change in X value. As Sub-stepping gives more realistic physics, maybe a more accurate (or simply different) treatment is done to spawning at Player Starts, which may contain an undesired line of code (or whatever) that causes that modification.

4

Thanks for bringing this up. It sounds like a bug, I’ve added it to our bug tracking system.

5

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.

If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.

Thank you.