Another stability issue: Upgrading Editor just forgot all the packages and that I was using HD render pipeline.
I can’t even add Entities package and half my game is DOTS/ECS now. I’ve been trying to update my Unity version since the 18th, spent a lil over 60 hours, no avail.
What is your package manifest file?
Does it contains upgrade changes?
Can you paste it here?
Checkout version control, what has changed.
Chances are, you got incompatible packages.
What was your previous version of Unity and packages. Specially entities.
Some packages were refractor.
Thank you. I’ll come back to this at a later date when I have time.
I’m suggesting the radical idea that UNITY should handle this automatically as I upgrade.
I spent 60 hours fighting with this. I don’t want to spend more time. I’ll stay on an old version of Unity for now.
Remember I spent about 600 hours trying to figure out how to use the scriptable build pipeline to make a standalone. It took me a full year to get DOTS/ECS to compile to standalone.
I spent about 500 hours on addressables, since it has many bugs in it.
Quite literally, in the past 2 years, almost a full year of my development has been dealing with unstable Unity issues.
UNITY is stronger now than it was 6 years ago if it works, but 6 years ago, I got a 10v10 multiplayer 3d starfighter MOBA done in 2 weeks just after rollaball tutorial. Now 2 weeks gets me stuck on simply updating the editor.
Imagine if you sold a video game, and your updates were buggy and told the players to read technical documents and write some code to keep playing. These business practices are unacceptable, this is an aggregate fall out of failed business policies of glitz and glam dog and pony shows indicative of Electronic Arts culture. You can take the executive out of EA, but you can’t take the EA out of the CEO.
Evolving software is not as simple as single button click unfortunately. Variation of projects, makes very complex to automate whole upgrade process. But Unity usually provide guidelines, about upgrading packages. Some stuff are handled automatically. Some are more complex for automation.
Either way, if you had provided info, ask on the forum early, then you would shortened time on your development, upgrade and issues.
So what is actual point of this thread?
Because initial post is no much helpful for yourself, neither Unity dev team. It got missing info. I thought you wanted an assistance.
If it is just for venting, then you should vent somwhere else to be honest.
3 Likes
So what is actual point of this thread?
Because initial post is no much helpful for yourself, neither Unity dev team.
Let me start off that I love Unity as a tool. I want what is best for Unity and the 2 fold reasoning for this post will explain it:
First Off A) UNITY is in crisis mode of being increasingly unstable. The last 2.5 years, I lost over 1100 hours due to Unity bugs or almost a full years of development between bugged scriptable build pipeline/addressables/editors bugging out. They need to tell the executives in charge, they’re running the show wrong. Focus on stability and not glitz and glam.
There’s two types of software architecture design. One is slapdash and gets something to work once and kicks it out the door to boast. When people use it, it may not even work for most ‘Addressables’. This fly by night devving results in updates being like building a house of cards on a tower of jello for stability. This is UNITY.
Proper software architecture really focuses on core foundational principles. This means as things become bigger and bigger, things actually get more and more stable. Updates become easier and easier to push. This is the proper architecture methodology for large projects such as Unity, not slap dash dog and pony shows to boast to shareholders about nonsense… Get us developers stable Unity so we can use what we have and raise your profit lines the honest way.
This is vitally important. 1100+ hours is a full years of devving in itself, just to bugs Unity could fix if they spent a bit more time on QA. I report bugs and the bug reporting filer just says,“Not a bug” and files it completed, bugs that have been pinned down and have been plaguging unity for up to 5+ years ago… I report the bug and solution and its just blown off. I do like Unity as a product even though it’s messed up with tons of bugs I could list if anyone was listening.
If you don’t reel it in and work on stability, often badly designed core foundational principles can snowball into legacy support so you can never fix it. So the sooner the philosophy is changed to stability over glitz and glam, the better.
Secondly B) And I do need help upgrading my editor. Here is my 2021.3.f5f1 manifest.json you asked for:
{
“dependencies”: {
“com.unity.2d.sprite”: “1.0.0”,
“com.unity.addressables”: “1.19.19”,
“com.unity.burst”: “1.6.6”,
“com.unity.collections”: “1.2.4”,
“com.unity.editorcoroutines”: “1.0.0”,
“com.unity.formats.fbx”: “4.1.2”,
“com.unity.ide.visualstudio”: “2.0.15”,
“com.unity.ide.vscode”: “1.2.5”,
“com.unity.mathematics”: “1.2.6”,
“com.unity.nuget.mono-cecil”: “1.10.2”,
“com.unity.nuget.newtonsoft-json”: “3.0.2”,
“com.unity.physics”: “0.51.0-preview.32”,
“com.unity.profiling.core”: “1.0.2”,
“com.unity.properties”: “1.8.3-preview”,
“com.unity.properties.ui”: “1.8.3-preview”,
“com.unity.render-pipelines.core”: “12.1.7”,
“com.unity.render-pipelines.high-definition”: “12.1.7”,
“com.unity.render-pipelines.high-definition-config”: “12.1.7”,
“com.unity.rendering.hybrid”: “0.51.0-preview.32”,
“com.unity.roslyn”: “0.2.2-preview”,
“com.unity.scriptablebuildpipeline”: “1.20.1”,
“com.unity.settings-manager”: “1.0.3”,
“com.unity.shadergraph”: “12.1.7”,
“com.unity.sysroot”: “2.0.3”,
“com.unity.sysroot.linux-x86_64”: “2.0.0”,
“com.unity.test-framework.performance”: “2.8.1-preview”,
“com.unity.textmeshpro”: “3.0.6”,
“com.unity.toolchain.win-x86_64-linux-x86_64”: “2.0.2”,
“com.unity.ugui”: “1.0.0”,
“com.unity.visualeffectgraph”: “12.1.7”,
“com.unity.modules.ai”: “1.0.0”,
“com.unity.modules.androidjni”: “1.0.0”,
“com.unity.modules.animation”: “1.0.0”,
“com.unity.modules.assetbundle”: “1.0.0”,
“com.unity.modules.audio”: “1.0.0”,
“com.unity.modules.cloth”: “1.0.0”,
“com.unity.modules.director”: “1.0.0”,
“com.unity.modules.imageconversion”: “1.0.0”,
“com.unity.modules.imgui”: “1.0.0”,
“com.unity.modules.jsonserialize”: “1.0.0”,
“com.unity.modules.particlesystem”: “1.0.0”,
“com.unity.modules.physics”: “1.0.0”,
“com.unity.modules.physics2d”: “1.0.0”,
“com.unity.modules.screencapture”: “1.0.0”,
“com.unity.modules.terrain”: “1.0.0”,
“com.unity.modules.terrainphysics”: “1.0.0”,
“com.unity.modules.tilemap”: “1.0.0”,
“com.unity.modules.ui”: “1.0.0”,
“com.unity.modules.uielements”: “1.0.0”,
“com.unity.modules.umbra”: “1.0.0”,
“com.unity.modules.unityanalytics”: “1.0.0”,
“com.unity.modules.unitywebrequest”: “1.0.0”,
“com.unity.modules.unitywebrequestassetbundle”: “1.0.0”,
“com.unity.modules.unitywebrequestaudio”: “1.0.0”,
“com.unity.modules.unitywebrequesttexture”: “1.0.0”,
“com.unity.modules.unitywebrequestwww”: “1.0.0”,
“com.unity.modules.vehicles”: “1.0.0”,
“com.unity.modules.video”: “1.0.0”,
“com.unity.modules.vr”: “1.0.0”,
“com.unity.modules.wind”: “1.0.0”,
“com.unity.modules.xr”: “1.0.0”
}
}
What steps should I take to update my editor from .5 to .10? .6 .7 and .8 busted me too, wasted about 50 hours trying to update to them, so its 110 wasted hours just trying to update my editor. Normally I just wait things out and a future editor will fix the bugs and I jump a few… But it seems like it’s forming a chasm so I need help getting up to speed.
Steps:
-
Should I update my package manager to latest?
-
Should I try some binary search micro jumps to .8, doesn’t work, .7 then .6?
Is there a way I can upgrade to 2021.3.10f1 without all my Unity Registry Packages being deleted away? Or does this do it to everyone when you get to .9 or .10?
I’m no here to bash Unity. I love this software. It’s like a Ship of Thesus tho, with some parts getting slapped on that are upgrades and some pieces downgrading it. Sometimes it is being sailed to places it should not be. An experienced sailor raises warnings to the captain and crew when it’s being sailed sub optimally in order that it can gain more performance and to avoid the rocks and sholes. There’s no need for me to praise a ship when it sails like it should, though I do praise Unity when it sails better than expected:
Do not confuse the passionate with the haters. Do not confuse criticism with hate either. Criticism is there so people can stop doing what is wrong and start doing what is right. Only those who are prideful refuse to be told when they’re wrong for it makes them angry instead of helps them do better.
A) While I completely understand the frustration and criticism you have, complaining about the overall stability of Unity as a whole on a subforum focused on highly experimental technology that is not “production-ready” is the wrong move. There are better places to state that criticism. Not here. And you would look much more intelligent if you just deleted all of those words and criticisms and just focused on the specific problem you face, at least until Entities 1.0 “stable” is released. That would also make your posts a lot shorter which would increase the chances of someone reading it and helping you. It also puts more focus on the actual issue you are having.
B) There’s a fairly well-known regression with IL2CPP between .8 and .9. Unless a patch release has a specific bug fix or new feature (rare) you care about, you are wasting your time updating. Also, you should really be using version control. If the upgrade process really did just forget all your packages, you could have just gone into the Packages folder, deleted the lock file, and replaced the manifest with the one prior to the upgrade. And maybe report a bug in the process.
But more likely, I suspect the upgrade dropped your Package Manager settings. So you were only seeing release packages without dependencies in the Unity registry rather than experimental packages in your project.
2 Likes
) While I completely understand the frustration and criticism you have, complaining about the overall stability of Unity as a whole on a subforum focused on highly experimental technology that is not “production-ready” is the wrong move.
With the depreciation of resources folder and assetbundles, Unity mistakenly forced Addressables as the only production solution. When an experimental package becomes the only production solution, it is no longer experimental. Unity took our only way of loading things outside the project away, so what was called the experimental package became the only option for what we used to do with assetbundles and resources. That’s a separate executive decision flaw in it’s own.
The editor is hardly an experimental package.
As for DOTS/ECS, it works flawless on my 2021.3.5f1 version and I have many elaborate systems. DOTS/ECS isn’t the problem.
There’s a fairly well-known regression with IL2CPP between .8 and .9.
I’m not even using that. I once tried for about 40 hours, didn’t work, so I stopped trying to get that to work. il2CPP’s problems are irrelevant to this thread.
And you would look much more intelligent if you just deleted all of those words and criticisms
You’re nearing crossing the line into a personal attack by calling me not intelligent, yet not really specifying what exactly I said incorrect. I didn’t come here for an argument or to be called stupid. I do not think I’m warranted of a personal attack for trying to make Unity a better product.
I’m intentionally approaching the line without crossing it specifically because you missed Antypodish’s very politely worded hint.
This is the DOTS subforum.
This isn’t the Addressables subforum. This isn’t the deprecations subforum. This isn’t the Package Manager subforum. This isn’t the platforms subforum. This isn’t the “general state of Unity” subforum. This isn’t the “how to do software engineering correctly” subforum. You even said it yourself:
When you post rants about these other topics in threads in the DOTS forum, people are going to judge you. That’s because what you are posting is logically irrelevant to the intended purpose of this subforum. The way most people enact their judgement of you is by ignoring your posts, which means you don’t get helpful replies and consequently you spend more time fighting the issue yourself alone.
You complained about having spent hundreds of hours troubleshooting issues. I’m trying to help you by explaining how to use these forums more efficiently and spend less hours troubleshooting. Will it completely resolve the issue? No. But the DOTS team isn’t the magic team that is going to solve those issues either.
If you are going to post in the DOTS forum about an issue, try to provide as much useful technical info that someone else may need to know to troubleshoot the issue, and nothing else. Otherwise, you are going to get suggestions that are completely irrelevant to the problem you are facing, as you’ve already seen. Or, people are going to ignore you.
This isn’t coming from someone being judgemental. This is coming from someone who used to make the same mistakes in how I spoke and posted on the internet. Even to this day, I am sometimes oblivious to how people perceive my posts and personality, and sometimes it requires people to harshly call out the very specific actions and explain why such actions make them uncomfortable for me to understand, learn, and grow.
Anyways, do with that what you will. I won’t judge. But to me, the issues this thread seems to be presenting have nothing to do with DOTS and don’t really belong on this subforum. But of course, if there is DOTS info that you haven’t shared that may provide further insight into this problem and consequently prove me wrong, then by all means share that information and if I can help, I will help.
But please respect the subforum topics.
1 Like
This isn’t the Addressables subforum.
I didn’t ask questions about addressables.
I wanted to give feedback the editor would not update.
I posted here because the editor would not allow me to even add DOTS/ECS from the packages menu.
When you post rants about these other topics in threads in the DOTS forum,
Look, other people can see you’re out to personal attack.
people are going to judge you.
and it looks like you’re trying to encourage other to dog pile on me. That ain’t cool. Justify your hate to yourself any way you wish, it still ain’t cool.
{
"dependencies": {
"com.unity.2d.sprite": "1.0.0",
"com.unity.addressables": "1.19.19",
"com.unity.burst": "1.6.6",
"com.unity.collections": "1.2.4",
"com.unity.editorcoroutines": "1.0.0",
"com.unity.formats.fbx": "4.1.2",
"com.unity.ide.visualstudio": "2.0.15",
"com.unity.ide.vscode": "1.2.5",
"com.unity.mathematics": "1.2.6",
"com.unity.nuget.mono-cecil": "1.10.2",
"com.unity.nuget.newtonsoft-json": "3.0.2",
"com.unity.physics": "0.51.0-preview.32",
"com.unity.profiling.core": "1.0.2",
"com.unity.properties": "1.8.3-preview",
"com.unity.properties.ui": "1.8.3-preview",
"com.unity.render-pipelines.core": "12.1.7",
"com.unity.render-pipelines.high-definition": "12.1.7",
"com.unity.render-pipelines.high-definition-config": "12.1.7",
"com.unity.rendering.hybrid": "0.51.0-preview.32",
"com.unity.roslyn": "0.2.2-preview",
"com.unity.scriptablebuildpipeline": "1.20.1",
"com.unity.settings-manager": "1.0.3",
"com.unity.shadergraph": "12.1.7",
"com.unity.sysroot": "2.0.3",
"com.unity.sysroot.linux-x86_64": "2.0.0",
"com.unity.test-framework.performance": "2.8.1-preview",
"com.unity.textmeshpro": "3.0.6",
"com.unity.toolchain.win-x86_64-linux-x86_64": "2.0.2",
"com.unity.ugui": "1.0.0",
"com.unity.visualeffectgraph": "12.1.7",
"com.unity.modules.ai": "1.0.0",
"com.unity.modules.androidjni": "1.0.0",
"com.unity.modules.animation": "1.0.0",
"com.unity.modules.assetbundle": "1.0.0",
"com.unity.modules.audio": "1.0.0",
"com.unity.modules.cloth": "1.0.0",
"com.unity.modules.director": "1.0.0",
"com.unity.modules.imageconversion": "1.0.0",
"com.unity.modules.imgui": "1.0.0",
"com.unity.modules.jsonserialize": "1.0.0",
"com.unity.modules.particlesystem": "1.0.0",
"com.unity.modules.physics": "1.0.0",
"com.unity.modules.physics2d": "1.0.0",
"com.unity.modules.screencapture": "1.0.0",
"com.unity.modules.terrain": "1.0.0",
"com.unity.modules.terrainphysics": "1.0.0",
"com.unity.modules.tilemap": "1.0.0",
"com.unity.modules.ui": "1.0.0",
"com.unity.modules.uielements": "1.0.0",
"com.unity.modules.umbra": "1.0.0",
"com.unity.modules.unityanalytics": "1.0.0",
"com.unity.modules.unitywebrequest": "1.0.0",
"com.unity.modules.unitywebrequestassetbundle": "1.0.0",
"com.unity.modules.unitywebrequestaudio": "1.0.0",
"com.unity.modules.unitywebrequesttexture": "1.0.0",
"com.unity.modules.unitywebrequestwww": "1.0.0",
"com.unity.modules.vehicles": "1.0.0",
"com.unity.modules.video": "1.0.0",
"com.unity.modules.vr": "1.0.0",
"com.unity.modules.wind": "1.0.0",
"com.unity.modules.xr": "1.0.0"
}
}
Oki, so this your current manifest?
Is tat before, or after upgrade?
I see there is no unity Entities, nor Jobs.
So I presume it is after upgrade.
If it is after the upgrade, can you show your version control differences of the manifest?
{
"dependencies": {
"com.codingwithunity.tweenlibrary": "https://github.com/sniffle6/Tween-Library.git",
"com.unity.2d.sprite": "1.0.0",
"com.unity.burst": "1.8.0-pre.1",
"com.unity.collab-proxy": "1.15.18",
"com.unity.collections": "1.2.4",
"com.unity.entities": "0.51.1-preview.21",
"com.unity.feature.cinematic": "1.0.0",
"com.unity.formats.fbx": "4.1.2",
"com.unity.ide.rider": "3.0.15",
"com.unity.ide.visualstudio": "2.0.16",
"com.unity.mathematics": "1.2.6",
"com.unity.memoryprofiler": "0.7.0-preview.2",
"com.unity.performance.profile-analyzer": "1.1.1",
"com.unity.physics": "0.51.0-preview.32",
"com.unity.properties.ui": "1.7.5-preview",
"com.unity.render-pipelines.high-definition": "12.1.7",
"com.unity.rendering.hybrid": "0.51.0-preview.32",
"com.unity.test-framework": "1.1.31",
"com.unity.textmeshpro": "3.0.6",
"com.unity.timeline": "1.6.4",
"com.unity.toolchain.linux-x86_64": "1.0.0",
"com.unity.ugui": "1.0.0",
"com.unity.modules.ai": "1.0.0",
"com.unity.modules.androidjni": "1.0.0",
"com.unity.modules.animation": "1.0.0",
"com.unity.modules.assetbundle": "1.0.0",
"com.unity.modules.audio": "1.0.0",
"com.unity.modules.cloth": "1.0.0",
"com.unity.modules.director": "1.0.0",
"com.unity.modules.imageconversion": "1.0.0",
"com.unity.modules.imgui": "1.0.0",
"com.unity.modules.jsonserialize": "1.0.0",
"com.unity.modules.particlesystem": "1.0.0",
"com.unity.modules.physics": "1.0.0",
"com.unity.modules.physics2d": "1.0.0",
"com.unity.modules.screencapture": "1.0.0",
"com.unity.modules.terrain": "1.0.0",
"com.unity.modules.terrainphysics": "1.0.0",
"com.unity.modules.tilemap": "1.0.0",
"com.unity.modules.ui": "1.0.0",
"com.unity.modules.uielements": "1.0.0",
"com.unity.modules.umbra": "1.0.0",
"com.unity.modules.unityanalytics": "1.0.0",
"com.unity.modules.unitywebrequest": "1.0.0",
"com.unity.modules.unitywebrequestassetbundle": "1.0.0",
"com.unity.modules.unitywebrequestaudio": "1.0.0",
"com.unity.modules.unitywebrequesttexture": "1.0.0",
"com.unity.modules.unitywebrequestwww": "1.0.0",
"com.unity.modules.vehicles": "1.0.0",
"com.unity.modules.video": "1.0.0",
"com.unity.modules.vr": "1.0.0",
"com.unity.modules.wind": "1.0.0",
"com.unity.modules.xr": "1.0.0"
}
}
Below is older reply, part of manifest which @Spy-Master replied to. Thx for pointing out, into manifest-locks.json.
Also ,there is something wrong with your manifest. Looks it has old structure. At least in comparison to mine.
It is expected to look something like mine below (For Unity version 2021.3.6 and entities 0.51.):
{
...
"com.unity.2d.sprite": {
"version": "1.0.0",
"depth": 0,
"source": "builtin",
"dependencies": {}
},
"com.unity.burst": {
"version": "1.8.0-pre.1",
"depth": 0,
"source": "registry",
"dependencies": {
"com.unity.mathematics": "1.2.1"
},
"url": "https://packages.unity.com"
},
"com.unity.cinemachine": {
"version": "2.8.6",
"depth": 1,
"source": "registry",
"dependencies": {},
"url": "https://packages.unity.com"
},
"com.unity.collab-proxy": {
"version": "1.15.18",
"depth": 0,
"source": "registry",
"dependencies": {
"com.unity.services.core": "1.0.1"
},
"url": "https://packages.unity.com"
},
"com.unity.collections": {
"version": "1.4.0",
"depth": 1,
"source": "registry",
"dependencies": {
"com.unity.burst": "1.6.6",
"com.unity.nuget.mono-cecil": "1.11.4",
"com.unity.test-framework": "1.1.31"
},
"url": "https://packages.unity.com"
},
"com.unity.entities": {
"version": "0.51.1-preview.21",
"depth": 0,
"source": "registry",
"dependencies": {
"com.unity.burst": "1.6.6",
"com.unity.properties": "1.7.0-preview",
"com.unity.properties.ui": "1.7.0-preview",
"com.unity.serialization": "1.7.0-preview.1",
"com.unity.collections": "1.4.0",
"com.unity.jobs": "0.70.0-preview.7",
"com.unity.mathematics": "1.2.6",
"com.unity.modules.assetbundle": "1.0.0",
"com.unity.modules.unitywebrequest": "1.0.0",
"com.unity.test-framework.performance": "2.8.0-preview",
"com.unity.nuget.mono-cecil": "1.10.1",
"com.unity.scriptablebuildpipeline": "1.19.2",
"com.unity.platforms": "0.51.1-preview.21",
"com.unity.roslyn": "0.2.2-preview",
"com.unity.profiling.core": "1.0.0"
},
"url": "https://packages.unity.com"
},
....
}
If that is a recursive issue, it may require reporting a bug, as old entities still should be present.
Please someone correct me, who has 2021.3.6+, if their manifest file structure is different (I have removed some stuff, to make it shorter). I am curious on the structure change.
As @DreamingImLatios mentioned, you need load experimental packages in Package Manager, to see entities.
Best if you follow strict upgrade guide to entities 0.51, if you haven’t yet.
One more things.
You upgrading from which version of Unity to 2021.3.10f1? Is that from 2021.3.5f1?
You should address that separately in designated sub forum. Otherwise, it clutters DOTS sub forum.
Such message here won’t reach to the relevant Unity devs.
We can assist you here only on DOTS side matter.
2 Likes
You’re looking at packages-lock.json. That’s different from manifest.json. In any event, that manifest shows Hybrid Renderer. The presence of Hybrid Renderer implies that Entities gets pulled in as a dependency, so that’s not an issue.
1 Like
Thx for pointing out, I made relevant amendment to my reply above.
assetbundles are not deprecated, in fact, addressables builds on top of the asset bundles.
I know of no such deprecation. AssetBundle is the foundation of Addressables so it’s still there. Resources is still a thing too and no Resources API has been marked with [Obsolete] attribute. So I suggest you read Unity documentation more carefully.
It is well known by many in the industry that Unity went beyond discouraging resources folder and is depreciating it. The news of asset bundles being flowed into addressables only is a thing too. You never want to get caught in a dead tech, so you need to follow trends.
I don’t have the forum/discord talk of professionals to quickly informinate you so I’ll drop you an older forum post: https://discussions.unity.com/t/602931
Yes. I tried going from 2021.3.5f1 to 2021.3.6f1, and after 10 hours I couldn’t get it to work and reverted.
Normally I just wait for higher versions and the bug resolves itself.
I waited for .7, and that failed and took 4 hours off my day (I predicted it probably not working so I didn’t commit to it much)
I waited for .8 and that failed and took only 2 hours off my day (super ready for it to fail, so I just forked my project to work on it while it tried to update)
I think I didn’t notice if .9 came out.
So I came to .10 and it straight gives me like 1000+ errors because it deletes all my packages for some reason. This is why I came for help. Normally I just wait a few versions for UNITY to iron the bugs out of the editor, but it’s getting worse instead of better this iteration.
I do not understand what you mean? Addressables bundles the assets into AssetBundles. That’s how it works from the start.
You got it broski! Thanks for helpin. Give me about 30-60 min while I try and update/edit this post again. And then I’ll edit this post with my current manifest. If Unity users like myself need to know this technical knowledge to upgrade their Unity Editor IDE, I’m down with it. I love love love Unity. It’s an awesome product and you get awesome stuff done in it. It’s worth investing in UNITY if you’re a top talent developer as other game engines are designed just for script kiddies. UNITY gives a talented developer the ability to do just about anything. So it is worth learning things like manifest files, .meta files and other technical details that maybe you don’t have to learn with other IDEs who just compile and go. I’m down for this learning process of the guts as we go. Maybe you guys can learn some stuff I know too like off meta usage, UI design for functionality improvements, foundational architecture and bugs you might not be aware of or how to fix em. I’m developing for the long haul of decades.
The consensus on the forums was not to use Resources folder anymore(I used to use that), and not use another similar “load from disk on the fly tech” which I hand waved as asset bundles. If asset bundles are only accessible by Addressables, then they’re just a subset of Addressables and that doesn’t detract from the point that Addressables in many people’s minds is necessary and no longer just experimental.
Lots of tech companies never tell you directly what they’ll depreciate for it messes with the market for various reasons. That is an acceptable business practice in my book though some don’t like it. Look at WCF for Windows, it’s fairly dead for many many years, and Microsoft didn’t give any heads up about it. Then you have stuff like Adobe Flash that they depreciate so hard, other tech related gets collaterally destroyed as well such as Adobe Air. It’s very important to stay alert to the tech talk of actual users and semi insiders on these matters. Because of this, you cannot limit yourself to company’s documentation and declaration of intent.
Finally, this is totally side tracking the conversation of me asking for help upgrading my editor. Addressables only came up in discussion because I lost hundreds of hours in the bugs trying to get it to work. If you want to talk about addressables, what bugs exist today, how to fix said bugs, what user interface errors are marring functionality for new users and such, open a new thread. I do not want to talk about addressables in this thread anymore since some people are forcing my help thread into a rabbit hole by low key demanding responses. Please just make a new thread and post the link in a reply. I will avoid replying to any more addressables concerns here. This thread is only meant to be about bugs with upgrading the UNITY Editor and how you cannot even get the Entities package anymore in .10.