• GhostlyPixel@lemmy.worldM
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 month ago

    The UE5 move had been telegraphed for a while from job postings, but I didn’t expect the rebrand.

    Feeling cautiously optimistic, but I still think they have the major hurdle of working with Microsoft’s contractor policies.

    • ShadowCat@lemmy.worldOP
      link
      fedilink
      arrow-up
      6
      ·
      1 month ago

      Yeah, was all but confirmed till now. But as you say the rebrand was unexpected.

      I still think the contractors is bad but at least they’ll be working on a familiar engine instead of having to learn a brand new one for the first however many weeks/months

      • Blxter@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        1 month ago

        I feel like the switching of engines is ‘treating the problem’ of hiring contractors instead of fixing the problem and keeping there engine. If they just kept there workers I really do believe it would be better in the long run. How is it that Xbox/Microsoft cant keep an in house team for one of there biggest IP to have a engine for it? I knew the switch was coming from leaks but I actually didn’t want it to be true.