Wedge009
Wedge009
@Pentarctagon Changes in the Steam run-time, perhaps?
What are the build errors in 1.18? You might wish to log that in a separate issue - I think, normally, there are pre-processor guards for version-specific boost differences. I...
Any update on this?
Back to the specific issue of 1.19 Steam releases not working, if there's no further information I'd say this is a candidate for closure - it's been a few months...
You can use key words in your commit messages to mark your PRs as resolving existing issues: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests The images are meant to show a 'before' state?
I confirm this using the 1.17.9 Windows installer package from SourceForge. But only on Windows 7, I couldn't find a similar directory for Windows 10 - and I have no...
Revisited this while investigating something else. Confirming this was introduced at some point between 1.17.4 and 1.17.5. Edit: @Pentarctagon could #6685 be related to this as well?
I'll check if 1.16 starts having the same problem if/when it gets back-ported then.
What's your drive layout? Maybe it happens only if a D-drive is available.
So presumably there's a hard-coded desire to write to a D-drive in fontconfig somewhere. If there isn't a D-drive, it just doesn't have a cache.