9 ms·
That's pretty bad, but I'd still file that under "too-hastily deprecating things before the new version is at parity". Not that it isn't a huge issue, but could
by brundolf 6y ago
That's pretty bad, but I'd still file that under "too-hastily deprecating things before the new version is at parity". Not that it isn't a huge issue, but could it be a temporary issue? Is the newer one, in theory, on a good track for the long-term?
- squeaky-clean 6y agoThe newer one (URP) is already in its second rewrite after ditching the initial version (LWRP). They also completely split the post-processing stack into two incompatible stacks depending on whether you're using URP or HDRP, then backtracked and are attempting to merge them into a single stack again. So while maybe they'll get it all fixed soon, based on their track record I'm pretty cynical and bet it's more likely in 2021 or 2022 they'll announce yet another overhaul of the rendering stack(s), probably unifying them back into one stack or something.
- DizzyDoo 6y agoAbsolutely. One more additional thing: the latest back-track has been the URP-is-not-a-standalone-package anymore, URP package versions going forward are going to be tied to a specific Editor version. I imagine this is going to make the ability to backport features and bug fixes incredibly difficult because the dependencies are going to be so tightly enmeshed.
- DizzyDoo 6y agoI mean, I've been watching this unfold over multiple years, and I fully expect this to continue over the next two at the very least, and it applies across every slice of the engine that I'm aware of, and some that I'm not intimately familiar with (I hear second-hand that networking is somehow in a worse state?) I guess everyone has different tolerances for what may technically be a 'temporary issue.' Yes, I have no doubt that all this engineering will lead to a better, more stable Unity, but for right now I actually have to somehow write real software and ship something to paying customers.
- Vermeulen 6y agoIt's not - they didn't deprecate the 'built in' render pipeline, and said they don't plan to until the new one has feature parity. They have odd marketing for their new features - where they want developers to use them so they call them production ready - but they do that so they can get feedback and continue to fix them