Okay I have a video about 15 minutes of issues I've experienced in 1.7 I have put the info in support ticket #AQL-838-40681.  At this point it makes any larger existing game virtually unplayable in it's current state and I hope this points out some of it's flaws.  Overall I love this direction and believe there is a lot of good here and can't wait until all the bugs and kinks are worked out.  Good Work Stardock.

Few more things...

• Don't have all existing star bases have auto sponsors when loading old saved games.  This creates a big mess to attempt to figure out when loading old games, especially if one has many, many star bases.
• Because of the above happens, as soon as a new module is unlocked the game goes crazy with adding new constructors to the build ques of any and all ship yards even those that one doesn't really want to upgrade.
• The current process doesn't see any constructor as having more than one module, which was mentioned in the dev stream and I'm assuming will be worked out.
• Existing games don't get the little white lines showing which shipyards are sponsoring the star base.
• Game locks up/responds slowly after the above happens even though memory and cpu usage are not an issue.
• Video shows all of the above along with saved game on ticket #AQL-838-40681.
• Edit: Mentioned in dev stream, have the latest best (auto upgraded constructor be chosen by default), it's a pain to have to change this with every star base.

P.S.  I love the soundtrack just sayin'

Additional Points from second saved game from 1.61 (65 hour game)

• Turn time prior to 1.7 was about 2-3 minutes post 1.7 is approaching 40 minutes with no sign yet of the turn completing.  (will hopefully update time when it finally does complete, don't have time to continue to keep near the computer while it continues to do whatever it's doing, I'm assuming should I continue to leave it go it will eventually complete.)
• The fast constant sound of selecting ship/buildings present in my video I created in ticket is not present as a fast sound in this game.  Instead it's there as a sound about once every 10-20 seconds.
• Appears this causes turn time to go up drastically as something else is happening in the background with no apparent sign to performance.
• CPU sitting at 40-60%
• Memory sitting about 11 GB of 16 GB usage. (67% used) [This fell after about 13 minutes to only 9 GB usage]
• This game was a game that previously was unrecoverable crash in 1.61, started in 1.7 to see if it would continue.

Right now, the system sets all shipyards as sponsors by default when loading an old save game.  We didn't want you to have to select every starbase and assign a new shipyard.  We've also set the auto-upgrade as a default for both old and new games.  What are your thoughts on this?

We'll look into clarifying the auto/manual assignment of shipyard sponsors 

Can you give some more details on the research project and destroying buildings issues?

Here are my thoughts which I mentioned in the video part of the ticket...

• All existing star bases from previous saves should be set to manual and auto should not be selected.  (This way one doesn't get the huge amount of items being added to the que once one clicks turn for the first time after loading the game in 1.7.)
• The above causes anywhere from a few second delay on that first turn to hours, depending on how many shipyards are present in the previous game.
• Because of the above this allows the player to choose to add the existing star bases to que up constructors or just stand pat at what they currently are at without having to go through the massive list of existing star bases and changing their settings.
• Not to mention most existing star bases usually are left alone after a while unless one feels they need to upgrade it for any reason.
• When having all these ships added to the que either manually or automatically the next turn (or as you add multiple ships to the que over 50 star bases) the game starts to crawl horribly with huge delay's  (Towards the end of my video in my ticket it shows this response on the planet that I'm attempting to change the buildings on.)
• As far as making it more easy to understand the new system.  I think it's good now, some old players (existing to the game) which don't like to read and like to just click and go may over look different things.  Little popups over the shipyard sponsors (when they are grayed out because manual is not selected) stating need to select manual to be able to adjust shipyard sponsor would be nice.

Beyond that, should those two issues be fixed I think this is a huge step forward but, right now playing 1.7 on one of these games is nearly impossible.  Really the video clip I posted in my ticket shows all of this, it lasts about 15 minutes, however, the first couple minutes is just the game loading, beyond that between minutes 7:30 and 9:45 is where the auto upgrade is constantly adding ships into que, which is real annoying and in some games with even more star bases this period slows the game well beyond that.  In my other 1.61 game (that has an unrecoverable crash into the very next turn.) The game just sits on adding ship to que every 10-20 seconds and I was waiting yesterday for around an hour trying to get that turn to complete (either crashing or continuing) and was still in that loop.

Hope that answers your question.

I believe Seliore is gaming on a AMD machine.  The game is significantly slower on AMD CPUs.

Ashes is DX12 or Vulkan API, I believe.  Better/different optimization.

I have said it before, AMD has excellent CPUs, but most games aren't coded to use AMD performance improvement, so we have slower games, most of the time.  I went from a similar CPU to yours to an Intel i5 4670k, and I don't regret it for gaming.  However, everything else I do on my computer is very slow.

I sometimes play Galciv 3 on a A8-6600k APU.  It ain't very fast to begin with, I understand, but Galciv 3 is notably slower on turn change by mid game, once a good portion of the map is shown.  I have yet to try a game on this computer with the new starbase improvements.

do you have the same problem if you start a new game or only on loading the old one?

Well, maybe Stardock will figure out some general optimization for AMD that would help alleviate the problem you are experiencing.

I did something similar on my Intel gaming rig and had no problems, aside that multiple constructors got stacked on my starbases.

Can you PM me a link to your saved game?  I would like to try it and compare the turn time on my gaming machine.   I will post my results here so that Stardock has a comparison base, if they can not reproduce it on their end.

I had about 20 starbases, but not the 160+ starbases and 10 shipyards that you have in the sample game  With so many starbases, I am now seeing a delay on the first turn after upgrading.  The alternative is setting the starbases to manual and then folks who wanted the feature would have to set them to "auto-upgrade" and you'd still have to wait (it just would be spread out over time).  

That sounds like a better alternative, what about the delay after the fact, just general building/deleting buildings or changing build ques?  The video shows this toward the end?