I've implemented a #ProtoFlux JIT compiler which dynamically generates ProtoFlux node classes to wrap #WebAssembly export functions. I had a Java moment and made the compiler very object-oriented, which let me abstract it so much that it can be used both for Action and Funciton nodes and for things other than WebAssembly.

This is really exciting for me because I've never messed much with #CSharp or IL and I'm happy that this part of the project is done, because debugging dynamically generated code can be a nightmare.

Next up is gonna be some more focus stability. For example, when a module is unloaded and loaded again, the ProtoFlux nodes wouldn't update.

Update on my #WebAssembly #Resonite plugin. I can instantiate modules now and inspect their function exports. It's also possible to modify the function signature because an "externref" maps to "object" by default, which is not very neat.

The next step will be implementing the actual #ProtoFlux node for calling such a function. It will need a Global of the function export. It will be an interesting challenge to implement though, because of the arbitrary amount of inputs and outputs it can have. But I got some ideas to try out.

I'm now very invested in making a Plugin (not a mod) for #Resonite which adds experimental #WebAssembly support to #ProtoFlux scripting. I'm also thinking of other use cases like custom audio effects and procedural assets implemented through WASM.

But before I can do that, I noticed that the tools for building ProtoFlux Plugins for Resonite need some improvement. Gonna do that first.

I tried to make a boop animation for my avatar without annoying anyone, and somehow... I think I succeeded.
I don't think animators are a thing in Resonite, so I came up with this. If they actually are... oops.

(Explanation in the alt text)

#VR #Resonite #Protoflux