> For the complete documentation index, see [llms.txt](https://dojo-project.gitbook.io/flycast-dojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dojo-project.gitbook.io/flycast-dojo/overview/collecting-logs-for-troubleshooting.md).

# Collecting Logs for Troubleshooting

In the course of troubleshooting issues, I may ask you to provide me with logs so that I can properly diagnose your issue when the root cause isn't obvious.

## Windows

### Internal Emulator Logging

In the Advanced settings, you can enable "Log to File" which will create a `flycast.log` file in the same location as `flycast.exe` while you run the emulator. For Fightcade users, this would be `Fightcade\emulator\flycast\flycast.log`

After you have enabled Log to File, replicate the issue you want me to diagnose, then send a copy of `flycast.log` to the Discord support channel.

<figure><img src="/files/XOlRGKGKwzE4bkF7LxwT" alt=""><figcaption><p>Settings > Advanced > Log to File</p></figcaption></figure>

### DebugView

If Flycast Dojo's own logs do not reveal anything, we may resort to using a program called [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) to show a log of events from all currently running programs to investigate what is going on. This may be useful when troubleshooting interactions between different programs launching Flycast Dojo, like Fightcade.

Just download [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview), unzip it, and run `dbgview64.exe`. This will open a blank window. From here, you should replicate the issue to be diagnosed once more. Once you have performed actions on Flycast, you should see the DebugView window populate with events.

Once you have completed this, click on the "Save" icon to save the log to a file. From here, you can send the log file to me in the relevant Discord support channel.

<figure><img src="/files/KS6miuWPTvrSSkzSrkdq" alt=""><figcaption><p>An example DebugView log window after launching Flycast Dojo via Fightcade</p></figcaption></figure>

## Mac OS

### Internal Emulator Logging

In the **Advanced** settings, you can enable "Log to File" which will create a `flycast.log` file in the home directory's `data` folder. To access this directory, head to the **General** settings and hit the "Reveal in Finder" button.\
\
After you have enabled Log to File, replicate the issue you want me to diagnose, then send a copy of `flycast.log` to the Discord support channel.

<figure><img src="/files/0LVQNXKvZP3vM2z8Hknn" alt=""><figcaption><p>General Settings Window, showing Home Directory</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dojo-project.gitbook.io/flycast-dojo/overview/collecting-logs-for-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.