Uploaded June 2025 | Updated September 2026, 1 week ago
These are the first bits of the splittening, laying out the skeleton of how the mechanism is going to work and interop with the new system.
As of right now, FrooxEngine has been completely removed from Unity, instead the Unity side has a new library called "Renderite" (with small portion of it shared between FrooxEngine). This facilitates the core of the communication between the two - messaging system.
You can see the initial engine initialization (this is just simulated one right now for testing purposes), followed by actual update loop - it doesn't really do anything yet, other than Unity sending message "I'm ready to do a frame" and then the system responding "The frame is ready" and providing it with data for that frame, which is blank as of right now.
Making it actually send some data for the scene to update and for assets to be loaded and so on are the next steps, I needed to verify that the initial communication bits work properly and the two sides can talk to each other in the first place.
You can also see me manually put the communication port in the editor - in "normal" use the system will launch the renderer process and tell it where to connect to for messages, but for testing purposes it's just manual, so I can better watch what's going on.
Support development at: patreon.com/resonite
Official website: resonite.com
These are the first bits of the splittening, laying out the skeleton of how the mechanism is going to work and interop with the new system.
As of right now, FrooxEngine has been completely removed from Unity, instead the Unity side has a new library called "Renderite" (with small portion of it shared between FrooxEngine). This facilitates the core of the communication between the two - messaging system.
You can see the initial engine initialization (this is just simulated one right now for testing purposes), followed by actual update loop - it doesn't really do anything yet, other than Unity sending message "I'm ready to do a frame" and then the system responding "The frame is ready" and providing it with data for that frame, which is blank as of right now.
Making it actually send some data for the scene to update and for assets to be loaded and so on are the next steps, I needed to verify that the initial communication bits work properly and the two sides can talk to each other in the first place.
You can also see me manually put the communication port in the editor - in "normal" use the system will launch the renderer process and tell it where to connect to for messages, but for testing purposes it's just manual, so I can better watch what's going on.
Support development at: patreon.com/resonite
Official website: resonite.com
