I personally tested it on Unity 6 and everything works. There's documentation in the MegaWorld folder, in the Getting Started section

Oh thank you for such a compliment, I'm glad you thought it was perfect. It's not perfect yet, I'm thinking of creating an alternative to Mega World, I've been thinking about this for a long time, I want to create something more revolutionary in the field of procedural generation

Just write to me on the Discord server or email and I will help you. Please do not write about help in reviews, I do not receive notifications of new reviews

Thanks for the feedback. Perhaps someone may not like MegaWorld and in general the Universal Toolkit that I'm working on, I'm fine with this and I'm always happy with criticism, it helps to make my tools better. You wrote that updates are slow, I remember when you first started using MW, at that time I was completely rewriting Instant Renderer, I was not just rewriting, I was trying to make it better in every aspect. I shared the Devlog every month so that users can see the progress, I couldn't release an update because I thought it was not stable in many ways, I tried to fix bugs in the old version. I agree that it took a long time to create an update, but you can't appreciate how much work I put in every Devlog, I worked 10 hours every day. Updates are not always long for me, it depends on how long it takes to create the update itself or the tool, after the release of this major update, I released another important update a month later, then two months later I got a new Sectorize tool - Streaming Toolkit and some IR improvements. About my earnings model, I did not quite understand your claims. My model is like Blender, the software is free, there is a subscription model. I have the same thing, all my tools are free, some of the tools will be in the Asset Store, and the full version will be available on my Discord server with a license, as well as on Patreon, probably, when I write this, I already had a yearly subscription, yes I I don't want to publish all my great work in the Asset Store. You wrote that if the user uses MW, he will not be able to use the GPU Instancer, Nature Renderer. I have GameObject spawn support. It is also possible to convert IR to Unity Terrain Tree or GameObject and use other renderings. Perhaps you would like to have support for direct spawning of the Unity Terrain Tree, I can’t add it, my Brush Erase Tool worked very slowly with the Unity Terrain Tree, my algorithm for finding objects did not work so as not to spawn inside the tree, this can be was to decide, but it is difficult. Also, many of my tools could not work with the Unity Terrain Tree. I don't understand why I need to create support for direct spawning of Unity Terrain Tree when you can just convert IR to Unity Terrain Tree. About that situation in the Discord server, where you wrote to another user that he should not use MW. I think you did not write bosebid things, but rather tough ones. I had the right to answer, I generally wanted to know what kind of complaints you had about my tools. Yes, I took a screenshot of your game (the last screenshot of the terrain that I saw from you) and wrote that you have a bad terrain, yes, I wanted to say that you are not a professional to talk hard to another user about the right workflow. As I understand it, you didn’t like it very much, I remember that you wrote that now I am your enemy, I wrote you my thoughts, why did I answer you, I apologized, because apparently I hurt you a lot

Thanks for the review :)

Thanks for the review :)

More free content coming soon