If I am moving the character and press ESC during play in editor whilst moving, it’s crashing the engine.
It’s only happening on my level that I created from “blank level”, I have a test level that is an open world and it doesn’t do it there.
I believe it is something to do with the Dynamic Material Array I create in BP, if I disconnect this from Tick, the crash doesn’t occur.
I’ve created a parallax background for a 2d side scroller, I have a 2d paper sprite static background (attached to the SpringArm) and 2x paper sprites attached to the background.
I ran a print string through both BeginPlay and Tick and the Array is never empty, always contains 2 as expected, the game doesn’t crash at runtime, only when I hit ESC whilst the character is still moving. And again, only when I’m in “blank” levels (I did create a new blank level to check and it crashed on that one too, but never on the “open world” level)
n.b. I did open the array whilst the game was running and went to the dynamic materials that were created and I did notice both of their Index was -1? It does show the same on the level that it doesn’t crash on, but I wondered if that was part of the issue?
It’s really hard to tell with the given informations. Though I’m sure you’re also struggling to find clues too! Like what else can you say right? To me, this seems like a clear sign of an error with your blueprint code, and I believe some aspects of your game won’t work as intended in your packaged version. If I’m right about that, we could detect which parts of your code are faulty by seeing what things don’t function in your packaged game. So could you try packaging your game and continuing your investigation from there?
Great idea! So I packaged it and everything seems to work fine I’ve implemented a PauseMenu when you press ESC, and there’s no crash when pressing it or going to Main Menu or quitting the programme I’m lost
You see the problem’s not about the ESC button. And I didn’t actually expect crashes either. But didn’t you notice anything off with the parallax you mentioned? Or any other thing? If not, the issue might not be about your code at all
If it’s not about the code, it could be about hardware. You see, it’s not a well documented thing, and this was actually one of my first posts but I also experienced some issues while trying to exit the test editor. And we couldn’t identify the issue even after countless online chats with various big companies’s support agents. The topic might go to a totally different direction but lemme tell you about my findings just in case. So one ASUS agent told me that since the editor uses RAM but the test editor uses VRAM, there could be a fluctuation between them. In my case, that just resulted in the edges of the screen flashing and flickering. But maybe, I don’t know how that’s relevant but maybe it also has something to do in your case as well. What was the specs of your hardware?
Oh I see! Nope nothing seemed off, it worked as expected
Here’s my PC specs, they’re pretty good AFAIK, I did just update my graphics driver so need to test that again, I’ll also run it with the Task Manager open to see if there’s any spikes there
What about the GPU and VRAM? Also, 16GB can in fact be pretty limiting even if your game is 2D. Unreal’s a very demanding program and unless your project is really tiny, that low of RAM might cause momentary freezes, lags and even crashes sometimes! Think about this, when I have a browser, VS and Unreal all open at the same time, they consume 32GB already!(Windows stretches it’s legs depending on RAM capacity, but still!) So when you’re talking about crashes, that’s definitely something we should consider to be the culprit.
I really hope it’s not about hardware though, that really sucks because… there’s nothing you can do about that. Anyways, could you also provide your RAM and VRAM specs? Like capacity, speed, latency etc.
I’d be surprised if it’s a RAM issue, considering how specifically the crash occurs? But it’s worth looking at for sure! I’m hardly an expert plus it really is a very small project, I haven’t really even got a level yet
Though your GPU seems pretty capable. And considering the project has been barely started, and also how specific the situation is for the issue occur, RAM also seems irrelevant actually. The only thing comes to my mind would be that fluctuation thing but why would it not happen when you exit while not running. Yeah back to code I guess But it’s really hard to say anything else with these limited informations. I mean… especially if @ClockworkOcean is silent I think there’s more debugging to do on your part
Honestly, I get all the weird stuff
But that was my thinking too, it must be coded related, I noticed the Blank levels don’t generate a HLOD map instance, wasn’t sure if that had something to do with it? And if the character is stood still and I exit the PIE, no crash! Honestly it’s beyond me
To me, this seems like a clear sign of an error with your blueprint code, and I believe some aspects of your game won’t work as intended in your packaged version. If I’m right about that, we could detect which parts of your code are faulty by seeing what things don’t function in your packaged game. So could you try packaging your game and continuing your investigation from there?
but I also experienced some issues while trying to exit the test editor. And we couldn’t identify the issue even after countless online chats with various big companies’s support agents. The topic might go to a totally different direction but lemme tell you about my findings just in case. So one ASUS agent told me that since the editor uses RAM but the test editor uses VRAM, there could be a fluctuation between them. In my case, that just resulted in the edges of the screen flashing and flickering. But maybe, I don’t know how that’s relevant but maybe it also has something to do in your case as well. What was the specs of your hardware?
