Originally posted by R41N3R
View Post
Announcement
Collapse
No announcement yet.
DXVK Reportedly Going Into "Maintenance Mode" Due To State Of Code-Base
Collapse
X
-
- Likes 3
-
Originally posted by archibald View PostBuilding such a CI system is certainly possible, it just requires a large amount of money/machines so that tests can be effectively parallelised. Importantly, the test machines need to be centrally administered and kept in known states, so it's not feasible for people to volunteer their own PCs to help out.
The Dolphin emulator is one of the projects that does this in order to make sure code changes don't affect rendering.
Running actual games is just going to be far too chaotic to be able to use as test cases, far too many places where parallelism or randomness - particles etc - could introduce noise in the resulting images.
- Likes 4
Comment
-
Originally posted by Ananace View Post
What would probably have to happen to solve that is for DXVK to adopt a similar CI design to what some emulators use, where they have a renderdoc-or-alike (of Direct3D) dump that's run with each commit, and that logs any pixels that differ.
The Dolphin emulator is one of the projects that does this in order to make sure code changes don't affect rendering.
Running actual games is just going to be far too chaotic to be able to use as test cases, far too many places where parallelism or randomness - particles etc - could introduce noise in the resulting images.
Comment
-
D3D drivers on Windows are full of workarounds to improve or fix some AAA games... Trying to match that in a generic driver like DXVK is probably impossible without introducing regressions. The only way to go further would be to introduce specific paths for specific games, but that would make the driver completely messy.
I think it's better to focus on maintenance and stability for now.
- Likes 12
Comment
-
Originally posted by spykes View PostD3D drivers on Windows are full of workarounds to improve or fix some AAA games... Trying to match that in a generic driver like DXVK is probably impossible without introducing regressions. The only way to go further would be to introduce specific paths for specific games, but that would make the driver completely messy.
I think it's better to focus on maintenance and stability for now.
- Likes 2
Comment
-
Originally posted by ssokolow View Post
Of course, the messiness could be mitigated somewhat by implementing it as some kind of "profiles" support that makes the combinatorial explosion and maintenance for game-specific hacks external to DXVK itself.
I has a sad because I know damn well that someone defend the "profiles are bad and you should feel bad for using them" stance because that person be more tarded than my cat
Comment
-
Originally posted by skeevy420 View Post
You know damn well that "profiles" are more evil than systemd and that no program should ever, EVER require any form of profiles or if/thens to work around a bug in a game from 23.4 years ago
I has a sad because I know damn well that someone defend the "profiles are bad and you should feel bad for using them" stance because that person be more tarded than my cat
- Likes 2
Comment
-
Originally posted by ssokolow View Post
Wine has profiles and, without them, it would be far less useful to me. I think they come with the "Running Windows things on Linux without a massive Microsoft appcompat team" territory.
- Likes 1
Comment
Comment