Matrix Games Forums

Playing the latest beta, coming fury balanced (modified) scenario. Playing as union. I captured Nashville and a few turns later the rebs took it back, so I went back in and re-captured it. Nashville then elected to visit the Twilight Zone and has disappeared, causing great consternation amongst the troops who were lining up to pay their respects to the brothels. I have before and after saves in the case of the Great Disappearance of Nashville. All I need to know is how to get the info from my saves to this forum. Tried to zip it and it won't let me attach a zip file.

Send it to

ericbabe@west-civ.com

Zipped and small explantion plz.

Kind regards,

Rasmus

Thanks. Save sent.

Jeff Davis was heard muttering something about that dam@#d experiment at Oak Ridge. Said he told those people to conduct that test way out in New Mexico, NOT Nashville.

make sure you send both files, there are two parts to each save file
 
 

Right, did that. Four files total, two saves, one before and one after the disappearance. Hopefully a solution to this can be found as I have had it happen at least 4 times.

Nashville still disappears using 1.9.23 and the save files started under the latest beta. Is this now a "known issue"? It's bad enough losing a regular city, but the loss of a capital puts a crimp in the operation of the state of Tenessee.

As far as i know, yes its a known issue. U send files yesterday if im correct. As far as i know Eric havent been able to get his hands of saves, pre and post showning this until now.
I'd suspect from what i know of WCS it will be fixed and a update to the gold patch will be released when fixed and ready.

Kind regards,

Rasmus

ORIGINAL: DD696

Nashville still disappears using 1.9.23 and the save files started under the latest beta. Is this now a "known issue"? It's bad enough losing a regular city, but the loss of a capital puts a crimp in the operation of the state of Tenessee.

Maybe it happens when Sherman is in the Lineup. [:D]

It's a known bug, but not one that has been pinned down yet. Anyone with save files (or autosaves) before and after it happens should zip the .rep and .sve files and e-mail them to ericbabe@west-civ.com. Thanks.

By the way, I moved the thread here because bug-related threads belong in the Support forum.

I've had the same problem with a game awhile back but didn't have the save files to send

New game under latest patch: Lynchburg has disappeared after a successful[:(] seige. Am also in the process of beseiging Memphis and Knoxville but am getting very frustrated with disappearing cities. Saves available if they are wanted. Game stopped and shelved until this issue can be fixed.

Thanks for the offer -- please do send the save files (both .rep and .sve) to ericbabe@west-civ.com, along with a description of the problem, giving as much info as you can. Saves both before and after the problem occurred are ideal, if you have both. To my knowledge, this is the only significant bug still out there, so we definitely want to move quickly to stomp it out.

Before and after saves sent along with some info. If any more is needed let me know. Either I and one other person are the only ones experiencing this or there are a lot of silent players out there.

Thanks.

It's a small -- and vocal! -- group that is being affected. The problem has been around for a while because Eric can't debug it without having save files that capture the problem as it's happening. Maybe your files will hold the key.

Anyone else who wants to help should always save before hitting "End Turn," so that if the problem happens then we'll have both the "before" and "after" files.

Just got back from a quick one day tour of the Gettysburg battlefield. Was quite pleased to see that the town had not disappeared like Nashville did. [:D]

I've been very quiet. Any progress made on this? Haven't played it since 5 June and would like to try it again someday.

We think it's fixed, but are still testing.

Thank you....anxiously awaiting the next release.

One thing I should point out is that with a bug like this, that happened so rarely, "absence of evidence is not evidence of absence." Meaning that since only one of our testers had ever encountered the problem, the fact that none of our testers has encountered it since Eric (believes he) fixed it does not prove it's fixed. But we think it's fixed.