UE5.1 Foliage have offset pivot point when selected

[glex]

Hey all,
I’ve been struggling with this issue for awhile now and can’t seem to find a solution. When the foliage gets brushed in, selecting the foliage using the Select Foliage tool doesn’t center the pivot point on the selected object. Instead the pivot point is a good distance away. Here is an example:

Does anyone know what could be going on or if this is even fixable?

[BananableOffense]

If I had to guess, that is probably the center of the hierarchal instance. The foliage tool splits meshes into grids of instanced meshes. Is the behavior the same of you get up close to the mesh?

[glex]

I was thinking that could be the case but selecting foliage objects near each other results in varying pivot points, all of which aren’t the pivot of the hierarchal instance.

[BananableOffense]

Very weird. And this is happening while you’re in the foliage editing mode?

[glex]

Yah, its definitely a weird one. Yes, this is happening in foliage editor mode.

[BananableOffense]

If the foliage actor is part of a blueprint, make sure that the static mesh origin is properly centered in the BP. Also check to make sure any WPO effects in the material are set up properly and aren’t pushing the mesh away from it’s origin.

[glex]

Thanks for your help but it looks like enabling nanite on a static mesh thats being used as a foliage object breaks the folaige selection tool:

[glex]

Looks like there are others who were having issues as well. Didn’t know it was a nanite issue so wasn’t even able to find these posts with my initial search:

Nanite Foliage - Single selection broken

Hi. I noticed an issue using Nanite assets along the Foliage tool. Clicking onto a single instance of a foliage highlights it but actually select another one, as the pivot of the object and transform editing are applied on another instance. (cf screenshot) So far the workaround is to disable Nanite from the foliage assets, as it “fixes” the selecting and pivot issue, do the instance editing as wished and re-enable Nanite. Unless there is something else to actually fix this problem? Thanks f…

Bug? Transform Tool "misplaced" when selecting foliage that has nanite enabled

Hello everyone, I encountered a weird bug with the Transform Tool today (searches on google and the UE forums didn’t yield any similar threads). I painted Nanite enabled rocks and branches with the Foliage tool - they don’t have any leaves, transparent bits or similar, so I expected no issues. They displayed properly and painting worked as usual. Eventually, I wanted to Foliage Select a single instance of one of these Nanite enabled Meshes to fine tune their placement. [220927_Foliage-Bug_01…

[BananableOffense]

Good find, good to know. I’ve yet to use Nanite on foliage.

[glex]

If anyone else is having a similar issue, I found a workaround for now. When going to edit the foliage use console command “r.Nanite 0” which will disable nanite for all objects, then use “r.Nanite 1” to enable nanite again.

[XavierAlbertStudio]

Helped a lot, thanks

[ianwburnette]

Nanite was the issue for me as well. I was trying to dynamically scale my foliage in a material, but the ObjectPosition node gives the nanite group’s position, not the individual foliage instance. It was working for other foliage, since I forgot I’d experimentally turned nanite on for this foliage type’s mesh

Here’s my shader graph, for anyone curious

In my case, I simply disabled nanite, since I wasn’t using it intentionally. If there’s a way to get this form of material-based scaling to work with nanite foliage, I don’t know what it is.

[BananableOffense]

Use the node Component Pivot Point, or take a vector (0,0,0) and transform it from instance/particle space to world space and replace he object position node with it.