Texture instances don't work on EditableMeshes

Bug Reports Engine Bugs
,
1

I am wanting to apply a Texture instance to an EditableMesh

There are numerous reasons for me wanting to use a Texture instance over trying to use an EditableImage (if that’s the argument gonna be put forward) It also classes the EditableMesh as a “MeshPart” the same as the cone mesh on the left. So there’s no reason Texture instances should not work

Expected behavior

It should render, like it would on a normal mesh

6 Likes
2

I am not able to repro. Would you mind sharing a place file?
Thanks.

3

Wait so this is a feature… I’ve DM’d a place file privately

1 Like
4

Thanks for the repro file, I was able to reproduce it with this example.
I tried removing UVs, colors, reparenting, and was still unable to see the texture properly applied.

We will look into it.

2 Likes
5

Idk if it’s any help, but I noticed Texture/Decals don’t work unless the MeshPart has a MeshId. But since EditableMesh doesn’t have a MeshId? Unless I’m doing something wrong?

6

That’s correct, editable objects don’t have an associated asset-id. In other words, MeshPart.MeshContent.SourceType == Enum.ContentSourceType.Object (not Uri)

This is a bug on our end, you’re not doing anything wrong.

2 Likes
7

Any updates on this? Textures still don’t apply to EditableMeshes.

1 Like
8

Hi, thanks for the follow-up.

This issue is still in our backlog. To be transparent, it’s currently a lower priority compared to other bugs we’re addressing. We will get to it, but we still can’t provide an ETA.

We appreciate your patience and for keeping this on our radar.

2 Likes
9

Are there any more updates on this?

I noticed this the other day

Idk if it would solve this issue or it’s something completely different

1 Like
10

Any updates? I’m trying to achieve the same thing with a texture on a editable mesh