r.MaterialQualityLevel=1 breaks POM materials in packaged builds

Development Rendering
, , , , ,
1

There is a quality setting switch inside POM node. You can rewire it as suitable for your project.

2

I’m seeing this same behavior in Packaged builds in 4.15
If I call the r.materiallevel function, it seems to fix the shader and I can return to the higher quality levels.
I wonder if this is tied to the Enable Static Lighting switch in the game settings?

3

Hi,

After much investigation I have found an issue with the command r.MaterialQualityLevel.

I use the sg.EffectsQuality scalability commands. I looked inside BaseScalability.ini inside the engine and ran each command trying to find the one which causes the POM render issue. I found that r.MaterialQualityLevel=1 is the issue.

When a packaged game has run r.MaterialQualityLevel=1 before loading into a level any materials with POM will not render at all.

r.MaterialQualityLevel=1

http://i.imgur.com/IZzvtAQ.jpg

r.MaterialQualityLevel=0

http://i.imgur.com/21a9TfX.jpg

r.MaterialQualityLevel=2

http://i.imgur.com/FfHDVEJ.jpg

And here are 2 materials which go blank with this setting:

http://i.imgur.com/Qb1XaNR.png

http://i.imgur.com/7g1Kri0.png

4

Still occurring in 4.17.2.