3. Sometimes this is enough. I think it depends on the map size tbh.

No, like stated earlier just moving your pointer over a Black Hole causes the game to sputter and stick.

Not being able to effectively use auto save without the worry of crashes or 8 minute+ lags isnt "working as intended"

Also I have used Large Galaxies and its happening. My rig is an i5 6600k @ 3.5 GHz, 4 cores,32 gigs of ram and a Gforce GTX 1070.

This set up should have NO problems running Large Galaxies.

The problem remains with my Lap top which is a Predator i7 4 core with a 1080 and 16 gigs.

This problem didnt start happening until the Intrigue DLC I believe. 

I did a complete uninstall and re-install as well.

One oddity is I keep getting "4 Files failed to validate and will be reacquired" when I validate the files. Weather its from the old or new install.

Thats the cache files been reaquired and nothing to worry about.

Blackhole issue is a whole different ball game, and I do think it is linked into the UI lag and Stuttery pathfinding.

This is a true problem.

As per this post: https://forums.stardock.com/493605/page/1/#3741547

Here are two files produced yesterday by GC3/Crusade in a medium galaxy with default settings, PC, Steam, latest version 3.4.

https://www.dropbox.com/s/zixgciblngcyi5k/loadtime_shenanigans.rar?dl=0

And here's the DXDiag:

https://www.dropbox.com/sh/tcf3jcv0zvsklvb/AACwdVgyvQxebhAf3JC7z9GJa?dl=0

(And before anybody asks, the swap file is under Windows 10s control which sets it to 16 GBMB, same size as my physical memory, and Steam cloud synchronization is disabled.)

Altairian_initial: Turn 1: Compressed size 8 MB, uncompressed 140 MB.

s2: Turn 18. Compressed size 33 MB, uncompressed 2500 MB.... an increase of 1686%.

s2 was produced by saving and reloading a lot during gameplay without exiting to desktop during play.

The excruciatingly slow loading I saw reproducible yesterday in 3.4 is 100% reproducible in 3.5 today with the 3.4 save files on my system. To reproduce:

1. Start the game from the desktop
2. Load the game s2. On my setup with a hard disk drive rather than solid state drive, that takes between 70 and 90s (differed between the 3 tests)
3. Within the game, click load, select game s2 and confirm that you'll abandon the current game. On my setup this takes 10 minutes+
4. Exit to desktop
5. If duplication tests needed goto 1
6. Start the game from the desktop
7. Load the game s2. Again 70-90s for me
8. Exit to menu
9. Load the game s2. 10+ minutes, no noticeable difference from attempting to load within the game
10. Exit to desktop
11. If duplication tests needed goto 6

I think it is safe to say that regardless of whether the loading time and save file bloating are related or not, there is something terribly wrong in (I presume) the dispose/load code in 3.5 (and 3.4) when loading the same save file will take radically longer to load the second time from within the game than the first. Sounds like a problem with cleaning or disposal, but you guys are the ones with the code, so you tell me.

(I know you guys would prefer save files created in 3.5, but honestly, at this point I can't be arsed. Since I started playing yesterday, I've spent considerably more time trying to track down your bugs and being annoyed by slow loading than playing the game, so you'll just have to make do with this as I return to other games, because GalCiv 3 certainly isn't worth playing for me in the current state.)

Hello Peter,

Why are you manually setting your swap size and not letting Windows dynamically manage it?  Have you done any tests where that was the case - where Windows itself manages the size?

-----------

Sean Drohan
Stardock Support Manager

We found the problem for gigantic save games and are working on a fix.  

I do not manually set the swap size. I explicitly state that it is under Windows control. I DID mistype MB for GB, as the size assigned by Windows is 16 GB, not 16 MB, which may be the cause of your confusion. (In which case you might also rightfully be wondering how I could play GalCiv3 on a computer with 16 MB RAM, as I stated the swap size was the same as my RAM size. )

Thank you for the clarification - what was confusing me was a value mentioned at all.  More commonly it is mentioned that 'Paging / Virtual Memory is automatically managed' without an explicit value mentioned.

Perhaps I was reading too fast in any event.

Again, thank you for the clarification.

-----------
Sean Drohan
Stardock Support Manager

Quoting Hosttage, reply 61

Hosttage

 

Join Date 11/2008

 

0

 

 

Reply #20 February 26, 2019 12:08:25 PM 

from Galactic Civilizations III Forums

 

Hi Paul, the loading and saving bug is gone with the wind.  No more problems.

End of Hosttage's quote

Glad to hear it.

~Patrick