No.27993
>>27992At the time of Fallout 3, it was probably fine, but it was outdated by the time NV was finished.
No.27994
Quest scripting doesn't have a good flow, which is pretty shit for making an rpg
No.27995
>>27994I wouldn’t really call any 3d fallout quest a quest. Maybe in 76 but the rest feel more like campaigns. Quests typically are one off stories or levels game design wise while in Bethesda titles they’re typically generally fleshed out with a lot of content which is why most quests in 3d fallout are packaged as dlcs and not quests like that one in new Vegas where you climb up black mountain to stop some weird looking nightkin from spreading propaganda. Or the other quest line in fo3 related to the lone wanderer and a bunch of cannibals underground
No.28018
Bethesda has been using the same engine more or less since Morrowind. It was already pretty much outdated for RPGs by then and now the cracks show big time with games like FO76.
No.28047
>>28018netimmerse 2 was their engine then and i think they upgraded the engine a lot since then so it is not really the same as gamebryo or whatever they were using for skyrim, its been upgraded many times
No.28050
>>28047They upgraded the graphics and animations I’ll give them that but the physics and ai is cartoonishly bad.
I think the physics will improve from starfield due to flight mechanics and new updates but the ai for me is expected to stay the same ignoring scripted encounters
No.28097
>>28075Honestly that’s just impressive to me. Really shows how much the team for 3 understood their own engine to pull off shit like that
No.28098
>>28075Why hat thought? Would it not be simpler to make train its own creature? Like changing model of dog to train.
No.28106
>>28098making a whole new creature would probably take longer than this