Critical bug

[HSishi]

That probably depends on the match text.

[adetia]

It also appears to be impacting the ability to search logs including the weird timestamps.
For example my current log has both data from the 27th of April and onward, but it cant detect any data in it at all, even though my gina triggers appear to be working (tho timestamp is included in the match text now).

[Pellakin]

Same issue here. Three different computers. Setting clock back a day (4/30/18) lets the program load. Trying to load a 'current" (5/1/18 and beyond) log file makes it crash. Is there something that can be done about the output file for the EQ log?

[HSishi]

Nope, unless you are someone at DBG, coding the Log writing sequence.

[Reht]

Gima is aware. Thanks

[Deloehne]

Have not checked the crash logs, but the same thing is happening to me. I am kind of reluctant to change the system date but I will give it a try for the night

[Deloehne]

I have the same issue. Changing the date alone did not fix it. However, changing the date, deleting the then current log file, and rebooting did. I doubt both actions were needed, but I did them at the same time.

[Drakaz]

Ya the date format is what is messing it up and crashing. Please update thanks so much!

[svann]

I dont know if it was the latest eq patch or the latest windows patch, but gina is not working now. If it doesnt crash when it first opens then it crashes when it sees the first trigger. Problem started may 1, 2018. I could change my computer date to the 10th, but that breaks other things and may break security even. Not good.

[HSishi]

@svann: It was the latest EQ patch in which the date format written to the log file got changed slightly: Instead of "01" .. "09" for the day EQ now writes " 1" .. " 9".

This was already mentioned in this thread, now we patiently wait for GINA to be updated.