I started using godot last month and at first it was really fast to load and test my game but recently it seems to have slowed down a lot. Loading the project menu can take 10+ seconds and the editor itself can take 15 or more. My game (2D) is very small but can take about 10 seconds to load it every time which can get annoying when making small tweaks.

Has anyone else had this? Are there any fixes or suggestions?

Also my 3D editor has been doing this:

I’ve never had a problem like this, but looking at the pictures I would guess the problem is GPU related. Based on the pictures, it looks like the OpenGL window is not being cleared correctly.

If OpenGL is not fully working, that could also be contributing to the longer loading times.

What is your GPU? Have you updated your graphics drivers recently? Also, does the console that pops up when Godot is running show anything when loading the project and/or the editor?


Another thing that could be contributing to longer load times is other programs running in the background, especially programs that read/write lots of data from/to the hard drive (like Antivirus software, streaming software, recording software, etc). Perhaps something you have installed/updated recently is slowing things down?


It is hard to say for sure, but I would try updating your graphics drivers first and see if that fixes things, as to me it seems to be the most likely cause :smile:

Ok so my GPU is an NVidia GTX 680 and although I haven't updated my drivers since downloading godot, I did try updating my drivers but it turned out that the 3D window ghosting is caused by setting the default_environment.tres background mode to canvas.

I haven't found the exact cause of the slow loading times, I have been checking my system performance while godot is loading to see if my cpu/memory/disk usage are high but they've been quite low. However I think it has something to do with my Corsair K70 keyboard since it wouldn't connect when I logged in to windows today (using onscreen keyboard) and godot was back to being super fast. Once I got my keyboard connected again it was back to being slow :/ I also tried changing the polling rate on the keyboard to "BIOS" and it seemed to fix it again then tried setting it back to the default 1ms and godot was still fast. This seems very strange :(

@AfroSpartan said: Ok so my GPU is an NVidia GTX 680 and although I haven't updated my drivers since downloading godot, I did try updating my drivers but it turned out that the 3D window ghosting is caused by setting the default_environment.tres background mode to canvas.

I haven't found the exact cause of the slow loading times, I have been checking my system performance while godot is loading to see if my cpu/memory/disk usage are high but they've been quite low. However I think it has something to do with my Corsair K70 keyboard since it wouldn't connect when I logged in to windows today (using onscreen keyboard) and godot was back to being super fast. Once I got my keyboard connected again it was back to being slow :/ I also tried changing the polling rate on the keyboard to "BIOS" and it seemed to fix it again then tried setting it back to the default 1ms and godot was still fast. This seems very strange :(

That is very strange.

Maybe Godot is having problems polling input from the keyboard or something? Does the console showing anything? Regardless, it seems really strange and totally not what I would have expected. I wonder why the keyboard would be effecting things.

I did some searching, and apparently CUE can cause some lag. I'm not sure if that is what is happening in your situation, but it's the only performance related thing I could find specific to that keyboard.

As you said, it seems very strange. I'm not really sure what could be causing it, nor what to do about it.

I wonder if it might be that the CUE software and godot are perhaps running in threads on the same CPU core? Not sure that even make sense, but call it a gut feeling.

@Megalomaniak said: I wonder if it might be that the CUE software and godot are perhaps running in threads on the same CPU core? Not sure that even make sense, but call it a gut feeling.

That's not an issue, unless CUE is using 100% of the CPU somehow (which is unlikely).