I was looking at the Debug Console today for a well known freeware airliner and I noticed these error messages.
Does anyone know what these might refer to? They come right before recompilation of wasm modules (but also sometimes after them).
@FlyingRaccoon @Boris any ideas on what might be causing those?
Thank you!
Hello again,
sorry - I don’t want to sound like a pest, but I am trying to narrow down a bug that causes something to crash and this error is something I’ve not seen elsewhere. Can someone please reply on what would cause it?
Thank you!
@EPellissier @FlyingRaccoon do you guys have any clue on what causes this error message?
Thank you
Hello @simfan
What crash are you referring to? A WASM module crash?
WASM gauges are rendering into CoherentGT canvas and “WasmGaugeLiveView_XX” is the name they are declared with for Coherent.
I have not been able to have this message displayed so far.
Is this something you see only with your own module or with any module?
This occurs when you use the “recompile” function from the “Wasm Debug” window?
Regards,
Sylvain
Hello @FlyingRaccoon - thanks for picking this up - it surely is weird!
If you install the FlyByWire A320 Neo (freeware) you will see this in the Debug Console as soon as you have it loaded:
1 Like
Hello @simfan
I see nothing critical so far.
Trying to load a file using the VFS path is a fallback method when the original resource was not found.
In this case, WasmGaugeLiveView_XX are the textures the wasm gauges are rendering into (we also declare a dummy one for the gauges with texture parameter set to NO_TEXTURE).
These errors show up because the Coherent context tries to access this texture before it’s ready but I don’t think it has any consequences on the gauge behavior once everything is loaded, especially since the gauges triggering this message are the ones with a NO_TEXTURE target.
I’ll log a bug so we can review if we want to make additional checks and get rid of this error to avoid any confusion.
Regards,
Sylvain
2 Likes