Dont they fucking own IDTech?
this post was submitted on 12 Oct 2024
192 points (98.5% liked)
Games
16536 readers
1006 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
I'm gonna assume that this is because they are Microsoft now. They use a ton contractors on everything these days instead of actual employees but the catch is contractor can only stay there for 18 months and then have to leave or get hired so any experience on the project gets thrown away. Moving to unreal allows them to bring on a wider group of dev contractors so hopefully the ramp up isn't as long. This is just a theory but the same thing happened to Halo since that's moving to unreal to. If they just retained actual talent this wouldn't be a problem and the games wouldnt suck as much even if engine was less advanced.
I hope they don't go with unreal, the level of broken-ness of every game on UE5 really worries me
I don't know anything about UE5, but many game developers seem to be putting out unfinished shit right now. I have to wonder if it's the engine or just the studios.
I mean they already own the Quake engine, or ID Tech 8 or whatever, just do it on that.
I know it would have the same issues as the Unreal Engine - all the training, engine building, and systems integration it'd take to get a game released, but I think it'd be cool if Bethesda were to make an Elder Scrolls game on their ID Tech engine. That codebase is pretty celebrated.
If I can't put a skull in a basket and balance it on a cheese wheel, then trick an NPC to walk on it, thus yeeting them into the stratosphere, is it even really a Bethesda game?
Watch Bethesda miraculously over performs the unfathomable hype around next elder scrolls game. Puts out what is unanimously considered the perfect performing and engineered video game that all peoples of the internet love. Give it one week after creation kit is released for it and someone will have made a mod that injects all the old physics bugs/features into the perfect game and will be the #1 downloaded mod for the rest of its existence 🤣
Not another one, unreal is so bad for mods, please just overhaul your own engine, take the time, another year for Fallout 5 is nothing.
It's cute that you think changing engine weight only add one year to a project
Do you think Total War will need 2 years to fix their engine then? They are also doing that after it finally caught up with them in Pharaoh.
Fallout 5? We already had two fallout games since the last TES game. Drag wants TES!
fallout 5 is most likely gonna be todd howard's last game ever. it wont come until after TES 6
And gain new tech debt in the process!
Tech debt accumulates over time. Starting fresh is the opposite of that
Unreal Engine was released in 1998, Creation Engine is derived from Gamebryo which was released in 1997.
They'reTheSamePicture.jpg
JFC UE5 is not the same tech. It has had major changes over the years. Gambryo is in no way a modern engine. I have used both of these technologies. Have you?
Starting fresh also leaves you with nothing
Chances are, you start fresh, start copying/ adapting existing code. Leaving you with much the same issues as you were trying to get away from
There's no way Unreal is completely free of inherent tech debt. But at the same time, there's no way it doesn't have way less baggage than the creation engine. Epic actually work on it, for a start.
Their tech debt for the most part isn't going to be because of the engine. Certainly some of it is. But starting back over and reimagining most of the code base affords them the time and ability to fix problems that make features problematic. As the spiffing Brit likes to point out every one of their titles is absolutely riddled with game breaking bugs. Doing an engine change has the kind of depth required to let them head those kind of problems off before they happen.
Of course with an entire staff of short timers they'll quickly just a mess new tech debt as they misgauge things.
I would have absolutely zero interest in an Unreal Elder Scrolls or Fallout game.
There's already hundreds, maybe thousands of indie games trying to be that very thing available on steam today and they all suck.
This indie games are also made by amateurs without the ability to make something with the breadth and scope of an actual Elder Scrolls game. They're not bad because the tech sucks; they're bad because they're not well designed in the first place.
Check out The Outer Worlds for a competently made game of similar scope and mechanics that's also on Unreal and doesn't suck.
The Outer Worlds is a good and fun game, for one fast and very linear playthrough with a great storytelling. But it has no replayability and it has zero possibilities for modding. It is not in the same league as Skyrim or Fallout, not even Starfield.
outer worlds would have been amazing on creation engine.
i remember hearing the devs for the darling 10/10 game fallout new vegas said that the creation engine was by far their favorite to work with
If CEOs only knew how much time and money they lose to tech debt, they would dedicate their careers to fighting it.
Long-term tech debt is also really just part of the problem, the same thing occurs in shorter time intervals too when you e.g. push fixing a bug from the time before release to the time after or even just from the time when one developer is working on that particular feature to after the time when it is merged into the shared code base.
That sounds like a problem for next year's CEO.
view more: next ›