After the recent Update, no longer I can click on the Layers! Error message!

GDevelop general Bugs reports
1

Unique Error ID for debugging: 7a08f740-ec24-41fe-a65d-25b4b4447f10

2026-07-28_14-38
2026-07-28_14-38501Ă—602 40.4 KB

Unique Error ID for debugging: 7a08f740-ec24-41fe-a65d-25b4b4447f10
TypeError: Cannot read properties of undefined (reading '3d-effects') at file:///C:/Users/Lubo/AppData/Local/Programs/GDevelop/resources/app.asar/www/static/js/710.123d5cec.chunk.js:1:1994320 at MT (file:///C:/Users/Lubo/AppData/Local/Programs/GDevelop/resources/app.asar/www/static/js/710.123d5cec.chunk.js:1:2000003) at Ea (file:///C:/Users/Lubo/AppData/Local/Programs/GDevelop/resource...
at MT (file:///C:/Users/Lubo/AppData/Local/Programs/GDevelop/resources/app.asar/www/static/js/710.123d5cec.chunk.js:1:1998946) at div at l (file:///C:/Users/Lubo/AppData/Local/Programs/GDevelop/resources/app.asar/www/static/js/710.123d5cec.chunk.js:1:3808385) at div at file:///C...

I am trying to simply click on the Base Layer. Doesn’t matter if it’s old scene or completely new and empty.

Can I reverse the Update? :grimacing: I am working on this for weeks.

2

Me too. I have gone back to vers 5.6.274 because I can’t do any work otherwise. It seems to happen with objects that have variables for me. If I click a sprite without variables it is fine. How did this slip through the net?! It’s a fundamental thing.

3

Same here on Windows 11 Pro and latest version of GDevelop 5.6.275.
Everything was working fine on GDevelop 5.6.274.

4

I’ve been told a hotfix is incoming.

Edit: they’re going to toggle the makeItWork variable to True :grinning_face_with_smiling_eyes:

5

I am usually against automatic updates, but this feature was written as Recommended… I will try to uninstall that and install the older version now. Release 5.6.274 · 4ian/GDevelop · GitHub

6

5.6.274 works fine, but a hotfix for 5.6.275 should be coming soon, I’ve been told. I will turn off auto-update though, as I can’t afford to not be able to do any work if something like this happens.

7

Hello, sorry about that issue, this should be fixed in just released 5.6.276

8

Same error here, 5.6.275, Windows 11. I triggered the error when editing instance variables in an external layout from the properties panel.