[RMA Foliage Tools] offers a collection of powerful foliage management tools.
Release Notes
V:4.4.0 New - 5.4 version support.
V:4.x.0 New - Task Progress Bar. New - Foliage To Actor Converter. New - Actor To Foliage Converter. New - Foliage To ISM Converter. New - ISM To Foliage Converter. Improvement - Performance. Improvement - Buffer File Is Now Saved In Json Format. Improvement - Interface Has Been Completely Reworked. Improvement - Codes Have Been Completely Refactored.
Hi! I’ve been using this plugin for a long time and it’s great and it does it’s job very well!
Recently, I started using World composition to optimize my open world map. UE4 allows landscape parts to be moved to other maps. However, while doing this, it does not move the plants. My opinion is this. A feature that allows us to choose foliage as the grid, taking into account the position of the landscape.
In this way, I can safely select the plants and move them to the other map. Would you consider adding such a feature? Have a nice day!
I’ve been using the RMAFoliageTools utility for some time, and I’ve run into a bug where the 2.8.5 version of the plugin fails to open buffer text files exported in an older version of the plugin (anything pre-2.8.0/UE4). Looking at the buffer files themselves, it looks like there’s some superficial formatting differences (changing the “Transforms” tag to “Transform” for instance, etc) but even after adjusting those to fit the new format, I still can’t get them to open in 2.8.5. Is this a known bug? Are there any workarounds that anyone else has found?
We are having the same issue. We want migrate foliage from a 4.27 project to a 5.1 project. The buffers we wrote out for 4.27 do nothing in RMA Foliage for 5.1.
A side issue with 5.1 is we would like to use RMA to move foliage from sub-levels to the World Partition level, but when we do, the foliage lands in the wrong place, around 0,0 rather than out where it should be.
Hi,
Thanks for reporting, about the first bug it has been fixed in version 2.9.1 which will be available in the coming days. About the second bug, please contact me by email to provide me more information.
Thanks.
I tried to use FoliageTools v2.9.1 to move a lot of foliage (700,000 trees) from a regular 5.1 level to a world partition level. Instead of making one big instanced foliage actor, it made 20,000… Is there something I’m missing? Is there a way I can merge the foliage actors or have FoliageTools generate fewer actors?
In the regular 5.1 level, the single massive foliage actor performs very well. I have tried to convert it to WP but when I run the convert tool, the foliage actor does not come through.
Hi! I’ve been using this plugin for a long time and it’s great and it does it’s job very well!
But we ran into a problem, after we converted the foliage to the actor, and then converted the actor to the foliage, the relationship between the foliage and the landscape disappeared, and I had no way to repair the relationship between the foliage and the landscape, would you consider adding such a feature?
