Description

In the world settings of any level, changing the max undilated frame time to a negative number results in the editor crashing.

Steps to Reproduce
  1. Open a level
  2. In the world settings change max undilated frame time to a negative value (set to -1 in test)

Result: Editor crashes

Expected: Prevent negative values from being entered

Callstack

LoginId:2425c04a4245ea67c3691fbe9144aff0
EpicAccountId:6b50d04f360f4c7587a1171ba17d6a2a

Assertion failed: GameDeltaSeconds >= 0.0f [Link Removed] [Line: 1340]

UE4Editor_Core!FDebug::AssertFailed() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\core\private\misc\assertionmacros.cpp:419]
UE4Editor_Engine!UWorld::Tick() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\engine\private\leveltick.cpp:1343]
UE4Editor_UnrealEd!UEditorEngine::Tick() [d:\build\++ue4+release-4.19+compile\sync\engine\source\editor\unrealed\private\editorengine.cpp:1482]
UE4Editor_UnrealEd!UUnrealEdEngine::Tick() [d:\build\++ue4+release-4.19+compile\sync\engine\source\editor\unrealed\private\unrealedengine.cpp:401]
UE4Editor!FEngineLoop::Tick() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\launch\private\launchengineloop.cpp:3339]
UE4Editor!GuardedMain() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\launch\private\launch.cpp:166]
UE4Editor!GuardedMainWrapper() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:134]
UE4Editor!WinMain() [d:\build\++ue4+release-4.19+compile\sync\engine\source\runtime\launch\private\windows\launchwindows.cpp:210]
UE4Editor!__scrt_common_main_seh() [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253]
kernel32
ntdll

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-57415 in the post.

2
Login to Vote

Fixed
ComponentUE - Gameplay
Affects Versions4.18.34.194.20
Target Fix4.20
Fix Commit4056665
Main Commit4058964
Release Commit4095966
CreatedApr 6, 2018
ResolvedMay 8, 2018
UpdatedMay 31, 2018
View Jira Issue