Description

Code projects in the binary version of 4.16.1 cannot be launched without the Editor in the debugger in Visual Studio. The project hits a breakpoint while launching, with the following showing in the output:

Assertion failed: HasFoundDataDirectory [File:D:\Build\++UE4+Release-4.16+Compile\Sync\Engine\Source\Runtime\Core\Private\Internationalization\ICUInternationalization.cpp] [Line: 128] 
ICU data directory was not discovered:
../../../TestDebug/Content/Internationalization
../../../Engine/Content/Internationalization
TestDebug-Win64-DebugGame.exe has triggered a breakpoint.

This breakpoint is not hit if the Engine has been built from source code, or if the project is debugged with the Editor attached (eg. DebugGame Editor).

REGRESSION:
Yes. Projects in 4.15.3 can be debugged without the Editor.

Steps to Reproduce
  1. Create a new Basic Code project.
  2. Cook content for Windows.
  3. Close the Editor.
  4. Set the Solution Configuration in Visual Studio to DebugGame.
  5. Right-click on the project in the Solution Explorer window and select Debug -> Start new instance.

RESULT:
Visual Studio hits a breakpoint when launching the project in the debugger.

EXPECTED:
The project successfully launches in the debugger.

Callstack
TestDebug-Win64-DebugGame.exe!FICUInternationalization::Initialize(void)
TestDebug-Win64-DebugGame.exe!FInternationalization::Get(void)
TestDebug-Win64-DebugGame.exe!BeginInitTextLocalization(void)
TestDebug-Win64-DebugGame.exe!FEngineLoop::AppInit(void)
TestDebug-Win64-DebugGame.exe!FEngineLoop::PreInit(wchar_t const *)
TestDebug-Win64-DebugGame.exe!GuardedMain(wchar_t const *,struct HINSTANCE__ *,struct HINSTANCE__ *,int)
TestDebug-Win64-DebugGame.exe!WinMain ()
TestDebug-Win64-DebugGame.exe!__scrt_common_main_seh() Line 264
kernel32.dll!00000000775e59cd()
ntdll.dll!000000007781a561()

Have Comments or More Details?

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

11
Login to Vote

Fixed
Fix Commit3478522
CreatedJun 6, 2017
ResolvedJun 7, 2017
UpdatedApr 27, 2018
View Jira Issue