{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/25/2023 10:10:52 PM
11
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?
English
-
The engine does have a lot of issues - and has since the game released. Notably DPS and other things being tied to frame rates. Gravity lifts were killing people because that was tied to frame rate 😂 But changing engines is not feasible
-
Yes it is the engine, it is severely outdated and is difficult to properly patch and work with. A little more detail into why the tiger engine is so bad we need to know that the current version of the tiger engine is actually a modification to the the tiger engine, an offshoot of the original tiger engine that was used for halo reach, and the tiger engine is actually a heavily modified version of the blam engine. The tiger engine is notorious for its inability to properly pack and unpack data properly leading to massively over bloated code leading to issues with file size and performance thus why d2 is such a massive file. The older engine is often referred to by its spaghetti coding and how difficult it is for new code to be added to the already older code being such a mess. The tiger engine was fine to use for d1 as it was a new game and concept and money could be saved if the project wasn't successful. But the engine should have been swapped out for the sequel and doing so would have solved a ton of issues we see now with the game breaking every single time a new patch is introduced.
-
Hell they could've done a reborn after the -blam!- show that was D2 vanilla, but all they've done is paint themselves in a corner now.
-
Edited by bbbhurricane: 1/26/2023 3:46:57 AMNot really since to do that they would have had to completely take the game offline for easily a year or two to recreate all the assets and coding in a new game engine. Pretty much the moment you start developing a game in an engine you are locked into you using that engine unless you scrap all your progress and start back at zero. Thats why when you start a franchise you typically use a previously used engine you've always had because it's the safe and cheap option but when you start going into sequential games you switch and upgrade to newer and better engines to keep up with advancing technology.
-
Why take it offline to develop a new engine tho? Why not develop it stand alone from the game as it is? It's not like it haven't been done before? Like in FF online?
-
Realistically yeah, not saying everyone would welcome it but could've been an option. Right about the build, but only to the point of TTK. Did they say it would be a year or two to do during that time or was it recently said?
-
That time frame was more of like an educated guess for how long it would take for them to do it, it wasn't an exact number just an approximation .
-
When was it said?
-
They never said anything about a timeframe the number I said was simply an educated guess for how long it would take them to switch game engines and take d2 completely offline to do so
-
Ok umm am I explaining this wrong, like the date it was said( 18jun18 ) not the time period( 1-3 years ) to get it done.
-
This is something I'd really appreciate too. I have only a little base knowledge and am no authority on this, like the vast majority of us, but I'd like to see a 3rd party with the knowledge base talk about this game engine and its technological capabilities, limitations, and issues in detail, because personally, I don't trust Bungie to be honest, or even know what they're talking about here given the dismal state of this game.
