[Runtime Bug]: Render artifacts linked to high xformOp:size values

[PappaSlask]

Describe the bug

When using a small mesh, and the user wants to increase the size of that mesh a lot, using the xformOp:size value, for example a 1.0x1.0x1.0 plane mesh to become 500 x 1.0 x 500, the center of this mesh will introduce noisy black outlines formed as a cube. This artifact is becoming more and more visible as the size of the mesh is increased. At 16 or 32m the artifact is nearly invisible. But as the size value is increased, the artifact becomes more visible. Here's some screenshots:

And here's three screenshots showing how the artifact subsides with distance from the center of the mesh:

The artifact is especially noticeable on semi-transparent materials.

The solution to this problem is to make your mesh as big as you need it prior to inserting/importing it to your scene in Composer, so that you don't need to rely on the xformOp:size values to make it big.

How do you reproduce the bug?

Inside Composer:

• Create a simple box or plane mesh
• Increase its size to 1000 x 1.0 x 1000
• Add a plain, solid color to the mesh
• Replace a vanilla game's mesh to bring it ingame
• Go to the center of the mesh ingame and look down

What is the expected behavior?

The runtime should...

Version

0.5.1

Logs

No response

Crash dumps

No response

Media

No response

[NV-LL]

Thanks for reaching out. A few questions:

• Would you please provide us with a mod package/set of files that you used to reproduce this test case?
• In what game did you encounter this issue?
• Does this happen in both the toolkit and the game, or just the game?

[PappaSlask]

Thanks for reaching out. A few questions:

• Would you please provide us with a mod package/set of files that you used to reproduce this test case?
• In what game did you encounter this issue?
• Does this happen in both the toolkit and the game, or just the game?

Hi LL and thanks for taking care of this!

• Sure, I'll setup an environment where this bug happens and share all relevant files shortly! But you're going to have to obtain Max Payne 1, but before that, you could always try this in another game first, because I think this bug is related to the Remix renderer and not being game specific.

• The game in question is Max Payne 1. But I have reason to believe this happens in more games, or even in any game if the circumstances are right.

• Not sure about the Remix app, as I'm using Composer, but it's not happening there, only ingame.

[PappaSlask]

@NV-LL Hi Lindsay! I've prepared a test environment for use on the first level (house prologue) of Max Payne, kindly try it out and see if it's working as supposed. I'll attach the relevant files in this post. You'll need to remove the ".zip" part of the filenames in order to extract.

You'll need to disable Volumetric Lighting under Froxel Radience Cache/Volumetrics But I also included this in the READ ME.

Artifact_debug_test_files.7z.001.zip Artifact_debug_test_files.7z.002.zip

[PappaSlask]

@NV-LL Did you follow up on this? Will there be a ticket?

[NV-LL]

Hi @PappaSlask - we apologize for such a delay! Thank you for providing those files for repro, and we've opened REMIX-3573 for tracking.

[PappaSlask]

Hi @PappaSlask - we apologize for such a delay! Thank you for providing those files for repro, and we've opened REMIX-3573 for tracking.

Hi Lindsay and thanks for the update! I want to add a few comments regarding those files that I shared: Some people have had troubles extracting their content, so let me be clear: You NEED to remove the ".zip" part of the filenames to extract, so that both files look like this:

DXVK_Bridge_latest_working_versions.7z.001 DXVK_Bridge_latest_working_versions.7z.002

You may or may not need 7zip to extract them, unsure if they work with winrar or Windows built in extractor!

The reason for this is that the file attachment/uploader for Github doesn't support 7z or split archive files, only plain .zip files are accepted, I worked around that limitation by adding a fake .zip suffix to the files ;)