• Vik@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    2 months ago

    It means a couple things I guess.

    It’ll probably still run bad thanks to associated technologies like nanite (see relevant threat interactive video).

    They’re not longer constrained by the technical debt of blam engine.

      • MrScottyTay@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        I think the MCC was unreal was it not? It’s likely it’ll be that team working on the next game and why unreal has been chosen

        • Vik@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 months ago

          The ‘wrapper’ around each of the individual halo engines is in unreal and is arguably the wost thing about the collection from a reliability standpoint.

          That said, they’d definitely be able to find people suited for the work, provided said people agent already scared away by stories of the work culture at 343i / MS

            • Vik@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              2 months ago

              naw unfortunately not. It’s kind of crazy that they nestle each individual engine within a wrapper. I’m not sure of this brings the api level to d3d11, or if they had to work to bring each engine up for that. Somewhat explains why MCC as a whole was so difficult to back port improvements to, like configurable FOV and weapon model placements, frame rate unlocking and interpolation, custom keybinds, missing assets and such.

              it’s kind of interesting seeing the player models rendered in UE when you use the customisation menus; everything looks so glossy and odd.