Re: WebAssembly
Hi Vladimir,
This has been low-priority so far, so no progress in this area. Happy to know you are interested in working on this. Please, let me know if you need anything, I assume you are going to use the Managed Wasm library included in our Unity package right? (because the native C++ one is not compatible with C#)
This has been low-priority so far, so no progress in this area. Happy to know you are interested in working on this. Please, let me know if you need anything, I assume you are going to use the Managed Wasm library included in our Unity package right? (because the native C++ one is not compatible with C#)
-
- ai_enabled
- Posts: 230
- Joined:
- Contact:
Re: WebAssembly
Hi Jesús,
Yes, I've started by investigating it first. And I certainly need your help as the Managed WASM library (specifically the Noesis.bc bytecode) has some Unity bindings.
I will send you an email soon providing the details.
Regards!
Yes, I've started by investigating it first. And I certainly need your help as the Managed WASM library (specifically the Noesis.bc bytecode) has some Unity bindings.
I will send you an email soon providing the details.
Regards!
AtomicTorch Studio Pte. Ltd. http://atomictorch.com
-
- ai_enabled
- Posts: 230
- Joined:
- Contact:
Re: WebAssembly
FYI, together with @jsantos we've worked on this integration but came across this issue with .NET 7 WASM https://github.com/dotnet/runtime/issues/92380 — unfortunately it prevents us from using NoesisGUI C# SDK (there are dozens of callback methods which expect string parameters).
I would appreciate it if anyone could help raise awareness about this issue as two weeks have passed but there is still no feedback. Previously they've fixed a similar issue (with blittable structures). Either way even if the work starts immediately getting the fix in the release version of .NET will probably take several weeks at least...
There is another issue with "null function or function signature mismatch" in Extend_FreeString call but I don't think we can debug it further until the first issue is resolved.
TL/DR: no luck with .NET 7 WASM support.
Regards!
I would appreciate it if anyone could help raise awareness about this issue as two weeks have passed but there is still no feedback. Previously they've fixed a similar issue (with blittable structures). Either way even if the work starts immediately getting the fix in the release version of .NET will probably take several weeks at least...
There is another issue with "null function or function signature mismatch" in Extend_FreeString call but I don't think we can debug it further until the first issue is resolved.
TL/DR: no luck with .NET 7 WASM support.
Regards!
AtomicTorch Studio Pte. Ltd. http://atomictorch.com
Who is online
Users browsing this forum: No registered users and 0 guests