Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible use NV_command_list #23

Open
mrdeathjr28 opened this issue Mar 6, 2018 · 3 comments
Open

Possible use NV_command_list #23

mrdeathjr28 opened this issue Mar 6, 2018 · 3 comments
Labels
wontfix This will not be worked on

Comments

@acomminos
Copy link
Owner

Beyond the scope of wine-pba. Perhaps a change for a more comprehensive wine-azdo, but I'd imagine fleshing out DXVK would be more worthwhile given the amount of effort required to integrate NV_command_list into wined3d.

@mrdeathjr28
Copy link
Contributor Author

mrdeathjr28 commented Mar 6, 2018

DXVK is good but your work have more chances than approve in mainline wine and your work at simple seek seems very compatible with wine mainline

Without forget NV_command_list as added in gl spec sometime ago in wine mainline

https://source.winehq.org/git/wine.git/commit/6c6f92ee42b518d0e6cd97195b4ca9b4fae20114

However when you send patches must be have enough tests (many patches are rejected for this) and see what said henri verbeet* and jozef kucia

*Him practically decide if patches are accepted or not, specially wined3d related

@fagoatse
Copy link

fagoatse commented Mar 7, 2018

Vulkan obsoletes this. It's as @acomminos says - not worth the time investment.

@acomminos acomminos added the wontfix This will not be worked on label Mar 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants