{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Skandxr:
10/15/2019 8:32:33 AM
11
-
Or a 15 yr old game engine.... but 🤷🏻♂️
-
>when they built the engine from scratch in 2012-2013
-
😂😂😂 it’s from halo reach. Come on they “modified” it they didn’t rebuild shit. 😂😂😂😂😂😂😂😂😂
-
Me when you can literally watch a D1 vidoc that quotes exactly what I said
-
Edited by Mara’s dirty laundry: 10/17/2019 12:37:23 AMSure ya can. You when it was found later after the game came out that they were using a version of the halo reach engine 🤷🏻♂️ https://www.giantbomb.com/destiny-2/3030-52647/forums/destinys-engine-1810867/ Ouch
-
Yet that article provides no source for their statement, while the vidoc is straight from bungies mouth
-
Edited by Mara’s dirty laundry: 10/17/2019 12:50:24 AMAlright dude whatever as it talks completely about software engineering and the process involved tools used what programs they run. Fold your arms and stomp your feet somewhere else. I’ll wait for you to supply anything from a developer who has been caught “exaggerating the truth”.
-
Ah here it is. You propose it's simply the Blam engine but modded. "TIGER ENGINE • In mid 2008 we began the Tiger engine, after months of evaluation and tech planning • Built around new core principles - Multithreading, Cross-platform - Decouple engine functionality from game logic - Preserve all of the good features of the blam engine, and none of the bad! - Support all advanced tech we ever want to develop! • Many of these principles were theoretical goals D E S T I N Y V So after some months of evaluation and technology planning, we started the Tiger engine in mid 2008 . ** We'd identified some core principles that we wanted from our technology. - It needed to be pervasively multithreaded and cross-platform. - We wanted to divide the codebase into layers, so we could decouple the engine functionality from the game logic. ** We were also pretty idealistic. We wanted to preserve all of the good features of the blam engine, and none of the bad features! And we had all of these great ideas for advanced technology that the engine had to be able to support! ** A lot of these principles were just theoretical goals when we started, and they became a lot clearer over the course of development. 13 SPOILER ALERT GDC2015 • Destiny was a moon shot • It took longer than we expected - Some difficult times along the way • We ended up with some great technology - A new engine for the next 10 years - Cross-platform, cross-generation content - Very stable and performant shipping game - Tons and tons of future potential • It was a rocky journey ... but still worth it" So it WAS the the blam engine, until it was completely stripped down and rebuilt only keeping the good features. Even the guy in the GDC talk recognized it as a new engine. If it was simply the Blam engine and they added some extra stuff and fixed some things, yes, it would be the same, but this was a complete redesign. Your condescending, snobby attitude has been your downfall, begone.
-
Edited by Mara’s dirty laundry: 10/17/2019 9:34:49 AMSo as I said a modified version of the Halo reach engine. You can strip down and modify a corvette, but in the long run it’s still a [spoiler]corvette[/spoiler]
-
"he doesn't blindly trust an unverified source he's a fanboy" Classic modern mindset
-
Edited by Mara’s dirty laundry: 10/17/2019 1:43:47 AMStill waiting on that vidoc... You going to keep running your gob or produce this “clip”? I provided you software engineers take after dissecting the game with a full rundown of how the engine has changed yet here you are...... with nothing to show for it. Don’t worry I’ll remind you tomorrow, Incase you got tucked into bed early tonight 😉 http://www.gdcvault.com/play/1022106/Lessons-from-the-Core-Engine here’s another...
