I was wondering if it was possible and if it was planned to have the texture created with the node “extended mesh” generate a Virtual Texture? Right now, even if we feed Virtual Texture to the “extended mesh” node, we end up with a merged texture none VT.
I dont know if it’s a limitation to do so in realtime, but if we could have an option to make those texture VT, it would be very usefull
I’m sending this question along to the Mutable team to answer, but regarding virtual textures for your use case: if the texture is generated in-Editor, you can set the virtual texture flag on that texture at creation time. However, if you are creating these at runtime there may not be much value in them being virtual textures since they likely need to be fully held in memory anyway.
If the reason you want them to be virtual textures is that you already have materials that read from virtual textures, you might just need to have static switch permutations to read from a virtual texture or not. We do also have UVirtualTextureAdapter which can wrap a regular texture (from Mutable in this case) for binding to a virtual texture slot in a material. We use that for a couple of Editor use cases like mesh painting, but it has a lot of overhead to copy from the source texture to the virtual texture pages on use.
Hi, just a quick follow-up that I’m going to pass this issue over to one of the Mutable dev team to get you an answer. They have a few people out of office at the moment so it may take a little while for them to respond.
I apologize for not getting back to you sooner. Mutable does not currently support generating virtual textures. It is something we may evaluate in the future, but there are no plans in the short/mid-term to tackle this.