NAP Framework version 0.4 is now open source
I’m proud to announce that NAP 0.4.0 is officially released and available for download. Next to a host of new features, including a complete new Vulkan 3D render engine, NAP is now officially open source. This means NAP is free to use for both commercial and non-commercial projects, no license required! The pre-compiled binaries and source code are already available on our website and github. 2020 was a rough year and we (at Naivi) wanted to end it on a positive note. I am a big believer in sharing knowledge and ideas, especially in times like these where greed, misinformation and ignorance seems to prevail, instead of logic, trust and yes ‘love’. In that light we decided to open source our technology and give it away for free. It is our hope that you will put it to good use, to create new works of art and beauty, something the world desperately needs right now.
Now that’s out of the way let me share some of the highlights of this release. We completely replaced OpenGL with Vulkan. The performance gains are substantial, the control amazing, the underlying complexity mind boggling. Luckily the (render) interface barely changed so you should be up and running in no-time. It’s also a great place to learn Vulkan. One of our contributors (Tim Groeneboom) created a brand new real-time sequencer, which is already a favorite of many. It allows you to create, edit, load and play-back a show in real-time, directly from the running application. Another cool new feature is the option to add a custom license to your application.
This, together with a bunch of other new features, big changes and bug fixes marks the beginning of a new chapter for us. We hope you enjoy using the open-source version of NAP as much as we love building it.
I’d like to personally thank: Bas Korsmit, Chris Heywood, Jelle van der Beek, Ritesh Varma, Tim Groeneboom, Stijn van Beek, Thijs Krooswijk, Dodo Kiss, Ewa Piotrowska, Ralph Das and Marcel Smit for their dedication, time and effort. Thank you.
See you on our github issues page.