OK, I suspect this might be caused by the Nux fix for bug 1014610.
That fix was developed because the fix for Unity bug 988079 requires it. However the fix for bug 988079 has not been released in precise yet (coming soon in Unity 5.16). So maybe the issue here is that the old Unity rendering code is not fully compatible with the fix for Nux bug 1014610.
I guess we will get an answer when Unity 5.16 is ready for testing. This bug may well vanish in Unity 5.16.
OK, I suspect this might be caused by the Nux fix for bug 1014610.
That fix was developed because the fix for Unity bug 988079 requires it. However the fix for bug 988079 has not been released in precise yet (coming soon in Unity 5.16). So maybe the issue here is that the old Unity rendering code is not fully compatible with the fix for Nux bug 1014610.
I guess we will get an answer when Unity 5.16 is ready for testing. This bug may well vanish in Unity 5.16.