[Bug] Changes to Material Panners have caused incorrect UV math issues.
I'm not entirely sure where this issue is stemming from, but I hope the following screenshots highlight the problem I'm having. I have re-created a material network that I created in UE3 to UE4, but there are apparently some math differences in the way the panner nodes now work, which is causing it to break/render incorrectly.
The idea is to add a second layer of more interesting UV distortion, this is the material network in UE3, all the nodes are commented with their values and 'live preview' is switched on, so you can see exactly what's happening at each node:
I then re-created this network in UE4, but as you can see, the panner nodes offer quite a different preview, setting negative panning speeds in the panners actually seems to cause them to preview completely incorrectly, and this is having an effect on the resulting math that follows, the difference between the UE3 and UE4 material is quite substantial and broken.
A more obvious example is probably here, where I'm using another layer of distortion on top of the original, again, the UE3 preview shows the correct result, whereas the UE4 preview is completely blacked out on some nodes due to the negative values in the panners. This is causing some strange tiling on my resulting material.
I'm not really sure how to explain the issue further, but you can see the difference in the nodes themselves, and this is causing an issue with my final material.
asked Mar 11 '14 at 01:54 AM in Bug Reports
ue4-archive ♦♦ STAFF
Thanks for providing the assets and additional information. I was able to load them up and take a look and it appears to be functioning correctly in our internal build. Please look for the adjustments in an upcoming Rocket release.
Regarding the UE4 preview being completely blacked out on some nodes due to the negative values in the panners, our developers have indicated that this is an intended change from UE3 as in this situation they were not accurately representing the preview values correctly. Since there is no good way to visualize negative values, we display them as black instead of display an incorrect preview.
Interesting, I'll have our QA try to reproduce this in house so we can investigate.
Follow this question
Once you sign in you will be able to subscribe for any updates here