derpysquirtle64 said:
True. Call of Duty still uses lots of components from 20+ year-old Quake 2 engine. And it serves its purpose just fine. My point was that Slipspace is not really and "old engine" and it's not the main problem with it. The problem with Slipspace is that making game engine just for one game doesn't work in today's world. Microsoft should either invested in it not just for Halo but for other games as well or shouldn't have invested at all. |
It could also be a meh engine Tbf. It took Bungie two huge overhauls to update Blam! to something not trash. I mean, Infinite looks good and runs well but that's only half the story, we don't know how it is to work with but based on recent rumours, it's still a bit of a nightmare. I bet they were planning on doing deeper overhauls to it but time caught up to them and they've not done anywhere near as many updates as planned.
It's also a fucking nightmare with Microsoft's shitty contractor policy and having to hire people, then spend months teaching them about Slipspace, then losing them, is really counterproductive, whereas you switch to Unreal Engine and everyone in the industry knows that. Slipspace has often been pointed at as a large problem for 343 for various reasons, not because it's "old" but because it's still an archaic engine with little documentation and massively interrupts onboarding new hires.
They could have invested in it for other games but every Xbox studio now is on Unreal Engine pretty much, it's just a lot simpler and easier.







