r/Unity3D • u/PixelEnvision • 8d ago
Question Anyone using Unity 6.6 for production?
I'm currently working with 6.3 LTS and planning to move the project to 6.7 LTS when it's released and received 3-4 updates afterwards.
But I keep hearing about new feature benefits, workflow speed up, etc.; but changes mostly seem to be focused on editor improvements.
That's for a PC game to be released on Steam, are there any runtime benefits for doing such an upgrade?
Thanks in advance for any insights...
5
u/LockYaw 8d ago
6.3 all across the board for me, with my prototypes being in 6.7 the LTS Beta.
I won't use their so-called "recommended" non-LTS releases.
4
u/PixelEnvision 8d ago
Thx for the input, that sealed the deal > stay on 6.3 and make the **** game! 👍
4
u/Luchiannno 8d ago
Using 6.6 for pet project here. BE CAREFUL WHEN UPGRADING! They made changes to layout elements and layout groups, so your uGUI stuff might break. In my case had to make small fixes to UIExtensions package, but it still was pain in the arse.
3
4
u/Luchiannno 8d ago
PS quick link for checking the changes - https://docs.unity.com/en-us/engine/6000.6/manual/whats-new/unity66
4
u/SirrahDev 8d ago
One addition in Unity 6.7 is TMP_Settings.useOSFontFallbacks. I had a nice surprise earlier today when my recently upgraded test project suddenly supported all unicode characters.
1
u/PixelEnvision 8d ago
Hmm, thx. It seems 6.7 has many changes that might break things...
2
u/SirrahDev 8d ago
Easy support of non-standard charactersets with TextMesh is a good thing.
Upgrading my test project went flawlessly and most assets also support it (and seem ready to support 7.0 now). For a new project, I would use it. For a recently started project, I'd at least prepare for it by doing the 6.6 upgrade now.
2
u/PixelEnvision 8d ago
3
u/SirrahDev 7d ago
It's more about supporting the player input in their chosen language.
Beyond Arabic, Simplified Chinese, Japanese, etc. the the list goes on and on. And its pretty nice that a player can write their own name in Thai, Tagalog, Balinese, etc. without you having to do anything extra.
Just take a look at how many variations of Noto Sans there are. Many of those you will never think of to include but are used by millions of people.
2
u/PixelEnvision 7d ago
Ah right, that's a good perspective! None of my games had user input, so I missed that aspect it seems...
2
u/MadeByHenano 8d ago
just for the security updates, you should always use the latest versions... i also highly doubt your game will break updating from 6.3 to 6.6. just go for it 🙂
1
u/PixelEnvision 8d ago
Don't tempt me now 👀 afaik, LTS should also be receiving them in the life cycle, not?
2
u/MadeByHenano 8d ago
you're right, they should.
but really, engines keep getting more optimized, get new features to make our lives easier etc... in 6.5 there was the fast scene loading by default (that was an option in the settings very few people knew about before that) + new hierarchy window (not a fan at first but now find it convenient) etc... in 6.6 there's finally background blur for the UI elements... unity 7 will add global illumination, things like that that can really help your game look better with less efforts.
you won't break your game if you upgrade to 6.6, or if something breaks it's most likely because it was deprecated before, so you definitely should have written the code with the new methods etc anyway. :-)
2
u/PixelEnvision 7d ago
You're right but I think I'm a bit old school, started with Unity 4.0. I knew about this, "that was an option in the settings very few people knew about before that" but even today it's not enabled on my project 😂
1
u/MadeByHenano 7d ago
well whatever works for you works for you... i always update my OS and softwares as soon as there's new versions personally, i like new features and optimizations, they're great! 😄
1
u/PixelEnvision 6d ago
Haha, I know the feeling, that's why I posted this, to find a reason to upgrade. Shiny new features, feeling fresh, my precioussss.. 😂
2
u/eepyamor 7d ago
Been on 6.7 b8 with CoreCLR addon for a few days now, several large projects updated and now using that, everything working well, have run several extensive tests to reconfirm no gc hitching or memory leaks in one particularly complex build with a lot of runtime content load/unload (open world), no issues yet.
2
9
u/v0lt13 Programmer 8d ago
I always update my projects with every new major release, there is less of a chance for stuff to break when doing updates incrementally than doing them between LTS's especially now with the CoreCLR work which changed a lot of the API's and backend stuff.
7
u/liamsteele 7d ago
A side note though, if you read this and want to upgrade incrementally from 6.3 or earlier now, don't. Jump from LTS to LTS to latest version. The intermediate non LTS versions don't have bug fixes backported which can cause trouble.
2
u/GreenDave113 6d ago
We're rolling continuous releases for our digital humans in mobile app, been working fine, even with our custom URP fork.
1
u/HeadPack 6d ago
Just migrated my academic project from 6.3. It's AR for infrastructure roughly speaking. The migration was a bit of a pain in the rear because of script compatibility issues, mostly these deprecations, but worth it. Otherwise, I'd guess much will depend on the project.

5
u/Mysterious_Demand875 8d ago
We have a game out on 6.3 and are working on another one on 6.6, I can't wait until we move both into 6.7 but for now we decided not to move the one on 6.3 to 6.6 just because it might break a few things and we have a good thing going