EVGA

Is it time for BioWare to give up on the Frostbite engine?

Author
rjohnson11
EVGA Forum Moderator
  • Total Posts : 102291
  • Reward points : 0
  • Joined: 2004/10/05 12:44:35
  • Location: Netherlands
  • Status: offline
  • Ribbons : 84
2019/04/03 05:17:18 (permalink)
https://www.kitguru.net/gaming/matthew-wilson/is-it-time-for-bioware-to-give-up-on-the-frostbite-engine/
 
Kotaku’s Jason Schreier has reported on the behind-the-scenes issues that plagued Dragon Age Inquisition and Mass Effect Andromeda. Last night, he dropped another bomb, this time detailing Anthem’s troubled development, complete with accounts from 19 developers that worked on the game.
 
Why were so many of the original ideas scrapped? Well, a lot of that does come down to the Frostbite engine. One developer told Kotaku that “Frostbite is full of razor blades”, while another said that the engine is “poorly documented” and “hacked together”. Another BioWare developer gave a bit more explanation: “Part of the trouble was you could do enough in the engine to hack it to show what was possible, but then to get the investment behind it to get it actually done took a lot longer, and in some cases you’d run into a brick wall. Then you’d realise, ‘Oh my god, we can do this only if we reinvent the wheel, which is going to take too long.’ It was sometimes difficult to know when to cut and run.”
 
It is worth noting that the Kotaku report showcases many other problems that plagued Anthem’s development. From a lack of vision or direction, leadership not dealing with critical issues, lack of resources, poor communication and a blind faith in ‘BioWare Magic’- a term used by the studio to describe the later parts of development where the puzzle pieces miraculously fit together.
 
I agree with the developers. Either remake the engine or dump it. 

AMD Ryzen 9 7950X,  Corsair Mp700 Pro M.2, 64GB Corsair Dominator Titanium DDR5  X670E Steel Legend, MSI RTX 4090 Associate Code: H5U80QBH6BH0AXF. I am NOT an employee of EVGA

#1

3 Replies Related Threads

    cneuhauser
    FTW Member
    • Total Posts : 1334
    • Reward points : 0
    • Joined: 2007/12/18 12:49:31
    • Status: offline
    • Ribbons : 5
    Re: Is it time for BioWare to give up on the Frostbite engine? 2019/04/03 07:24:41 (permalink)
    BioWare is losing ground quickly with many recent mistakes...sad really.

    Entho Evolv Anthracite Grey
    ASUS ROG E-Gaming X299
    i7 9800x 4.8ghz on water (Cuplex Vision block) 
    EVGA RTX 2080 XC Ultra / Water / EK Block
    GSkill Trident Z - 32gig
    2x Samsung 1TB SSD Evo
    Intel SSD 730 Series 240GB 
    Windows 10 Ultimate  
    EVGA 1600 SuperNova T2 
    Samsung G7 Faker 32" 240hz monitor
    Asus ROG Swift PG329Q 175hz monitor
    SteelSeries Arctis Pro+DAC
    B&W 801s, Driven by Sumo Amp via DAC
    #2
    aka_STEVE_b
    EGC Admin
    • Total Posts : 17692
    • Reward points : 0
    • Joined: 2006/02/26 06:45:46
    • Location: OH
    • Status: offline
    • Ribbons : 69
    Re: Is it time for BioWare to give up on the Frostbite engine? 2019/04/03 11:05:59 (permalink)
    DICE should be getting rid of Frostbite... or at least a complete overhaul.  The network code is trash in it and they haven't figured out to fix it for a long time now.

    AMD RYZEN 9 5900X  12-core cpu~ ASUS ROG Crosshair VIII Dark Hero ~ EVGA RTX 3080 Ti FTW3~ G.SKILL Trident Z NEO 32GB DDR4-3600 ~ Phanteks Eclipse P400s red case ~ EVGA SuperNOVA 1000 G+ PSU ~ Intel 660p M.2 drive~ Crucial MX300 275 GB SSD ~WD 2TB SSD ~CORSAIR H115i RGB Pro XT 280mm cooler ~ CORSAIR Dark Core RGB Pro mouse ~ CORSAIR K68 Mech keyboard ~ HGST 4TB Hd.~ AOC AGON 32" monitor 1440p @ 144Hz ~ Win 10 x64
    #3
    fergusonll
    FTW Member
    • Total Posts : 1686
    • Reward points : 0
    • Joined: 2013/02/21 09:49:10
    • Status: offline
    • Ribbons : 3
    Re: Is it time for BioWare to give up on the Frostbite engine? 2019/04/03 21:20:55 (permalink)
    Didn't EA play a part in these developers having to use Frostbite, maybe they need to keep their hands out of developing the games.
    #4
    Jump to:
  • Back to Mobile