v2.0.1 crashes on startup due to lack of AMD display driver about displaymagician HOT 9 CLOSED

@domenic AAARGHHHH! Can you please change the Settings > Logging Level to TRACE, and then restart DisplayMagician (which will create a TRACE level DisplayMagician.log file. Please then attach the TRACE DisplayMagician.log file to this issue and I'll look at it later this evening. I should be able to get out a fix overnight, so I'd appreciate it if you could test tomorrow....

from displaymagician.

If anyone else is experiencing this issue, please comment below. I need to have a few more people to test in order to try and figure out what is happening.

In my tests, when the AMD driver was removed from my machine, DisplayMagician v2.0.1.59 still worked fine. So I need some more information from people who are experiencing issues so that I can troubleshoot it.

from displaymagician.

@domenic I've tested multiple times and stepped through the code, and that AMD thing might be a problem with some left over from your testing of the alpha for me....

Are you able to please delete your DisplayProfile_2.0.json for me, and start again with new displays, and then tell me if you still have an issue?

from displaymagician.

Hi @domenic ,

I tested on another PC that doesn't use AMD at all and hasn't had it installed, and that worked ok without errors. It had previously run DisplayMagician v1.1.4, so I had to recreate the v2 DisplayProfiles and update the Game Shortcuts, but then it ran the games fine.

It's looking more like a problem that is only affecting your PC, but further testing should help. Are you able to please delete your DisplayProfile_2.0.json for me, and start again with new displays, and then tell me if you still have an issue?

from displaymagician.

I was unable to configure the logging level because it crashed on startup. May I suggest just making the logging level default to "trace", so as to make debugging easier in the future without the extra step for your users? Especially since you erase the logs on every program start anyway, it shouldn't be an issue...

Renaming %LocalAppData\DisplayMagician to %LocalAppData%\DisplayMagician.bak indeed fixed the issue and now I can start the program again. It's a shame to lose all of my profiles :(

from displaymagician.

Great point about the trace log file. The problem is that it slows down the application with all the logging to disk when in trace mode from the volume of trace messages sent. I might try to add a button that restarts in trace mode somehow to make it easier, and packages up all the files I need to see into a zip file. That would be pretty handy...

Did you manage to make a trace log for when the app was broken? I'm afraid no logs came through the GitHub system of you did :(. I'm still really keen to see what was broken so I can figure out how to make DisplayMagician more robust and not crash when that situation happens.

Would it be possible for you to go back to the older broken configuration and to make a trace log files, and then come back to this issue in your web browser and reply with the following attachments? I'd like to see:

• Trace level DisplayMagician.log
• DisplayProfiles_1.0.json and DisplayProfiles_2.0.json
• Settings_1.0.json and Settings_2.0.json
• Shortcuts_1.0.json and Shortcuts_2.0.json

That should give me enough information to troubleshoot this properly.

Thanks
Terry

from displaymagician.

I'm going to close this now so that I can better keep track new incidents. I'm still really keen to understand how is broken but I understand if you aren't able to get a copy of the files then that's perfectly ok.

from displaymagician.

@domenic Sorry to open up old issues, but were you running a cloned display at the time DisplayMagician failed to start? @sneakingJ has found this seems to be the cause of his issue under issue #47, so I was wanting if it was also the cause of yours....

Thanks
Terry

from displaymagician.

No, I have no cloned displays.

from displaymagician.