Unity’s editor and asset ecosystem are incredibly powerful, but its runtime is heavy, closed, and increasingly restrictive.
I’ve been exploring a radical idea:
Running Unity projects outside the Unity runtime.
This concept is called NextLiber VRM (NLV) — a Java-based Virtual Runtime Machine that interprets Unity scenes, assets, and logic without relying on Unity’s native runtime.
Why this idea matters
- Unity runtime dependency is a long-standing bottleneck
- Licensing and platform restrictions limit long-term sustainability
- Research, education, and enterprise use cases often need more openness
- Unity assets are valuable, but the runtime is not always the best execution layer
What NLV aims to explore
- A Java-based external runtime
- Interpreting Unity scenes and assets
- Redefining the execution layer of Unity projects
- A new architecture for long-term asset liberation
Still conceptual, but the vision is clear.
GitHub
https://github.com/Akito5928/NextLiber-VRM/
Discussions
https://github.com/Akito5928/NextLiber-VRM/discussions
If this idea resonates with you, I’d love to hear your thoughts.
Top comments (1)
Really interesting concept! Running Unity projects outside the native runtime could open up a lot of possibilities for testing and lightweight deployment, especially for APKs and mobile prototypes. I can see how a Java-based runtime could help bypass licensing and platform restrictions while keeping asset usability intact.
One thing I’m curious about: how does NLV handle complex Unity physics or shader behaviors? Would love to see some real-world examples or demos if possible — this could be a game-changer for indie developers experimenting with Unity assets outside the standard runtime.