Which would mean a brand new game, and potentially worse problems. Just ask 343 Industries about Halo: Infinite and Slipstream…. The issue isn’t the engine right now. It’s that Bungie is trying to make too many changes too fast with too inexperienced of a dev team. We are four weeks away from a new expansion dropping, Stadia shutdown last week and we have no idea how that is impacting things, plus Bungie is making massive changes to the game. …and we’re caught in an in-between state right now.

That or we just have too much stuff in the game that needs to be removed like Dream city and DOE the previous content wasn't designed to stay in the game long term like this we basically slapping dlc on top of dlc creating more bugs and breaking things

Ppl think it’s so easy to transfer games to another engine 🤦‍♂️ and worst part is you think it would solve every problem.

[quote]Speaking from 23 years of professional experience as a systems engineer/SRE, without seeing how things work on the back-end, calling for a new engine is likely mildly premature. If I were to guess, bungie doesn't have (SRE|System Eng|DevOp)s (whatever you wanna call them these days) managing infrastructure and operations. Instead, they likely have developers doing it and traditionally, that's always been a horrible idea, because frankly, they really don't have a great track record for knowing how to run operational infrastructure. Writing a whole new engine is painstaking, takes a long time, and is error prone. Besides, why throw the baby out with the bath water. It's better to fix the bugs and enhance the current engine usually. I'm curious, how have you identified that the engine needs work? From a client side of things, I have never seen any significant issues with the game play. The network suuuuucks! That could likely use some work, but as I said, we have no idea how they're running their servers as far as I'm aware. My guess is that their back-end needs some optimization. I *think* they use AWS for their back end infra (based on region names I've seen). At any rate, my guess is that this is where they need help. If they're using kubernetes, then that could cause some additional question in terms of load balancing, ingresses, etc, in my estimation. A new engine would be like taking a hammer to an ant hill I think. I doubt much good can come of that right now if your goal was to still play d2 as it currently is in form. Also, data migration is extremely difficult to perform flawlessly and almost always runs into problems. I doubt db schemas are perfect (assuming they're used, which I'm guessing they are). Migration isn't impossible, but I almost promise you it would never be done. They'd just start over from scratch minus basic player data and if you start with a new engine, that's likely what you would do...at least I would.[/quote] Not me but it gives a very good explanation on why it's not the engine

Please tell me which steamer had mentioned the need for a new engine. It can't be coincidence you all think the game needs a new engine on the same day as each other. Also, please educate me, what exactly is the engine? How does it work? How will "upgrading"it help the game? I'm very keen to learn from you.

Did we forget about the Vulcan engine update with BL? I think its more spaghetti code. The best example of this was how the reveiled to us the sparrow Always On Time cant be fixed because it was made by Vicarious Visions and Highmoon Studios. Remember Bungie always reminds us how changing one thing can have massive effects. Think of destiny 2 as built ontop of the ancient ruins of a far more advanced civilization, what Bungie does now is scrap work and piece meal.

This is stupid. Switching engines isn’t like switching the batteries in a remote.

You're asking for a new game.

Is it the engine though? I’d love to have someone who actually has expertise with this chime in. Is it the overload on the engine? Do they have to vault more stuff? Is the engine too old? Is it the servers? Is it the way things are coded and put into the game? It needs to be addressed but what causes all the issues?

[quote]the fact bungie engineers spent 23 HOURS YESTERDAY working on the backend issues so huge respect to that.[/quote] I wouldn't say huge respect when it's their job and how come they don't see this coming and they need 23 hours to fix it. At this point I'm thinking maybe unity engine would do better

YouTuber makes video on a new engine being a possibility suddenly 100 people post the same opinion hours later 🐑

Do you have any idea how long and complicated it’ll be to migrate Destiny 2 from its current engine to a completely new one? I stg you kids think changing an engine is like installing new batteries into your TV remote. How about you go to your car or parents car and swap the engine with your neighbors car, see how simple it is then.

yeah, that 6 cylinders is way to old