Issue with chaching shader at the start of the game

[buzzbuzz20xx]

Godot Version

Godot 4.2.1

Question

when exporting my game to HTML5 it runs completely fine until an explosion effect is spawned on screen for the first time when killing a mob, the game freezes for an entire 2-3 seconds, an easy fix is to just spawn it at the startup of the game so that the freeze would happen at the start instead

func _ready():
	var SMOKE_SCENE = preload("res://smoke_explosion/smoke_explosion.tscn").instantiate()
	get_parent().add_child(SMOKE_SCENE)
	SMOKE_SCENE.position = Vector2(0.0, 0.0)
	print("spawned smoke")

but for some reason this isn’t working and the smoke isn’t being spawned at the start

func _ready():
	var SMOKE_SCENE = preload("res://smoke_explosion/smoke_explosion.tscn")
	var smoke = SMOKE_SCENE.instantiate()
	get_parent().add_child(smoke)
	smoke.position = Vector2(0.0, 0.0)
	print("spawned smoke")

this also didn’t work, the smoke isn’t being spawned at the start

get_tree().add_child(smoke)

tried getting the tree instead of the parent but it doesn’t help

I tried putting breakpoints in the _ready function to see if the smoke is actually being instantiated at the start and I noticed that it seems to be instantiated and put in the game before any of game graphics actually appear on screen, so it looks like it’s appearing and disappearing before we even see it, so it fixes nothing !

Any help is appreciated !!!

[TimothyAlexisVass]

You shouldn’t preload anything in the _ready() method.

Try this:

const SMOKE_SCENE = preload("res://smoke_explosion/smoke_explosion.tscn")

func _ready():
	var smoke_instance = SMOKE_SCENE.instantiate()
	smoke_instance.global_position = Vector2(0.0, 0.0)
	get_parent().add_child(smoke_instance)
	print("spawned smoke")

[TimothyAlexisVass]

You may want to use threads instead of “caching shaders”.

How do you properly explode an enemy? (Without freezing the main thread)

Here’s the core of how to use threads. This comes from a file I use as a central threaded object loader: func _ready(): m_nError = ResourceLoader.load_threaded_request(m_stPath) if m_nError != OK: print("Can't start the threaded load.") func _process(delta): if !m_bDone: m_nError = ResourceLoader.load_threaded_get_status(m_stPath) match m_nError: ResourceLoader.THREAD_LOAD_INVALID_RESOURCE: fatalError.emit(self) queue_free() ResourceLoader.THREAD_LOAD_IN_PROGRESS: …

[buzzbuzz20xx]

Thanks for the answer, I already tried this but it didn’t solve anything

I’ll look into the thing you mentioned in your other reply

[TimothyAlexisVass]

Is position (0, 0) visible when the level starts?

[buzzbuzz20xx]

Yes it is and I just double checked

[TimothyAlexisVass]

@buzzbuzz20xx

I noticed that it seems to be instantiated and put in the game before any of game graphics actually appear on screen

That would be possible.

Using SceneTree

If you have this simple scene tree:

Parent
  Child

Then this is the order:

1. Parent _enter_tree
2. Child _enter_tree
3. Child _ready
4. Parent _ready

Notice that Parent will wait for all children to run _ready before running _ready.