From b9ca08304f93f2fb02c41843d5d41fa2a5fa8730 Mon Sep 17 00:00:00 2001 From: Mikael Hermansson Date: Wed, 17 Sep 2025 14:22:34 +0200 Subject: [PATCH 1/2] Mention importance of thread-safety in `Logger` example --- tutorials/scripting/logging.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tutorials/scripting/logging.rst b/tutorials/scripting/logging.rst index ee6a1ecd3..a51cdbaee 100644 --- a/tutorials/scripting/logging.rst +++ b/tutorials/scripting/logging.rst @@ -225,6 +225,8 @@ Here is a minimal working example of a custom logger, with the script added as a func _log_message(message: String, error: bool) -> void: # Do something with `message`. # `error` is `true` for messages printed to the standard error stream (stderr) with `print_error()`. + # Note that this method will be called from threads other than the main thread, possibly at the same + # time, so you will need to have some kind of thread-safety as part of it, like a Mutex. pass func _log_error( @@ -239,6 +241,8 @@ Here is a minimal working example of a custom logger, with the script added as a ) -> void: # Do something with the error. The error text is in `rationale`. # See the Logger class reference for details on other parameters. + # Note that this method will be called from threads other than the main thread, possibly at the same + # time, so you will need to have some kind of thread-safety as part of it, like a Mutex. pass # Use `_init()` to initialize the logger as early as possible, which ensures that messages From a0501c87382eb4afc82331f0e6db9e3f2409c1b4 Mon Sep 17 00:00:00 2001 From: Hugo Locurcio Date: Sat, 27 Sep 2025 00:54:59 +0200 Subject: [PATCH 2/2] Document exporting/compiling for the iOS simulator not currently being supported Once the issue is resolved, it could support Compatibility but not Forward+/Mobile due to these renderers requiring a feature the iOS simulator doesn't support (image cube arrays). --- .../development/compiling/compiling_for_ios.rst | 8 ++++++++ tutorials/export/exporting_for_ios.rst | 9 +++++++++ 2 files changed, 17 insertions(+) diff --git a/engine_details/development/compiling/compiling_for_ios.rst b/engine_details/development/compiling/compiling_for_ios.rst index 1ad0d877f..72c64270d 100644 --- a/engine_details/development/compiling/compiling_for_ios.rst +++ b/engine_details/development/compiling/compiling_for_ios.rst @@ -74,6 +74,14 @@ The MoltenVK static ``.xcframework`` folder must also be placed in the ``ios_xcode`` folder once it has been created. MoltenVK is always statically linked on iOS; there is no dynamic linking option available, unlike macOS. +.. warning:: + + Compiling for the iOS simulator is currently not supported as per + `GH-102149 `__. + + Apple Silicon Macs can run iOS apps natively, so you can run exported iOS projects + directly on an Apple Silicon Mac without needing the iOS simulator. + Run --- diff --git a/tutorials/export/exporting_for_ios.rst b/tutorials/export/exporting_for_ios.rst index 45fbbaca8..604e454a6 100644 --- a/tutorials/export/exporting_for_ios.rst +++ b/tutorials/export/exporting_for_ios.rst @@ -57,6 +57,15 @@ When the export completes, the output folder should look like this: .. image:: img/ios_export_output.webp + +.. warning:: + + Exporting for the iOS simulator is currently not supported as per + `GH-102149 `__. + + Apple Silicon Macs can run iOS apps natively, so you can run exported iOS projects + directly on an Apple Silicon Mac without needing the iOS simulator. + Opening **exported_xcode_project_name.xcodeproj** lets you build and deploy like any other iOS app.