Originally Posted by Soggy_Popcorn
Oh, please OP. Epic freaking Mickey does not have performance issues because it has the graphical quality of a game from 2005. And Lego Universe? Oh yeah, real taxing visuals there.
What do taxing visuals have to do with crashing and bugs? Not all crashes or bugs are related to taxing visuals. The only crashes you see in this area are due to things like incompatible GPUs trying to use certain shader techniques, or bugs where available memory is low. These are things that can occur when taxing a machine during a game, but are things that can be managed by developers, regardless of the engine, and are not unique to Gamebryo.
I didn't say Gamebryo was still an epic game engine, I just said that bugs you see in Bethesda's games are unrelated to Gamebryo.
Originally Posted by TestECull
Every problem I have ever had with Fallout 3 and/or Fallout: New Vegas can be squarely pinned on the engine. Instability, horrible animations, ram-rod stiff dialog, AI that enjoys staring at walls instead of guarding valuables, general pathfinding issues, graphics that would make 2004 blush with shame, the innate inability to load the world properly on anything less than an SSD, inability to load the world at all sometimes, dodgy collisions, spazzy ragdolls, all things the game engine is responsible for.
I'm eagerly awaiting buglists for Skyrim, because that's going to be the engine under Fallout 4.
Rigid animations cannot be Gamebryo, other Gamebryo games do not suffer those problems. AI issues, of ANY kind, are completely unrelated to Gamebryo, as Gamebryo is not an AI engine. Dodgy collisions, again, Gamebryo is not a physics engine, so that is not Gamebryo. Ragdolls, more physics, not Gamebryo. Instability, not Gamebryo, other games using it have very few crashes or instability of any kind. Stiff dialog? Do you mean like the facial animations? If so, they use a seperate program for generating those animations, not Gamebryo.
I've said this kind of thing on multiple threads, and I don't know how I can be much more clear: I'm a professional game developer, I'm currently working on a shipped title that uses Gamebryo, Gamebryo is not responsible for most bugs or animations problems, and is absolutely not related to any game logic, physics/collisions issues, or AI issues that you've ever seen. Long story short, most of the issues you've seen with Bethesda's products are simply Bethesda's problem, not Gamebryo. That being said, it is possible they had trouble with integrating many of their features/tools/etc with Gamebryo, and that affected the overall quality of the game.Edited by lordikon - 12/27/10 at 6:25pm