@fguinier
Hello Florent!
If I understand your reasoning correctly, I have to disagree, though.
In 5.2.2, even final iOS builds had much better shadow quality on the device (not just inside the editor) compared to what I get in the 5.4.0F1 editor and in 5.4.0F1 iOS builds.
To me, it clearly seems to be a problem with the shadow’s resolution. Even worse ( !! ) settings than fantastic look better in 5.4.0F1, which is weird as well.
Please take a look at the screenshots of an iOS game that I released using Unity 5.2.2:
https://itunes.apple.com/us/app/one-life/id1033007854?mt=8
I made those screenshots on device.
The shadow quality there is very nice.
That project was also using just one directional light.
If this really is a bug, which I’m pretty sure it is (in fact, I just cannot reproduce 5.2.2’s shadow quality in 5.4.0F1’s iOS editor and builds), I hope this can be fixed in time for 5.4.0’s final build?
It really has been rough developing with very buggy 5.x releases and as far as I can tell, 5.4.0F1 is pretty stable now, but I cannot work with shadows like these.
@Metron
Thank you for your reply!
It’s weird, though. In 5.2.2, I get very nice quality with shadow distance 150, which is the default fantastic setting. So basically, in 5.2.2 the shadows just work and look nice. I don’t even need any optimizations there.
EDIT:
I cannot see any difference in the quality settings in 5.2.2.
The shadow distance is 150, too. Cascades are set to four cascades and shadow projection is stable fit.
Maybe in 5.2.2, shadow cascades weren’t set to none for iOS?
After reading Unity’s documentation, I can say “Close fit” is not an option for me.
Besides, it worked in 5.2.2, too. Why shouldn’t it work now?