Source: x.com
Unity 6 is slated for release towards the end of 2024. A specific date has not been announced yet.
Unity 6 beta feature highlights: Unity 6 beta (2023.3) - Feature Highlights
Source: x.com
Unity 6 is slated for release towards the end of 2024. A specific date has not been announced yet.
Unity 6 beta feature highlights: Unity 6 beta (2023.3) - Feature Highlights
No official thread about that?
Not that I can tell. Seems like socials people pulled the trigger a bit early. It was likely slated to be revealed at the Unite keynote in about 4 hours:
Or the youtube version is just a replay, and it has all already happened. I haven’t paid attention to Unite schedule.
The keynote is long ended. On YouTube you will see the thing from recording. Hopefully not edited. Also no Roadmap talk for YouTube AFAIK. Only keynote.
Also people already are defending this performative BS. I guess Unity can’t shoot themselves in the foot hard enough for some people.
https://discussions.unity.com/t/932808 page-5#post-9474865
sounds to me like another desperate attempt to redemption from pricing changes.
Anyway, I’m confused more than ever. I guess Unity will have fewer versions of the engine to support.
I thought this was Unity 2024 but it’s actually Unity 2023 LTS rebrand. Weird to say the least.
This explains the weird wording of all the revenue discussions that went “starting with the LTS release that comes in 2024” rather than just saying “2023.4 LTS”. They were planning the rename.
This also seems to mean they can rejigger the release pipeline any way they want now. Rather than expecting a .1 each year, they can just sit around with v6 for 18 months, then v7 for 29 months, then v8 for 43 months… just like they used to do.
100% the only reason they’ve done this is because they know they absolutely can’t stick to the yearly naming convention anymore. What was the reason they gave for the switch to yearly anyway? Because I think they said that was to avoid confusion too.
I would be excited if I heard “We remove SRP and focus on one modular pipeline”…but atm nothing excites me there…we will see :).
Its just 2023 LTS rebranded; nothing like the older 2, 3, 4 & 5 new versions which came with some big feature overhauls and additions and deprecations of some older stuff.
The skeptic in me says this is a marketing cover up of the out of sync release cycles (LTS shipping 6 months later than its named year) and also the runtime fee stuff (which is attached to this version). Also playing up dev-nostalgia for the old release cycles before JR became CEO.
I also hope Synty is getting a sizable cheque for the amount of times their demo projects are used by Unity.
Like I mentioned in the licensing thread that’s precisely what this is, but like I also said it makes sense to abandon it too because it’s a scheme that is intended to have releases come out the same year that they’re labeled. It was just needlessly confusing.
I haven’t touched Unity in over a year and seeing Unity return to the old naming scheme helps a bit. Now I hope they DO focus and improve the engine and improve the life of the developers who use it
If unreal wanted to be cheeky their next release could be Unreal 6.01
If the release cycle doesn’t change, will we get Unity 7.1 before Unity 6 LTS?
This is great. Now we just need them to start going backwards with that number.
Unity 3.5 here we come!.
I think it will change. The .1 will be public alpha, the .2 will be public beta of the next major release. So I think there won’t be 6.1 or 7.1. There will be 7 alpha (what would be 2024.1) and 7 beta (what would be 2024.2) and 7 LTS (what would be 2024 LTS).
Nah, they went from 2023 to 6, which means the next version will be -2011
Well that’s still a step in the right direction…
The release notes:
When Unity would do it, this would be the original plan but the results:
I wonder if this will mean anything or if it’s simply just that - a naming change. Part of me would assume a change like this signifies a wish make considerable changes and implement major new features without having to worry about compatibility with previous versions. But at the same time, considering how everything seems to move into and revolve around packages nowadays, it feels like it’s too late to pivot into such a strategy.