Description

Timing appears to be different for the first call of tick causing the camera to appear in a different area than what it was in 4.13

This issue appears to be a regression

Steps to Reproduce
  1. Open a blank project
  2. Open the level blueprint
  3. Call Set Game Paused on tick
  4. Save
  5. Play in editor
  6. Notice that the camera appears at position 0,0,0 in the world

Expected: The camera would be in the position that it is when starting the game normally
Result: The camera appears at 0,0,0 instead of the area the camera appears without pausing the game (as was the result in 4.13)

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

0
Login to Vote

Fixed
ComponentUE - Gameplay
Affects Versions4.14
Target Fix4.15
Fix Commit3224003
Main Commit3227721
CreatedNov 30, 2016
ResolvedDec 6, 2016
UpdatedApr 27, 2018
View Jira Issue