Indeed. A lot of the canon inconsistencies could also be culled from the list, as they're either pointless or not beefy enough to provoke a Cryptic response.
Thanks for the input jes. ^.^ I've given a lot of the canon inconsistencies the chop, leaving only the big iconic hero ships like the Constitutions, Galaxy, Intrepid, Defiant and Sovereign (and Akira, cause it's awesome. :3 )
Has anyone bothered to poke Logan about the new skin for the Intrepids being horribroke when combining the old pylons with it? I mean, 'holy carp on a dorf, that's broke' bad.
The damned thing's been fixed already on F2P tribble. So I don't believe CapnLogan is the issue.
It's Cryptic including the existing fix in a patch to holodeck, which I believe is someone else entirely.
CapnLogan may be able to pass the message on to the appropriate party, but I wanted to make the distinction that I believe he's already done the work to fix it.
It really burns my muffins that this fix, (which has been on tribble for a couple of weeks already, never made it to the holodeck, where we actually had to pay real money to play with it!
thanks for the video. That is 1 accurate Galaxy. I really wish all of STO's ships were that good... seriously. Just compare the 2 ships, the difference is clear. that 1 on u tube seems much more finely-crafted. I also think the starbase looks a bit more like the ones in the series/movies.
Oh well, perhaps someday STO will get the ship models fixed. It can't be that hard, I mean, cheap games that don't get monthly $ seem to be able to do it. (star trek legacy, for 1. pretty accurate 3D models there)
Is this the right thread to post about ship hardpoint issues?
I have a Venture-X-class equipped with heavy cannons and dual beams that both fire from the furthest most port and starboard sides of the saucer section, even though the beams should be firing from midway between the bridge and outer edge of the saucer and the cannons should be firing from the physical cannons near the mid section of the saucer near the bridge.
I haven't checked to see if this effects the Galaxy-X-class, does anyone know of this issue?