When ovrt is fresh started, it does have access to the APIs, such as window.SpawnOverlay.
Example of when an overlay is opened and no errors are shown on the console:
init main
ovrt_sys.js:319 calling spawn_overlay
ovrt_sys.js:322 transform_str: {"posX":0.0,"posY":0.0,"posZ":0.0,"rotX":0.0,"rotY":0.0,"rotZ":0.0,"size":0.25,"opacity":1.0,"curvature":0.0,"framerate":60,"ecoMode":true,"lookHiding":false,"attachedDevice":0,"shouldSave":false}
ovrt_sys.js:322 called spawn_overlay. Uid: 0
ovrt_sys.js:325 event overlay_opened. Uid: 900
ovrt_sys.js:325 event interaction_state_changed. is_interacting: false
But when F6 is pressed and the custom app is reloaded, no window is opened, and the console shows:
init main
ovrt_sys.js:319 calling spawn_overlay
ovrt_sys.js:322 transform_str: {"posX":0.0,"posY":0.0,"posZ":0.0,"rotX":0.0,"rotY":0.0,"rotZ":0.0,"size":0.25,"opacity":1.0,"curvature":0.0,"framerate":60,"ecoMode":true,"lookHiding":false,"attachedDevice":0,"shouldSave":false}
ovrt_sys.js:293 Uncaught (in promise) TypeError: window.SpawnOverlay is not a function
at imports.wbg.__wbg_SpawnOverlay_cc02f3dde427def0 (ovrt_sys.js:293)
at :8000/wasm-function[106]:153
at :8000/wasm-function[111]:197
at :8000/wasm-function[78]:289
at :8000/wasm-function[232]:4
at wasm_main (ovrt_sys.js:51)
at run ((index):67)
I expect that some rewiring is needed when refreshing the custom app, since it loses the API functions.
When ovrt is fresh started, it does have access to the APIs, such as
window.SpawnOverlay.Example of when an overlay is opened and no errors are shown on the console:
But when F6 is pressed and the custom app is reloaded, no window is opened, and the console shows:
I expect that some rewiring is needed when refreshing the custom app, since it loses the API functions.