All menus up and running (including a splash screen
1 map for the main menu and world menu.
1 map for the levels menu
1 map = level0101
Basically what is happening is that I start the game by pressing the icon, you see the navigation icons flipping because my game is in landscape mode but the screen stays black.
When validating in ddms.bat (monitor.bat) I don’t get anything, no warnings or message errors. It just gets stuck on the black screen.
workflow of first map:
map loads.
save game actor in scene loads or creates save game file.
splash screen widget should appear on screen for 3 seconds.
then the main menu appears above a “mini” level (it’s just there for “decoration”!)
So why is my game only successfully starting once every two tries? What am I missing?
I can’t actually help you, but I want to make you sure that you are not the only one who has this kind of problem. I was asking the same (sub-)question in this thread. It seems that we only have to wait for 4.8.2. I currently develop in alpha testing phase on the Store and my friends with different phones have the same problems. I got 13 levels in my game and a “menu-level”. What is weird is that it doesn’t crash typically, but just blacks out and then goes back to app menu. For me it sometimes blacks out right after turning left the screen (I have landscape too), sometimes I am able to play 1st or 2nd level. And I have some render failures in the game I didn’t have before, what about you? In the main menu of my game I got a pawn that walks and jumps over some blocks. Sometimes the mesh of the pawn just doesn’t render correctly (hard to describe).
Sometimes it will go back to the “android” menu, but it’s rare and I have no info on why. I plugged my device on ddms.
What I’ve notice is that when it doesn’t work, meaning it stays on the black screen, it seems to be taking a couple of seconds more to go in landscape mode compared to when the game works. So if I had a guess, there’s something not working right just before the game goes into landscape mode.
Once the game is started, I don’t have any real problems other then going from the level menu to the actual level, once in a while maybe (20%) the game will crash. But that seems to be known issue regarding UMG eating too much memory for whatever reason. Hopefully they will get that resolved.
Huh? There’s an issue where it never releases RHI texture resources it uses in 4.6/4.7/4.8, but that shouldn’t be an issue unless you’re constantly throwing newly allocated textures at the UI, or map transitions (full map transitions can cause the textures to be reallocated), fixed in 4.9. Other than that I know of no such other issues.
In one of them, they say they will try to get in 4.8.1 and in the other issue, as of 1 day ago, still no changes. But I know you guys have a lot on your plate. But it’s crucial that we get these issues resolved in order to be able to ship our Android games
In my case it is really similar. Sometimes I have problems even to launch the game. When it’s successfully launched, then it works fine until I want to open another level (just like you). I would guess it’s about the memory too… the truth is, that I didn’t have the problem with that until I redisgned the UI. But an single image has about 70kB and on computer it works fine. I will maybe later take some screenshots or recordings from android. Any ideas how to fix the memory problems caused by graphics and textures?
This may be an issue recently fixed for 4.8.2 with threaded file loading; it sometimes would load from the wrong location in the file due to timing of the reads and seeks. This was causing a number of random issue (texture corruptions, out of memory from allocating too much space, decompression errors, etc). If you are working with GitHub, you can grab this patch for now, or wait for 4.8.2 which should be out soon:
I had this issue - in my logs it was something bout one of my sound cues being corrupted on a map load - but it ran fine all the time. I manually implemented the 4.8.2 changes from github and stability has gone way up
I wanted to point out that the second post said that the fix will almost certainly not make it into 4.8.1, and in fact didn’t But it is on the approved list for 4.8.2 and should be included. Again there’s never any absolute guarantees, but as of right this second it’s set to be included.
But it is on the approved list for 4.8.2 and should be included. Again there’s never any absolute guarantees, but as of right this second it’s set to be included.