I am running version 2.6.4 release 183.

For a while now I've had an issue with encounters that have already ended. It seems that over time they tend to get screwed up. Initially when the encounter ends it appears to be correct. After a time the past encounters will change name, combine, combatants will disappear from an encounter or it will just be completely deleted for some reason. Sometimes it happens 1 or 2 fights later, sometimes it takes a while. It is starting to be really frustrating because after a raid I go back to do some analysis and the encounters are gone or I have to open each encounter 1 by 1 till I find the right one. But then I don't even know if the numbers are right.

I've gone through the settings and don't see anything that could be causing it. I thought it might be culling, but everything there is unchecked.

Any ideas?

Leodox

There have been about three reports of something similar, however I have never seen it nor has anything changed in a long time regarding how ACT stores data. Even though everyone claims it was something recent (last two months).

Do you usually run ACT minimized? Does pressing the Refresh button change anything? Does importing logs from the same time frame show different results than real-time parsing?

I always run ACT minimized. It seems to have started around the time that I started using "Minimize application to Mini Parse window" and have ran minimized ever since then.

Very good questions. I will check both and get back to ya.

Leo

Just a little update...

After a long period of parsing, when my encounter list gets all screwed up, the "Refresh List" button does make it right again.

I have not tested the export/import feature on a screwed up encounter, but I assume if I first click the "Refresh List" button, then import/export afterward, everything will work fine.

Thanks for the input.

Leo

Since it was just a cosmetic issue instead of the blown out of proportion thing that people were making it out to be, I was able to fix the issue. It just had to do with the labels being written while minimized. They should not have, because the TreeView doesn't get new encounters while minimized.

Yeah, it looked alot worse then it really was. Great job! Thanks for the excellent support and quick response.

Leodox