Godot

5913 readers

1 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Other Communities

Rules

Posts need to be in english
Posts with explicit content must be tagged with nsfw
We do not condone harassment inside the community as well as trolling or equivalent behaviour
Do not post illegal materials or post things encouraging actions such as pirating games

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

[email protected]

Credits

The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
The banner is from Godot Design

founded 1 year ago

MODERATORS

Ategon

snowe

Feyter

Await Question (self.godot)

submitted 10 months ago* (last edited 10 months ago) by plixel to c/godot

6 comments fedilink hide all child comments

I'm curious what happens if you use await for a signal, but the signal is never received? Does this cause some kind of hangup?

For example if I have a function structured like so:

func foo():
    do something
    await signal.finished
    do something else

And the "finished" signal never comes, does the await call just hang indefinitely?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 10 months ago (1 children)

Just tried this out in one of my projects, here's what happened:

do something works without a problem.
do something else never goes off.
the rest of the game keeps running as normal. You can even call foo() again any number of times and do something will still go off.

Having it waiting in the background didn't seem to have much of a performance impact. I started 5000+ of them and foo() only took up ~0.6% frametime with the rest of my game running alongside it.

[–] plixel 4 points 10 months ago

Thanks so much for testing that out! That's very informative and even more thorough than what I was looking for! I wasn't at my computer when I posted this so I couldn't test it myself.

I ended up connecting the signal to a secondary function to run on finished to avoid any potential memory errors, but it's super helpful to know that the performance impact is minimal.

Godot

Links

Other Communities

Rules

Wormhole

Credits