IvanEfimov
commented
3 years ago Our idea to save the scheme with separated app of Player, because it is closer to the real project app. Also the editor is more stable, no sense to implement scene restoring. However, loading time and memory consumption increase. The idea is to share resources between the editor and the engine. When the Player needs a resource, it can get it from the editor.
If the user wants to test 3D content, both the editor and the player can be open which may consume lots of RAM. For example, the nature demo scene could be running inside the editor while there is another one loaded by the NeoAxis Player. On a computer with 8GB of RAM and integrated graphics, I tried to have only the player open and I loaded the nature demo but it still ate nearly all of my remaining RAM even after I set the resolution to 640x480. To possibly save plenty of RAM, the editor might need the feature to play the scene directly within the editor after clicking "Play". One way may be to launch a separate window that is part of the editor (without opening the player) and the other is to use the scene's area for testing with no isolated window. Another problem is that the big chunk of RAM is not instantly freed after I close the nature demo scene inside of the editor. In the future, I hope for NeoAxis to use less RAM so that devices with just 4GB of RAM can test the 3D content better (with or without having to run both the player and the editor simultaneously). There are the other game engines that run okay with 4GB of RAM.