Hey folks,
I’m resubmitting [this][1] as a bug since after some more testing it looks like an issue.
I’m having issues with a masked material applied to a Static Mesh (set to movable) which has an animated Opacity Mask. The effect I’m trying to achieve is of an object that gradually appears from the bottom going up. Here’s the graph of a test material that I setup to show this issue:
The effect itself was pretty easy to achieve but I’m having a weird issue with the shadows. Here’s a screenshot of the problem:
The shadow isn’t rendering, unless the masked part isn’t visible (if A == 1 or if the camera is zoomed in enough to hide the masked part. I thought this was somehow a UV issue, because feeding a regular gradient texture to B correctly displays shadows but I’m getting inconsistent results in trying to fix this problem.
I’ve tried replacing B with a gradient texture that had BoundingBoxBased_0-1_UVW’s R and B channel as the UV but still no shadow. Why the mesh renders correctly but the shadow doesn’t?
Hey vernocchi,
I tried setting this up on my end, but I did not get the results you are reporting. I suspect it is directly related to your mesh. Could you provide me a sample project in which to test and verify the issue you are reporting?
Let me know if you have further questions or need additional assistance.
Thanks,
Hey Andrew,
I highly doubt it’s a mesh problem considering I’m getting the same issue on the Basic Cube and from a Cube I freshly exported from Blender. I’m on Mac 4.11.2 (Metal) but we have the same issue on Windows.
In any case, here’s the test project showing all of that: TestProject
Hey vernocchi,
This is actually a bug in 4.11.2, but if you enable ‘Two-Sided’ on the material as well as enable the ‘Two Sided-Shadow’ on the mesh placed in the world within 4.12, the shadow renders as expected.
Let me know if you have further questions.
Thank you,
Hey Andrew,
so the bug is already known and a fix is coming?
Unfortunately checking “Shadow Two Sided” doesn’t fix the issue for me.
Cheers,
Gian Paolo
So this is a bug just in 4.11.2 right? You’re saying that changing that settings works in vanilla 4.11? Because it’s not working for me in 4.11.2.
The question is, if it is in fact a bug why there is no official report for it?
A bug was never specifically entered for this issue that I could find, but the issue does not occur in 4.12 using the settings I mentioned.
No, I am saying this is fixed in 4.12 using the settings I mentioned.
Sometimes fixes for other bugs will indirectly fix and/or break other features. In this case, a fix was made somewhere in the process of working towards the 4.12 release, which fixed the issue you are having.
A bug is not needed as this is fixed in the release after 4.11.2, which won’t receive any more hotfixes. Entering a bug would be seemingly pointless since it no longer occurs in future builds.
I’m so sorry Andrew, I’ve read 4.11 all along. It’s been a long day.
Thanks for the patience!
No worries, I understand your pain. I look at version numbers and changelists a lot during the day so I get where you are coming from. Best of luck!
