I packaged a shipping version of a game that is not use .pak archives.
I write a simple installer that do related stuff.
And here’s what I found.
Files below are empty after packaging (have zero size).
WindowsNoEditor\Engine\Config\Base.ini
WindowsNoEditor\Engine\Config\BaseEditorLayout.ini
If you run an executable with these files, all is ok. But if you remove them, the game will crash.
You can repro it on the example FpsCpp project.
My installer had a bug when it does not copy empty files. So, after installation process I was not able to run a game.
Fatal error is on the picture.
You should definitely check this behaviour.
Yes, those files can have some special meaning, but crashing when zero-sized files are absent is a strange thing.
Unfortunately, there’s very little in the way of usable crash data in the Visual Studio logs, and I have been unable to locate this as a known issue. Have you experienced this crash since you first reported it? If you like, you can PM me your Epic ID/Machine ID and I can search the crash reports for your specific crash.
As I said you can try the next thing.
Package any project you have without .PAKing files into archives.
Make sure the file WindowsNoEditor\Engine\Config\Base.ini is empty.
Delete it.
You should see a crash on project launch.
What about epic and machine ids.
I don’t think that crash information was sent to epic.
And yes, I see this crash every time I delete empty Engine\Config\Base.ini file.
Base.ini is a file that we expect to exist. It is the only .ini file that we require. We could add some text in it, but since we know it will exist, we do a couple of things based on its existence.
So, while I want to keep assuming it will be there, we can add some text into it so that it’s not anything special.