2 ms·
Oh, no I am self-aware of how that probably comes across haha. I know it's a really complex field but I guess the presumption is that these things would work ou
by ehnto 8y ago
Oh, no I am self-aware of how that probably comes across haha. I know it's a really complex field but I guess the presumption is that these things would work out of the box because they are so core to the experience of the engine. I essentially changed not because I thought it was easy but because after digging into the issue I realised how complex the domain is, and I couldn't afford to be bogged down with it when another engine does seem to get it right out of the box for my use case.
I guess my categorising them as no brainers is just that the use case seems so obvious that it not working is surprising. It was just a door casting a shadow onto a floor plane, I may have done something wrong but, that it was even slightly problematic was a red flag to me.
- stephth 8y agoHow did Unreal compare regarding that issue?
- ehnto 8y agoIt was much more straight forward to build levels that would be well lit with the standard tooling in my experience. I didn't have to change anything at all and there were fewer weird artifacts to clean up. The asset workflow from Blender to substance painter to Unreal also had no hidden demons. It all just worked as expected. Just to be clear as well, my concerns weren't about the post processing stack which I got working to good effect in Unity. But the lightmapping and material workflow is just a bit clunky in unity. To say nothing of the confusion that having more than one lighting engine causes in docs and online support.