this post was submitted on 06 Oct 2024
48 points (94.4% liked)

Halo

720 readers
1 users here now

Welcome, Reclaimer, to halo@lemmy.world !


Upcoming/Active Events:

* : Denotes a date based on leaks and, while likely, is subject to change.


Resources:

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] GhostlyPixel@lemmy.world 10 points 2 weeks ago (1 children)

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.world 6 points 2 weeks ago (1 children)

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 1 points 2 weeks 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.