search

Yellow-Dog-Man / Resonite-Issues

Issue repository for Resonite.
https://resonite.com
138 stars 2 forks source link

Crash / log submission system #2934

Open shiftyscales opened 1 month ago

shiftyscales commented 1 month ago

Is your feature request related to a problem? Please describe.

Currently when a crash occurs, the log files we request users submit are split across several directories- for a lot of issues we mostly only ever need the Resonite logs, however- for crashes, we also request the Player.log and error.log as available.

When the client crashes in a controlled way, it has time to provide stack traces in the error.log and memory dump as well as including the Player.log all in the same directory timestamped when the crash occurred.

The Resonite log itself however is in a separate directory- so users might include one set of logs, but not the other if they do not know any different / realize there are multiple places log files can be found, and several different types of log files.

Describe the solution you'd like

When possible- include all types of log files in a single (ideally easy to find) place to reduce friction of users having to collect and submit log files.

Describe alternatives you've considered

Some form of automatic submission system / wizard that helps the user report their issue- although this option would require additional development time compared to a (hopefully?) lower-effort bandaid fix by unifying where log files are generated / stored- particularly in the case of crashes where we often need / request all types of log to be provided.

Additional Context

I'm not certain if this is presently possible / easy to do- but there have been many occasions where I have to direct users to where to find crash-specific logs to include alongside their Resonite logs, particularly when submitting a crash report.

Seeking feedback from @Frooxius or @ProbablePrime.

Requesters

@shiftyscales

Frooxius commented 1 month ago

This isn't really easily possible. When the crash like that occurs, it's handled by Unity and our code at that point ceases to function - so we can't really do anything.

We'd actually much more likely implement the alternative with the submission system, which can handle collecting and submitting logs.

shiftyscales commented 1 month ago

I see thanks. I'll update this issue accordingly then.