Are you still getting the blurry mip issues though? I’ve had a non-VT texture based RVT material and has been unforgivingly blurry ever since UE5 came out.
We also have issues with VT in our scene. We are heavily using Quixel Megascans and texture loading in Stand Alone is very slow. If I use the non vt shader, the loading is much faster and almost immediately. Probably for now we are avoiding using VT.
Trying to solve this exact issue right now…
Same issue with a landscape rendering into a volume then sampling back the RVT.
But this solution worked for me in the ElectricDreams demo project. The double DXT5 pool entry isn’t configured. I edited the project’s \Config\DefaultEngine.ini with a new entry.
Then you still need to ensure there are no virtual texture samples rendering into the runtime texture output from your material as that seems broken.
3 Likes
Addendum;
If your using the YCoCg Base colour with the extra mask, it uses a separate pool than the double DXT5.
So add another Formats line for PF_DXT5,PF_BC5,PF_DXT5 else it will use defaults too.
3 Likes
This is the solution here, finally after all this time it was the pool sizes. RVT is actually feasible again in UE5 with this config, much appreciated!
2 Likes
Also:
- Simplify the shader and terrain.
- Reduce the resolution of the virtual texture. Reduce the Virtual Texture Tile Size first.
- Use baked Streaming texture. The higher the resolution of this texture, the better. Of course, this texture will take up video memory.
- Check texture pool size.
This seems to have fixed it for me as well, using the original fix and the addition mentioned. Thank you both from the bottom of my heart, I was going insane!!!
Please guys I’m struggling with the same issue since months, can I get the solution along with some screenshots explaining the settings…Thanks in Advance.
This is the post up-above that described the solution: Runtime virtual texture sets landscape to lower mip - #57 by cannasoftware
-=-=-=-
Use the following console command to show the pools around residency:
r.VT.Residency.Show 1
You should see some graphs like such (you do this whilst running, not in editor):
The line tracks consumption, starts at the bottom and rises as pages/resources are consumed from a given pool. If the red-line reaches the top you are consuming all the resources in that pool and need more (you’re bottoming-out).
In your ‘C:\Program Files\Epic Games\UE_5.3\Engine\Config\BaseEngine.ini’ file, locate a section like this:
[/Script/Engine.VirtualTexturePoolConfig]
; Configure VT physical memory pools. Usefull commands to set these
; “stat virtualtexturing” show dynamic use of the VT system including the cache loads
; “r.VT.ListPhysicalPool” list in-depth details on the allocated physical pools
; The upper allocation limit for a pool is caluclated by matching a size and format from the list below or falling back to the default
DefaultSizeInMegabyte=64
+Pools=(SizeInMegabyte=96, MinTileSize=0, MaxTileSize=9999, Formats=(PF_DXT1, PF_DXT5))
+Pools=(SizeInMegabyte=512, MinTileSize=0, MaxTileSize=9999, Formats=(PF_A32B32G32R32F))
+Pools=(SizeInMegabyte=128, MinTileSize=0, MaxTileSize=9999, Formats=(PF_DXT5, PF_DXT5))
Add/futz-with the values for the pool that is bottoming-out. Test, repeat.
I have some issue, randomly turn my landscape into grey color or low res.
Can fix this issue by clicking "
SetBounds" in my RuntimeVirtualTExtureVolume actor in the level. Try play standalone got no issue.
This is what i get… constant blurring when moving the camera and backing up…
What should my settings be? Nothing i do seems to work. I am using the YCoCg Base Color, Normal, Specular, Mask
Documentation says BC3 + BC5 + BC3
though when i run this command to check it looks like DXT5, BC5, DXT5 is way over… not sure what to do about it.
found my issue had to do with the tile size for the virtual texture… lowering it made it no longer blur when i turned the camera.
So I have a weird issue, I can’t seem to increase the fixed pools, no matter what. Anyone got an issue like that?
Oddly, if I lower their value that is on the HUD chart, then the HUD is updated and get lowered as well. Also changing the mip residency also makes their green line go higher, so I’m sure the fixed pools are being used, but for some reason they are capped at that random value.
Btw, my issue wasn’t that the landscape is blurry overall, but rather that if I rotate the camera, I see blurry for a 1 second. I managed to fix this by changing the Feedback resolution factor to 8.
Hope this helps someone.
If you enable RVT for your landscape, your landscape material should not use VT sampler and VT. Lnadscape mateiral sample VT from wrong mip level when it enable RVT. So, here is a simple solution, your landscape only use non-virtual texture.
I am getting this problem as well. I am using quixel asset and the texture is all blurry with enabling RVT on the mesh. is there a work around for this ?
Also had this issue (5.4.4, and still here we are), and, as well as someone said above - switching to non-virtual textures in material that outputs result to RVT helped.
Then, I found that if using vitrual textures in material, output becomes blurry when I manually change VT pool size in the project settings (Project Settings → Engine → Virtual Texture Pool), or sometimes if it changes automatically (although in most cases pool auto grow didn’t caused blurriness, but manual changes always caused it - either when I changed default pool size, or changed fixed/transient pools). Weird thing that if you just open texture assets used in material - brurriness goes away (while other things, even engine restart/recreating all setup from scratch didn’t helpedl).
So, after I set default pool size to a bigger value (default is 64mb which is really small, although for me changing it to 256 mb was enough to not see texture loads), and disable checkbox ‘Pool Auto Grow in Editor’ - with this I was able to get rid of blurriness and still use VTs in material… in PIE. Sadly, but when using Standalone - blurriness returns. So there is definetly smth wrong with Texture Sampler when using VT/or with VT itself, but I haven’t been able to figure out what exactly.
With the release of 5.5, the patch notes have many virtual texture changes. Under my project I was running both r.VT.MaxUploadsPerFrame and r.VT.MaxUploadsPerFrameInEditor at 0 since the cost of 1 was really high on most machines and was still loading properly enough without much cost by VT. So in case it looks worse with 5.5 make sure you run that value at 1 minimum.