Sparen wrote: ↑Mon Aug 03, 2020 11:42 am
Following up from
https://bugs.winehq.org/show_bug.cgi?id=33765
I haven't touched the 5.0.1 stable - only the standard development builds. I tested with the 5.11 version you released and also experimented with a more recent one.
I’d mentioned Wine-5.0.1 as this won’t have some known bugs.
Fonts shouldn’t look so different but you can use the following;
Code: Select all
export FREETYPE_PROPERTIES=“truetype:interpreter-version=35”
This will force the older rendering mode, over the much newer freetype rendering mode.
Sparen wrote: ↑Mon Aug 03, 2020 11:42 am
The second issue I ran into was a major performance hit when using the packaged application over digging into the .app to locate the binary. In a game that typically only runs below 50 FPS when OBS is recording the screen and using 90% of CPU, the .app release of Wine adds enough overhead to have equivalent performance. This one can be avoided by using the command line to start the application, though it requires multiple steps to get to the bin directory within the .app.
I recommend installing using my brew tap so the package is installed without being marked as quarantined causing increased CPU load due to tccd going nuts.
Using the brew tap also adds the wine binaries into your using PATH meaning your able to use wine(64) within a stock terminal session.
The pkg don’t suffer from getting flagged by gatekeeper nor translocation due to how the installers function.
Sparen wrote: ↑Mon Aug 03, 2020 11:42 am
I also ran into a crash when I was planning to do some testing. I don't know if it was related to the build or not but I determined that it was best to wait for an official WineHQ build before submitting any more test data to the AppDB.
After the NTDLL conversion to PE format I’ve seen a huge increase in crashes during and since this occurred, these might be macOS/clang specific however I haven’t had enough tying to verify the issues also exist between Linux clang and macOS clang compilations.
I’d have liked to have sat down and verified all of the recent issues with my usual contact but we’ve both been rather busy as of late