Closed terrymacdonald closed 1 year ago
This appears to be at least partially related to #179. There may be a fix available in the ValveKeyValue library, but it requires DisplayMagician to move from using .Net Framework v4.8 over to using .Net 7. This is a major change, and something that will take a while to action.
Changing to .Net 7 means changing some libraries that we currently use, for example the Audioswitcher library to swap audio devices and the NHotkey library for keyboard hotkey support. This will take time to suit out and action, and it will almost certainly mean that shortcuts will need to be recreated. My gut feel is a month before I'll be able to have DisplayMagician converted. .
ok some big news! I managed to find some code that works with the new Steam format. Turns out they added a binary_vdf SHA-1 hash as a checksum into the structure of the new Steam Beta client. Big props to the SteamDatabase team for figuring that one out! I've tested the new code and it works fine, so now I'm preparing for a new release over the next couple of days.
For those who can't wait for the automatic upgrade, here is a zip file containing the version I'll be sending out tomorrow:
DisplayMagicianSetup-v2.5.0.350.zip
Hope that makes someone's day! If it does, maybe you may feel predisposed to buymeacoffee or two? I'm saving for a button box to make driving my simracing games easier.
Hope the rest of your day is amazing.
Thanks Terry
This has been fixed in the latest version of DisplayMagician released here: DisplayMagician v2.5.0
I will close this issue for now as the issue should have been fixed, but please feel free to reopen this if that specific issue is not fixed. If you find a different issue please create a new separate issue so that I can work on them separately.
Thanks Terry
Describe the bug Since the latest Steam Client Beta has been released, DisplayMagician is not able to read the Steam Games within the Steam Client. This is because Steam have changed to a new file format, and the library that DisplayMagician uses cannot support the new file format.
We will need to find a new solution for parsing the file format so that Steam Games will be able to be supported.
To Reproduce Steps to reproduce the behaviour:
Screenshots If applicable, add screenshots to help explain your problem.
Reporting Logs If DisplayMagician starts:
If DisplayMagician does not:
C:\Program Files\DisplayMagician\DisplayMagician.exe --trace
to create a TRACE-level DisplayMagician.log file.C:\Users\<yourusername>\AppData\Local\DisplayMagician\Logs
which should contain a LOT of detailed TRACE level log entries.C:\Users\<yourusername>\AppData\Local\DisplayMagician\Profiles\DisplayProfiles_2.1.json
C:\Users\<yourusername>\AppData\Local\DisplayMagician\Shortcuts\Shortcuts_2.0.json
C:\Users\<yourusername>\AppData\Local\DisplayMagician\Settings_2.0.json
Enviroment (please complete the following information):
Additional context N/A