You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Godot and game engines in general, have a known problem for lag spikes when shaders are loading (displayed) for the first time. - see godotengine/godot#61233 for example.
To reproduce, open game on new device or clear shader cache on the device, before loading any shader e.g. darkness shader when clicking enemy on darkness tab.
A possible workaround that I've seen used around, is to display all shaders at one scene and then hide it behind a loading bar. Sometimes, this is not enough so people have hidden an "automated playthrough" behind a loading scene to cover all shader compilation cases, e.g. https://www.youtube.com/watch?t=438&v=oG-H-IfXUqI
The text was updated successfully, but these errors were encountered:
Moved from Trello: https://trello.com/c/hvs2OZcF
Godot and game engines in general, have a known problem for lag spikes when shaders are loading (displayed) for the first time. - see godotengine/godot#61233 for example.
To reproduce, open game on new device or clear shader cache on the device, before loading any shader e.g. darkness shader when clicking enemy on darkness tab.
A possible workaround that I've seen used around, is to display all shaders at one scene and then hide it behind a loading bar. Sometimes, this is not enough so people have hidden an "automated playthrough" behind a loading scene to cover all shader compilation cases, e.g. https://www.youtube.com/watch?t=438&v=oG-H-IfXUqI
The text was updated successfully, but these errors were encountered: