Various Editor Issues Arrising In Medium-Sized Projects

The bugs described here all start to appear once your project has large events sheets and objects with hundreds of animations and variables.

  1. Accessing and interacting with the variable view (both on objects and scene/global variables) becomes very sluggish. Ordering variables lags intensely. This is more pronounced on real projects with more sub variables, event sheets and object, but I was able to reproduce it here with just a few dummy variables:
    bug var edit

  2. Adding sprites to objects with 50+ animations starts to introduce massive delays, on my real project as much as 10+ seconds every time you add something, even if these sprites are already added to the game’s resources by other animations.
    bug anim editing

  3. Accessing large event sheets does not load the whole sheet. Attempting to scroll repeatedly extends the scroll bar until the whole sheet is loaded. The only way to avoid this seems to be searching something that is at the end of the event sheet.
    bug event sheet size

  4. On large event sheets, using undo with strg+z can introduce considerable lag. More often than not this also jumps the viewer to a new scroll position, requiring you the search for the thing again that you just edited. To me that is so jarring that I now try to avoid using undo at all cost. :smiley:
    bug undo

Example project:
https://www.dropbox.com/scl/fi/9fisma1822wu8czm7yuh5/GDev-Bugs-on-large-projects-SG.zip?rlkey=f2sjxszspslei9m9x34vxx3hx&dl=0

Lenovo ThinkPad X390
8,0 GiB ram
Intel® Core™ i5-8365U CPU @ 1.60GHz × 8
Mesa Intel® UHD Graphics 620 (WHL GT2)
Ubuntu 22.04.5 LTS (64-bit Gnome 42.9)

For reference: my real projects are about as complex as something like Monster Train or Dome Keeper. I don’t think the project size, amount of events, variables, animation etc are unreasonable for these kind of medium sized games. I can see that these issues don’t affect many GDev users but I’d still love to see these things improved! Many of these issues did not exist in GDev 4 but other than that I really love the current state of the engine. Keep up the great work!

8 Likes

+1
Happened to me when creating a trivia game, where the flags (more than 150) were in one object as animations.
I thought it was my incredibly-low-end device’s fault, anyway I had to split the flags object into continents.

2 Likes

yeah, i’ve faced the same problems with editor and i also noticed that after all those updates with variables, custom objects, side panel, etc… performance of editor got worse, which made using engine pretty frustrating for me(
Compared with construct 3 (which i used recently), editor runs smoother and I didn’t came across such issues. So maybe Gdevelop team should work on performance of the editor :thinking:

2 Likes

Upvoted.

For the record, I had already reported all the issues mentioned above individually, starting from version 5.4.
The problems started showing up for me after the variable system change.

btw this is real… it definitely needs more upvotes.

2 Likes

@sleeper_service I kept posting these issues here in hope that the team actually take a step in the right direction but unfortunately so far nothing changed regarding theses issues.
.
100% Confirming each and every single issue you mentioned, In my next project where we’re talking about the size and complexity or games like Hollow knight, ori or rayman … These issues starts to be very visible to the point where it actually increases the amount of time needed to work on a project like this.
.
Gdevelop 5 was not like that, I remember the engine to be much faster, it did have these issues yes but it was much faster than this.
.
I feel like the Gdevelop team kept adding in new stuff which is very cool but they didn’t try to test or check performance degradation each time they added stuff to the engine, something is truly wrong with the current state and performance of Gdevelop.
.
I highly recommend the team to stop at least for 2 months, and start to polish the engine performance because if they keep adding in new stuff and no check on performance, things will be going in the wrong direction, I don’t need new additions if the performance can’t even make me use these updates.
.
I also think that 90% of people probably don’t have a gigantic project they’re working on, that’s why performance check from the team side seems to be a second thought I don’t really know…
.
I hope this reaches the Gdevelop team, I’m sorry but I will tag some of my friends here from the team in hope that they make this a priority in the next updates because It’s becoming urgent and very apparent that something is 100% wrong with Gdevelop, I’m doing this because I love Gdevelop 5 and I dream of it becoming better and better, the best engine I ever used on the planet, it just needs to be faster.
@4ian @Silver-Streak @davy @Bouh @Luni

5 Likes

Hi dash, if you’re interested, there’s a recent poll asking people with the scrambled events problem what operating system they’re using: Scrambled events sheet - Poll - please vote

Interestingly, sleeper_service is using Linux which is the first non Windows user I know of to have this problem.

3 Likes

Thanks for reporting this :slight_smile:
We’ll take a look, all of these are not related to a particular update (adding features to the editor is not magically making the rest slower ;)) but more the conception of the events sheet that has always been a bit brittle for large sheets (which we try to avoid by encouraging usage of behaviors/custom objects, but it’s right that it does happen to have very large events sheets anyway).

For sprites, it’s strange to see such a long time, we’ll also have a look.

5 Likes

Thank you for taking a look at it. From my limited understanding,if it helps,I would focus on checking why, after adding a certain number of animations, even just rearranging them becomes problematic. It’s as if the order is being read and updated in real time in the event sheet, causing the lag.

Anyway, these are just assumptions.

I trust that in more experienced hands the problem could be resolved.

3 Likes