I have already posted something like this in the forum, I think?
But I still don’t understand it, sorry.
I’ve never had any problem with 4.7.6. But 4,8.X and 4.9.X and the preview of 4.10 are just not running well.
I have no idea why. It only slows down then I play it the level. I can somewhat play it on Low but Medium and up just makes it slow down to a crawl.
I am using a laptop. I have tried making it use Nvidia instead of Intel (Integrated). I have tried r.GraphicsAdapter=0 (the same). But it’s still slowing down.
I have an okay laptop. 3.1GHz (8 CPUs) and 12GB RAM.
Like I said, 4.7 runs just fine. Tested with the same scene, etc. What is the cause of the slowdown? It’s only when I play it. (Simulate, Play In Editor, Launch)
Okay, so I haven’t posted it anywhere else. I posted it as a comment in one of my other questions.
"Ah, no, I actually made the scene in 4.7.6 and converted it to 4.8.0 but then I had this weird overly blown color and this horrible, horrible slowdown whenever I would “Play” the project. So, I, then, decided to remake the project in 4.8.0 from the scratch it worked. Well, actually, I was able to copy the objects in the scene directly from 4.7.6 to 4.8.1, as in “Copy/Paste” as long as the objects had the same name it would work. The game goes for the lights and such. You can’t do it the other way around due to some of properties have been modified, I guess? Anyhow, I have now redone it, again and I am back to the more stable and faster 4.7.6.
However, if anyone has a solution, feel free to post it here.
And thank you very much or you comments and help."
Try debugging it using the built-in debugging tools.
I had a similar problem once with creating UMG widgets every frame after about 5 minutes it would get down to about 1FPS until i stopped “playing”
i had to use the debugging tool to find out what was causing the slowdown and traced it to my blueprints.
I found this in the output log: “LogActor:Warning: GameSession /Game/Maps/UEDPIE_0_HeadTest3.HeadTest3:PersistentLevel.GameSession_4 has natively added scene component(s), but none of them were set as the actor’s RootComponent - picking one arbitrarily”. I will keep looking.
Okay, I did some tests. It seems that if the scene is empty and I click “Play”, it will run fine. But if I place a cube something, it will slow down. I really have no idea what is causing this.
Yeah, it’s a standard cube and standard materials.
If it’s blank (completely black) then it runs fine…? I actually don’t know, since everything is black. But it just feels like it’s not slowing down. In fact, no, I can feel it. When it slows down, it’s slowing down overall.
and the standard templates like the FPS template?
then try copy and pasting a few hundred cubes or similar, if its still snappy, it might be something you added at some point?
Hmm, it doesn’t play well from the get-go. But…it’s like it’s, uh, “collecting”/“building” up something, uh…that eats away at the memory. Because if I let it “Play” for a while and “Stop” it, it doesn’t go back to normal.
In other words:
100% = Before pressing “Start”
10% - 1% = (perfomence decreases after a short while) After pressing “Start”
90% - 15% = (depending on when I stop it) Stopping it.
I am not a techy guy, at all, so I don’t know if it makes sense.
