Multiple messages about base change (GWX 3.0 Gold)

[Crunch Troll]

Originally Posted by danlisa

Hi.

Yes, this Bug was caught in GWX 2.1, however, that was for Memel/Kiel.

The cause of this were the flotilla entry\exit dates for the 2 ports in question being in conflict with each other, thus putting SH3 in a loop.

That is what I figured based on the threads I read from GWX 2.1 and since I could find no threads for GWX 3.0.

In your instance it sounds like a conflict between Konigs & Kiel however, as you are the first to report this issue with GWX Gold, I must assume a file conflict with an enabled mod, corrupt file or an unchanged line in the Alternate Flotillas mod.

Again, that is what I figured.

Believe me, when this happened in GWX 2.1, these forums were spammed with the issue.

Knowing gamers, I think that is a bit of an understatement of what happened.

To correct the issue, firstly I would suggest an examination of the flottila.cfg of the base GWX version & Flotilla mod (& campaign_LND.mis - not sure about this one) version. See if any of the dates differ for the ports in question.

I do not write code for anything (even though I do computer technical support) but in my limited knowledge I should be able to view the code using something as simple as Notepad.

Secondly, a MD5 check of your GWX install files. Just to be safe.

Did that when I downloaded the files but used the md5 text file included. Heck I even read the installation instructions before I downloaded the expansion. But I should check using the md5 values on the GWX page.

Lastly, SH3's message system is rather odd. A 'rollback' to a previous save or disabling a MOD usually will not prevent SH3 spamming you with the same info. You get the same occurance when you receive the 'Your base has been changed to X' popup. Perhaps a test would be to create a new career near the same date and see if they re-occur.

That is a thought. I have another career going (started in the 2nd where I transferred to for my primary career. Go figure.) But do have a generic, unused 'Player' setup (for another SH3 issue) I could use as a test.