11 Oct
2024
11 Oct
'24
2:47 p.m.
On Fri Oct 11 14:47:40 2024 +0000, Jimi Huotari wrote:
Using a benchmark [1] to test for example, this helps a lot with performance when WINEDEBUG="err-d3d". I also get a similar score up to a certain point at least, with this patch and without it, when not setting 'err-d3d', though I don't know if that is a good test on the enabled slowdown.
If you want to run benchmarks you should use `WINEDEBUG=-all`, anything else is pretty much meaningless.
In particular, doing WINEDEBUG=err-d3d will give even worst results, because it allows d3d log level to be changed dynamically through the taskmgr, which means every trace will have to check if the level has changed.