Godot

5842 readers

22 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

[email protected]

Await Question (programming.dev)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]

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?

all 7 comments

sorted by: hot top controversial new old

[–] [email protected] 14 points 9 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.

[–] [email protected] 4 points 9 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.

[–] [email protected] 2 points 9 months ago (1 children)

On their own, there's usually no timeout condition for async functions like this. The task (I don't know what they're called in gdscript, I use c#) will just hang until it completes, errors, or is canceled.

There are cases when you can run into timeouts, such as sending web requests. There are also use cases for making your own timeout trigger. In both of these cases, the timeout is because of what made the task, not something inherent in tasks.

[–] [email protected] 1 points 9 months ago

Thanks for the explanation! Your explanation led me down a rabbit hole of seeing if there's a way to cancel an await call, from what I can tell there was no clear way to do so. In my case I ended up connecting the signal to a secondary function instead of utilizing the await command, I'm not entirely sure if there's an advantage to utilizing one method over the other.