Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi, I'm trying this latest version and with any Tween I get an error with TGMS_EasyUseDelta not set before reading it.

___________________________________________
############################################################################################
ERROR in
action number 1
of Create Event
for object Object2:
global variable name 'TGMS_EasyUseDelta' index (100193) not set before reading it.
 at gml_Script_TweenEasyScale (line 35) -        __TweenEasyScale = TweenFire(id, ease, argument_count == 8 ? argument[7] : 0, global.TGMS_EasyUseDelta, delay, duration, "image_xscale", x1, x2, "image_yscale", y1, y2);
############################################################################################
gml_Script_TweenEasyScale (line 35)
gml_Object_Object2_Create_0 (line 4) - TweenEasyScale( 0, 0, 1, 1, 0, 1*room_speed);

I will look into this. Thanks for letting me know.

(1 edit)

I think a temporary fix is to place o_SharedTweener into your game's first room. The object is *supposed* to be automatically created, but it looks like it isn't for your project.

Let me know if that helps for now. I will need to look into this some more.

Also! If you haven't already, I encourage you to clear your project's compiler cache. (CTRL+F7)

(+1)

I have found the problem!

The object has a Tween in his create code, so it appears with a popping effect.
I dragged the object in the room via the room editor and the error occurred.
Then I instanced o_SharedTweener in the room creation code and I got all different errors.
So I removed the object from the room editor and instanced it in the room creation code and all worked fine!
No need to manually create o_SharedTweener

With previous versions I always placed some objects (eg. start button, etc..) in the first room via room editor drag n drop, and the tweens in their create event always worked fine.

If this behaviour is intended, I suggest to mention it in the documentation, when it will reach final stage.

Thank you for your support!!

Oh, this makes sense! I see what is going on now.
Yeah, I will need to adjust some things or mention this in the documentation.
One option is to create an initial room which immediately goes to the next room. That should allow you to use the room editor again for the object.

Thanks for getting back to me. This information is helpful!

I have uploaded Beta 4.1 which should fix the issue you mentioned :)

It works fine!

And best wishes for a happy new year!!

Good to hear!

Happy new year :)