[Mesa-dev] [Bug 93551] Divinity: Original Sin Enhanced Edition(Native) crash on start
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Aug 18 18:43:01 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93551
--- Comment #42 from Alex <axfelix at gmail.com> ---
(In reply to Thomas J. Moore from comment #32)
> Created attachment 125302 [details]
> Simple LD_PRELOAD shim to apply necessary patches for divos
>
> Game works great for me with the above patches (thanks to those who figured
> this out!). However, since they are not likely to be incorporated into
> Mesa, and patching my system Mesa just for one poorly written game is a bad
> idea, I think one of two alternate solutions needs to be provided. My
> preference would be to patch the game binaries. I don't really want to mess
> with that right now, though (especially since I can't easily locate where it
> does the vendor check). The other would be to provide the patches in the
> form of an LD_PRELOAD shim. I have attached the source code for one that
> seems to work for me.
Would it be possible to add another function to that shim to override the
output of sysconf (_SC_NPROCESSORS_ONLN)? I spoke to the developer and
apparently the game will only use as many "worker" threads (indicated by "[N]
WT" in the app title bar) as your number of cores minus the main thread, but if
you're in an environment where your single-threaded performance is heavily
constrained (e.g. a Y series Intel notebook chip like mine, when using the iGPU
throttles the CPU speeds) but you have multiple cores available, this isn't
ideal. From looking at my CPU usage under Divinity I'd really like to be able
to hack it to give me 2-3 worker threads instead of 1 to see if that helps
performance at all... I don't have much C experience though.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160818/e912806c/attachment.html>
More information about the mesa-dev
mailing list