Unstable / Corrupted Runtime Virtual Textures

We’re having an issue with RVT’s where they show either corrupted tiles or wrong pages, its really hard to say what’s going on, but we’ve uploaded Pix captures and videos of it happening on our BOX file storage in the RVT Folder.

This has proven itself extremely hard to reproduce reliably, but it does happen with a high frequency, just not when we try to validate a fix for it.

Any pointers to why this sort of bug is happening and any settings/console commands that might help improve the situation would be really appreciated.

Steps to Reproduce

We are using RVT’s to create a smooth transition between two landscapes. - We might be able to provide access to the steam beta where this is happening for further testing on your end.

Hello there,

It seems that this may be related to an issue reported here: [Content removed]

One setting to try would be r.VT.PageFreeThreshold 15 (down from the 5.2 default of 60. 15 is the default in UE Main going forward.), though if it is the same issue, there may be API validation issues when running with -rhivalidation or -d3ddebug.

If the issue isn’t related to that issue, I’m not sure I can see the PIX captures, but they would be useful to diagnose the issue further.

Best regards,

Chris

The issue shown here - [Content removed] - looks similar to our issue, and using the RVT MIP debug CMD does show some potential issues - the red squares among the other MIP Colors.

[Image Removed]

Hello! Just wanted to jump in and point out that if there is a better/updated fix, CL#42038703 (public issue) which should be easy to cherry pick, for the issue reported in [Content removed]

By any chance does this issue appear to be hardware or driver dependent?

Hi! Thanks for this pointer, We’ll give it a go!

The pix captures should be uploaded here: https://app.box.com/folder/319785776914

Thanks [mention removed]​! We’re currently testing the fix from - [Content removed] - But I’ve also shared the CL you gave us to our Render Coders.

The initial results from the first fix is promising, but since its a tricky issue to reproduce we’re not 100% certain yet.

I’ll post an update here if it happens with these fixes or not.

Update: After implementing this, we’ve not been able to repro the issue!

Tested this as well - and the bug is gone for us!

Thanks! for the quick repsonse!

That’s fantastic news, I’m glad it’s resolved.

And thank you, Alex, for jumping in with that changelist.

If you have any further questions, please feel free to ask. Otherwise, would you mind if I close this case for now?

Best regards,

Chris

Sorry for the delay - Yeah you can close the case for now!

Thanks for all the help - our Large beta went ahead without the RVT Issues!

You’re very welcome.

I’m glad to hear that that resolved those issues.

Best regards,

Chris