unitywebrequest
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
unitywebrequest [2021/05/24 19:17] – 151.204.147.19 | unitywebrequest [2025/01/15 04:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== UnityWebRequest ====== | ====== UnityWebRequest ====== | ||
+ | |||
+ | ==== Local Filesystem Requests ==== | ||
When using UnityWebRequest to load from the local filesystem: | When using UnityWebRequest to load from the local filesystem: | ||
- | | + | |
- | * Windows and Android | + | |
+ | * Android | ||
+ | * Windows does not require | ||
+ | |||
+ | ==== Sending requests during destruction ==== | ||
+ | |||
+ | To ensure that UnityWebRequest operations are completed even if the MonoBehaviour is being destroyed (e.g. when the game is exiting), it appears to be safe on at least some platforms (such as Windows) to manually wait in a loop inside '' | ||
+ | |||
+ | * Note however that mobile platforms don't provide destruction callbacks at all and will usually simply kill the process. | ||
+ | * It is recommended to limit the maximum running time of such a loop, and an appropriate time measurement method like '' |
unitywebrequest.1621883843.txt.gz · Last modified: 2025/01/15 04:35 (external edit)