Page 1 of 1

Possible Bugs in 1.7.0.16

Posted: Sun Jul 22, 2012 1:31 pm
by vengen
I've noticed a few things that may be bugs in 1.7.0.16 (but I've played so infrequently in the last two years that they may be things that I've somehow messed up in my settings):

1 - Started a game as Wekkarus and the default escorts were the size of frigates, the default frigates were the size of destroyers, and the default destroyers were so large that I could not even build them.

2 - My next door neighbor Hakonish kept removing its trade embargo, then immediately re-imposing it. Both messages appear at the same time - the removal above the re-imposition. This stopped once I built a bunch more warships.

3 - I can't build them yet, but I have a bunch of non-obselete designs for Cruisers and Battleships in my design screen.

4 - This has been happening since at least 1.7.0.12, but sometimes I get the same exotic resource on two different planets - it's usually Zentenaba Fluid. Is that WAD or a bug?

I'm not seeing anyone else post bugs, so I'm thinking that this is probably an issue with my machine, a corrupt install, or I've messed up my settings?


RE: Possible Bugs in 1.7.0.16

Posted: Mon Jul 23, 2012 11:18 pm
by Dracus
number 3 has always been there, the auto design will create plans for every ship type even if you can not build them yet.

RE: Possible Bugs in 1.7.0.16

Posted: Wed Jul 25, 2012 6:20 am
by feelotraveller
Number 4 has always happened, at least on bigger maps.  I regularly encounter more than one source of each exotic resource on the largest map.  Though they could have tweaked the thresholds in recent patches?

RE: Possible Bugs in 1.7.0.16

Posted: Wed Jul 25, 2012 10:28 am
by WoodMan
Yes number 3 and 4 aren't bugs they are WAD.

RE: Possible Bugs in 1.7.0.16

Posted: Wed Jul 25, 2012 7:15 pm
by vengen
My issue with #3 is that the old designs are not getting obsoleted, so I end up with 15 or 20 crusiser and battleship designs being displayed as avaialble for construction.

However, since no one else is reporting any problems like mine, it's probably something specific to my situation. I'm side tracked onto something else right now, but when I get a chance I'll re-install and patch directly to 1.7.0.16 and see if #1, 2, and 3 go away.