RickySpanish, on 09 May 2018 - 10:10 AM, said:
Memory leaks are not good, they are atrocious.
Furthermore, HBS used Unity of all things to develop this game which may have led to a faster development time, but is also the root cause of every major reported bug.
Long load times? You have Unity's craptacular asset management to thank for that - just check out the "Unity standard" file structure in your Bt install folder, and wheep.
Multitudes of loading screens, plus having to load the "mission start" screen before loading your actual saved battle, plus the main thread blocking when loading? That's Unity's amazing scene based game design system right there.
Bugs with not being able to hunt down all reinforcements / targets? I wonder if those units didn't fall out of the world?
Don't get me wrong, I love BT, but as a game developer who has had (and continues to have) the misfortune of using Unity, it's pretty clear that it was in many ways, a poor choice for engine.
FYi in case it hasn't been mentioned, dropping texture detail and turning of cloud saves speeds loading up a tad, as does removing old save games - I'd love to blame Unity for taking its time to populate the saved game list, but that's probably all on whatever muppet decided to parse every save file to validate it instead of just the header...
again, sarcasm.
also, not that im a fan of rent an engine development. its always used as an excuse not to have a few good programmers on staff, and the inability to fix problems is the result. this is a problem with the dev team, not the engine.
unity doesn't have these problems in other games. you have to throw a pile of mods at kerbal space program to get it to crash. granted ksp is a mature title and had a great dev team (hbs are noobs in comparison). unity games have been pretty stable for me (a lot more stable than cryengine for sure).
Edited by LordNothing, 09 May 2018 - 04:59 PM.
























