I still think the lasers look too much like flaming arrows.
Printable View
I still think the lasers look too much like flaming arrows.
The new cartoonish dark model sux,the old was much better(same goes for the Thor),And currently the attack animation is both good and cool,firing non-stop volleys of plasma projectiles ,But that's for the animation,the usefullness of the unit is for a different topic ;)
Hiding. Under a rock. With my fingers in my ears and eyes staring at the ground.Quote:
Wow were have you been????
The removal of the customizable Battlecruisers depresses me greatly; that was one of the things I was looking forward to, greater customization of forces to fit a given situation. And it looked as though they had put a great deal of thought and effort into it, only to remove it come Beta. ._.
I actually happen to like the new battle cruiser better then the old one. Of course, you have to realize, that the SC1 BC and the SC2 BC are two entirely different BCs (the Behemoth in SC1 and the Minotaur in SC2)
Granted, it doesn't look that great in screen shots, but once you actually see it in action, it looks a whole lot better. You can fully appreciate the neck portion where it shows the Yamato cannon and sparks coming through the infrastructure, it kinda gives a sense that the Minotaur is a huge flying cannon ready to blow stuff up.
Now that being said, I find the rearward bridge structure a little awkward looking, and I hope that Blizzard will put in the effort to create a custom Behemoth model for the Hyperion, as it is right now just a regular looking Minotaur (which it is not.)
The BC in SC1 did look a little sleeker IMO, but I don't really hate the look of the SC2 BC either. It's a shame it lost its extra upgrades though.
Sleek, yes that's a word that Samwise has forgotten completely in SC2.
Nothing looks sleek in this game what so ever. Vulture was sleek, Wraith was sleek... too bad Vulture now looks bloated, Wraith now looks stubby and BC is now a plush toy.
They really just need to redo its attack animation to make it look like it's not shooting fireballs at things.
I have no idea how they look; nobody builds them.
I once commented on the aesthetic changes to the battlecruiser, back when people were still more concerned about sapping the color out of everything than fixing the fundamental design flaws in the models.
As others have commented, the original BC design was sleek and predatory; it conveyed a sense of scale, despite its (relatively) small sprite size. All of the defining details were small, which therefore gave the craft an inherent sense of largeness. This is the law of conservation of detail at work.
The raised bridge; the enormous, bulky gun turrets; the unnecessary "fins" on the nacelles. All of these are added details to the new model that serve to make the Battlecruiser look smaller than it really is. I even once photoshopped together a few 'before and after' pictures once to display just how they affected the perception of the model. These details could be compensated for, if the unit was enlarged to scale to the new details better (specifically, if the neck was elongated it'd look less toy-like). However, the far more economic option would be to reduce (or even remove) the unnecessary details in their entirety.
A Short-List of Changes:
• Lose the Raised Bridge. It has never been cool, and never will be.
• Shrink the fins so they're less prominent.
• Go for a more utilitarian turret design. Ball turrets look clumsy; employ something more 'flat' and/or angular.
• Reduce turret size to between 2/3 or 1/2 their current size.
• Improve turret placement to something moderately sane.
• Flatten the "nose" of the Battlecruiser model to be flush with the hammerhead, or very nearly so.
• Don't exaggerate the animations: disproportionately subtle animations imply mass. Its a big object; let it act like it.
Anyway, since we know that Blizzard isn't going to fix this by this late in development, lets just hope that some bored modder comes up with a third-party graphical update that takes this sort of thing into consideration. ;)