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

Generic EXE names in util/config/config.cpp #4048

Closed
Tiagoquix opened this issue Jun 2, 2024 · 4 comments
Closed

Generic EXE names in util/config/config.cpp #4048

Tiagoquix opened this issue Jun 2, 2024 · 4 comments

Comments

@Tiagoquix
Copy link
Contributor

Hi there.

The file https://github.com/doitsujin/dxvk/blob/master/src/util/config/config.cpp has generic EXE names, which makes me think that we should use more folder-based paths to apply fixes. As far as I understand it, DXVK can also be used to run normal apps (and not only games), so generic names (generally short names) may cause conflict for some apps (or, even, for non-related games) due to the fact that the fixes are applied globally to a specific EXE name.

Some examples below.


/* Assassin's Creed Syndicate: amdags issues */
{ R"(\\ACS\.exe$)", {{
{ "dxgi.customVendorId", "10de" },
}} },

/* SteamVR performance test */
{ R"(\\vr\.exe$)", {{
{ "d3d11.dcSingleUseMode", "False" },
}} },

/* Atelier Firis */
{ R"(\\A18\.exe$)", {{
{ "d3d9.deferSurfaceCreation", "True" },
}} },

/* Nights of Azure */
{ R"(\\CNN\.exe$)", {{
{ "d3d9.deferSurfaceCreation", "True" },
}} },

/* Crazy Machines 3 - crashes on long device *
* descriptions */
{ R"(\\cm3\.exe$)", {{
{ "dxgi.customDeviceDesc", "DXVK Adapter" },
}} },

/* God of War - relies on NVAPI/AMDAGS for *
* barrier stuff, needs nvapi for DLSS */
{ R"(\\GoW\.exe$)", {{
{ "d3d11.ignoreGraphicsBarriers", "True" },
{ "d3d11.relaxedBarriers", "True" },
{ "dxgi.hideNvidiaGpu", "False" },
{ "dxgi.maxFrameLatency", "1" },
}} },


And many others.

As much as, until then, I have not seen any report because of the generic EXE names, I still think we should remedy them and avoid them as much as possible.

Thank you for your attention.

Tiagoquix referenced this issue Jun 2, 2024
Works around flickering on character faces
@Blisto91
Copy link
Contributor

Blisto91 commented Jun 2, 2024

We would have to be careful though so as not to regress anything.
There is a small chance that if a game is available on different stores it might have different folder name or structure. Or if a game have a old retail version that have changed those with time through updates or when added to a digital store later. Though this is probably pretty uncommon.

Adding a folder would also mean the config wouldn't apply to a game if a user or modder decided to change the name of the game folder. If that is even something we want to take in to consideration

@Tiagoquix
Copy link
Contributor Author

Tiagoquix commented Jun 2, 2024

You have very valid points.

For newer fixes, as I suggested, if the name looks a little too generic, then we should use folder-based paths (Steam being the priority here for folder paths, if the game install is different on EOS and/or other stores).

As of now, I don't see anyone having an issue with the generic names, because the majority of users use DXVK to play games. But it's a nice thing to keep an eye on.

@doitsujin
Copy link
Owner

doitsujin commented Jun 2, 2024

Which of these exe names are used in more than one game?

The regex approach we use already supports install folders, but unless there are known instances of a config unintentially applying to a different game, changing these is just going to cause more harm than good (e.g. if a game uses a different directory on GoG/EGS than on Steam).

@Tiagoquix
Copy link
Contributor Author

Which of these exe names are used in more than one game?

Currently, I can't tell you if there are any games that suffer from this problem.

My idea was to create an issue to make the problem more visible.

Considering the previous comments, and considering that I also agree with them, I will be closing the issue.

Specific cases of games having problems due to a fix from another game being applied should be reported in individual issues in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants