I have a large project and managed to pack it for shipping. However when I try to pack it for debugging or development, it doesnt start when I doubleclick the resulting exe. The Windows taskmanager shows me that the game exe lingers in memory and goes nowhere. The window doesnt show.
When I pack for shipping all is fine
That doesn’t happen with a small new program.
So what could be the reason for this? I am desperately trying to debug the shipping, when I give the program to others to test, it crashes sometimes, so I need to get output somehow. The shipping version does not create a logfile without compiling the whole UE, which I dont want to do, and the debug version does not run. How am I supposed to fix the errors on external machines?
Just to clarify, whenever you package the game for Development or Debug, and then click the resulting {ProjectName}.exe file, you are not seeing anything pop up?
Does the game play properly in Standalone in the editor?
Could you provide the logs from the Saved->Logs folder of the Debug build after you attempt to run the .exe?
I see nothing at all, no window opens. In the taskmanager I see Client.exe (which is the name of my project) and the Client-debug-exe project. Both linger intuil I kill them and they also prevent the directory from being deleted for as long as they are not killed.
The game plays correctly in standalone mode and gives debug output on the screen which shows that it’s a debug version that’s running
As for the log file: When I ran the cllient for the first time and checked, there was no logfile, I am pretty sure of that. I ran it again later and then there was a logfile. I don’t know if that was an error on my side or if it really wasn’t crated the first time.
I include the logfile I found here link text
Unfortunately, there isn’t a lot more information in the log that would point to the cause of this crash, but it appears to be related to an issue with allocating memory.
So we’ve discovered why the build isn’t showing up, but unfortunately that doesn’t solve the issue of how to fix the crash or prevent it from occurring.
Here’s what I recommend, since the issue appears to be isolated to your project. If you are distributing the project to others for testing, and they are getting a crash, I recommend getting repro steps from them and having them perform additional testing in order to get information on what is causing the crash occur.
If there is a crash that is occurring in shipping builds, even if it’s not ideal for you, you’ll need to enable logging in the shipping build in order to gather more information. This is what I recommend doing most because it will allow you to get the information you need to work on resolving the crash.
My main problem was that logging in the shipping version did not work, that’;s why I thought about distributing development versions to the testers, but I finally got logging working in the shipping version, so this problem here isn’t so important for me anymore, although there is some problem of course that may haunt others at some point, but for now I am ok at least