Originally posted by [email protected]
View Post
Announcement
Collapse
No announcement yet.
75 Patches Queued For Gallium3D's Nine State Tracker
Collapse
X
-
Gallium nine integration in wine is totally independent from wine d3d9 support. It's in another directory, and uses only Windows API that wine implements via it other dlls, except for one specific request. That should be easy to maintain.Originally posted by pinguinpc View Post
Because wine development specially in d3d relates stay changing so much in lastest moths: buffer incorporation, buffer management, many changes in swapchain and other issues and in any update could be break nine
For this reason nine must have fork of wine for prevent this situation

- Likes 3
Comment
-
wine does not offer support for translating dx9 to cuda. if you mean that it translates cuda to cuda, then of course it does that, otherwise it will have to translate cuda to something else which is much more workOriginally posted by soulsource View PostFunny reasoning though, given WINE does offer support for CUDA, which is only working on nVidia...
and i guess cuda works on osx which is funding wine development
Comment
-
If d3d9 stay isolated this can be true but swapchain, buffer and other components affects all d3d (6-7-8-9-10-11) used by wineOriginally posted by mannerov View Post
Gallium nine integration in wine is totally independent from wine d3d9 support. It's in another directory, and uses only Windows API that wine implements via it other dlls, except for one specific request. That should be easy to maintain.
For this reason nine could be broken is only matter of time
Wine fork allows prevent this issue or maintain only wine versions dont break actual nine implementation

Comment
-
d3d9-nine.dll uses its own swapchain implementation.Originally posted by pinguinpc View Post
If d3d9 stay isolated this can be true but swapchain, buffer and other components affects all d3d (6-7-8-9-10-11) used by wine
For this reason nine could be broken is only matter of time
Wine fork allows prevent this issue or maintain only wine versions dont break actual nine implementation

- Likes 1
Comment
-
Wow! That is exciting. The performance of Nine is so much better than not using it, even with CSMT applied... I understand upstream not wanting to support it (kinda), but as an end user looking for maximum performance under Wine you would be crazy not to use Nine.Originally posted by sarnex View PostWe are working to merge with staging.
I don't have benchmarks, but I did compare the three options a few months back (vanilla, wine-staging with CSMT, vanilla+Nine) with Cryostasis, and I recall Nine performance destroyed everything else. I know Grim Dawn is the same story with recent builds... ~15 FPS for vanilla, ~60-90 FPS with Nine on my Fury X. Goes from being unplayable to being comparable to Windows performance. Did not test CSMT with Grim Dawn as I only noticed I didn't enable Nine the other day by accident - wasn't specifically looking to benchmark. But can't imagine too much has changed.
Surely the difference will be even more significant when Wine has more complete D3D11 support. I imagine many games will barely be playable due to the performance hit, and a Gallium3D Eleven option could make a massive difference.
With AMD making such progress on the free software drivers front, I don't think it'll be long (maybe within the next 12 months) before there is no question that AMD cards on GNU/Linux are the way to go. It used to be Nvidia cards were the best option not so long ago, and already many people are questioning that. If most GNU/Linux users would benefit from Nine or Eleven, that should be a big help in seeing such options make it upstream.
Comment

Comment