Dxvk: Suggestion: Registry or .ini file for settings

[SveSop]

Probably been suggested before, but seeing as there are some game/app specific things being added every now and then in the source code as a "setting", having this in either registry or in a settings.ini file would be highly beneficial especially for testing.

eg. https://github.com/doitsujin/dxvk/commit/01147492d5d8a27fff9a329faa43b9bf77ce1e07 is a specific setting for ManiaPlanet.exe.
There was another a bit back too i dont remember atm.

I see something being done with https://github.com/doitsujin/dxvk/commit/e53cb72e39610915a4fce49253e61635369281c4 aswell, but was not immediately clear how this is meant to be used.

As i said.. probably something that has been talked about, and is being considered, but what is the best solution tho? Registry setting, or .ini file? And if so.. where should the .ini file be? c:\windows? Game folder? What do ppl think is the most convenient? :)

[doitsujin]

Support for configuration files is planned, but has low priority.

[baka0815]

I think registry settings in \HKEY_LOCAL_MACHINE\SOFTWARE\DXVK\<Name of .exe> would be a nice way to do this.
This way there could be multiple settings under this key like ForceTex2DArray REG_DWORD 0x1.

[SveSop]

And perhaps a "Default" key if you want something to be set for all running apps, unless a override in the key.

[ssorgatem]

I'm not a fan of dealing with registry keys, so I'd prefer something like an INI file... maybe in the same location the log files would be generated. This would also allow different settings for games/apps sharing the same executable name.

[pchome]

One here for DXVK.ini (or so):

• It's a bit easier to edit text file and/or share between WINE prefixes
• It can contain comments to clarify what each options for
• It can contain multiple sections
• It's easier to switch options by commenting/uncommenting (;) them
• It have simple format widely known to most gamers

[default]
; PossibleOption explanation text
; PossibleOptionDefault=1

; Explanation text
ForceTex2DArray=0

[Name of .exe]
ForceTex2DArray=1
LogLevel=debug

Search path can be set to C:\windows (system root variable (?)), than to game root directory, so users can have either one config for each game in prefix or per-game config files.

[pchome]

Also here (simpleini) is the link I have posted before in another issue.
I'm not looked further than README, but it looks like single header file SimpleIni.h with simple and powerful API. This can save some time.

[SveSop]

Did not think about that @pchome Having comments (if its doable) is quite useful. I tend to make comments in my scripts just if i change a setting or whatever, and forget what it did.. so that is absolutely useful.

Do not like the "per game.ini" tho, as having multiple .ini files could be a mess.. Having a system .ini would be nice, and easy to backup incase you need to recreate the prefix :)

[jarrard]

Sounds good, but keep in mind that some settings can be VENDOR/Driver specific so a AMD or NVIDIA flag would need to be defined also, and maybe separate registry key areas like DXVK/AMD DXVK/NVIDIA. To top it off DXVK would need to check specific registry and be vendor aware.

That could be a issue.

[ssorgatem]

That all seems much easier to handle with an INI file with dedicated driver sections.

Driver, and not vendor, because one vendor can have more than one different driver (e.g. AMD: Windows driver vs AMDVLK vs RADV).

[pchome]

@doitsujin
Is there any plans/thoughts for this issue?

This should also fix some problems with #60 / #268 , so I'm asking is it worth to spend time on fixing build problems (supposing env vars will not be used anymore)?
I'll better try to help resolve this issue, if this welcomed and you have final view what should it be ( .ini/tool/imgui (is it possible ?) /... ).

[doitsujin]

@pchome yes, there are plans to add support for configuration files, but it has low priority and I have my hands full at the moment. I don't really want to have to deal with this right now.

[doitsujin]

Latest master adds support for a configuration file. Documentation is available on the Wiki.

Environment variables are still being used for:

• Debugging-related options, such as DXVK_LOG_LEVEL (it'll probably stay that way)
• The HUD options (I may add those options to the config file as well)
• Backend options (those will be moved to the new system soon).