Checking thing on HDRP not always the best testing strategy. I will do a bug report asap about stupid memory issue on 2022.3.8 LTS. While using universal render pipeline after some random 5-20 min time even in empty scene my scene machine ram usage hit the 28 gigabytes+ and keep increasing until it killed my windows session. Ram backed to normal while I closed the unity editor.
**There is no script in my project. Just a main camera, directional light.
**Tested on two machines. same issue.
I don’t find this issue in HDRP and legacy pipeline. Unity needs to fix this issue soon. Whatever I will switch to unreal at year end, Almost finished learning. At least it won’t break the existing feature often.
LTS is not more stable than tech. Actually in the past I had to update to tech because some fix were only available to tech and not LTS, go figure.
Unless you go hard on the latest features or update as soon as it does come out, most of the time Tech stream is more polished on the basic/old features.
I just upgraded everything from 2021 to 2022, and if I didn’t see that 2023 has raised again the minimum requirements for mobile(removed open gl es 2.0 and Ios 12 support) I would have went directly with 2023.
I upgraded from 2021.3 URP to 2022.3 URP and everything started to freeze. Even the URP/Lit shader has an error message.
So I created a new project from scratch, configured everything according to my project, and dragged the folders out of the box and updated.
Several things improve, as if the update was not a good way to go.
Lots of things crashing like this: Constant Crashes - Failed to present D3D11 swapchain due to device removed.
Disappointed too.
The truth is that the last real LTS release was 2021, and that is what you should use if you need stability. The closest thing to an LTS with modern features is the 2023 tech stream, just pray that the specific features you need are either working or will actually be acknowledge by QA and fixed at some point before you need to ship. 2022 is the absolute worst option despite being labeled as the current LTS, it’s already unsupported since the critical fixes are going into 2023 and are not getting backported.
2022 is dead on arrival and Unity needs to take responsibility for that and stop misleading developers into using their worst release on offer by baiting them with an LTS label just to save face, in the long term this is going to hurt their image just as much as it will hurt developers that fell for it in the short term.
I sadly must agree to this. I’m during a massive update to my game this year, started on adding multiplayer back in January 2022. My focus of cause have been on NGO etc. and i have had great dialogs with people from that team and they solved and added stuff during the year.
However, as I was closing in on opening up public multiplayer beta here in december, me and my closed team of testers started to notice low fps. Long story short, it turns out Unity decided to redo some audio stuff in a LTS version that eats like 50% of the fps if you have a lot of audio sources/clips… which my game have A LOT of! Something that use to be close to free.
Oh yeah and it seems to be leaking, so the longer game session you play the lower FPS you get…great.
I really like Unity and indent to use it for many years ahead - but things like this is just not ok.
REALLY nope they fix it soon… sadly it won’t be before New Years where I have my high season of my game.
Not sure what you mean? I linked to the thread and in there there is a link to an issue, however, there is also an Unity employee saying they fixed it in that thread.
Maybe I was too fast, I was thinking 2022.2 was LTS, but maybe it’s not until 2022.3 it’s LTS.
So maybe they didn’t break it in an LTS update - but they did break it between 2021 and 2022. And it’s like eating SO much FPS/performance. Look at my screenshots in the thread.
Anyway, they said they fixed it and MAYBE it’s coming to 2022.3.x LTS in January 2024…crossing fingers
