From c6abcbae94649e37b8ca4e00706605692d5c469e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E8=B0=A2=E5=A4=A9?= Date: Wed, 24 Jan 2024 18:25:36 +0800 Subject: [PATCH] Update thread_safe_apis.rst to mention don't call certain rendering functions on other threads (#8749) * Update thread_safe_apis.rst to mention don't call certain rendering functions on other threads --------- Co-authored-by: Max Hilbrunner Co-authored-by: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com> --- tutorials/performance/thread_safe_apis.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tutorials/performance/thread_safe_apis.rst b/tutorials/performance/thread_safe_apis.rst index 0ee4c5721..26e1abeba 100644 --- a/tutorials/performance/thread_safe_apis.rst +++ b/tutorials/performance/thread_safe_apis.rst @@ -60,6 +60,10 @@ To make rendering thread-safe, set the **Rendering > Driver > Thread Model** pro Note that the Multi-Threaded thread model has several known bugs, so it may not be usable in all scenarios. +You should avoid calling functions involving direct interaction with the GPU on other threads, such as creating new textures +or modifying and retrieving image data, these operations can lead to performance stalls because they require synchronization +with the :ref:`RenderingServer`, as data needs to be transmitted to or updated on the GPU. + GDScript arrays, dictionaries -----------------------------