In older versions of Ashes, this file was written to a single fixed location, %temp%/ashes, and was overwritten every time Ashes started. It now goes into a folder of its own for each run, next to that run's Debug log file and Minidump file, so that a crash report always carries the logs of the run that actually crashed.

If you experience a crash with Ashes, you can send the log file by including it in the Crash report. If you want to share the GUI events log file with us when Ashes has not crashed, please follow these steps:

Close all Ashes related windows that might be open
Open Ashes
Reproduce the error you are contacting us about
Close Ashes Open the %temp%/ashes-crashdumps folder. The easiest way to do that is to open an Explorer window, type in %temp%/ashes-crashdumps in the address box and press Enter
Every run of Ashes writes its logs into a folder of its own in there, named after a long identifier. Sort the folders by date and open the most recent one: it is the run you have just made.
In that folder you will find the file named ashesactions.log
Send us this file to support@simis.io.
To make sure we can help you as effectively as possible, please write in the email:
- What is the error? Why is what happened not what you expected?
- What steps did you take in Ashes before the error occurred?
- What is your use case? What type of results are you trying to obtain with Ashes?
- Do not hesitate to add screenshots that might help us understand your issue.

Here is an example of the data contained in a GUI events log file: