Repository navigation
feat(config): implement initial ReShade preset support - #78
Conversation
This is preliminary work for updating uniform values at runtime. In order to update the uniform value in the buffer, the effect instance needs to look up the uniform by name - hence the need for the config key, which corresponds directly to the uniform's name.
More preliminary work for updating uniform values at runtime. Adds config parser support for int32, uint32, and boolean vectors.
This forms the foundation of ReShade preset support. - Added uniform support for int, uint, and bool vector types - Uniform values are now initialized from the preset k/v store - Uniforms now subscribe to changes in the preset k/v store
|
Very cool! <3 |
|
@kakra I'm sure you'll be eager to test this, rather than continue hardcoding values into effect files. Let me know how it works out for you! =D I have file watching almost ready as well, so you'll have the preset hot-reloading that you were asking for! It's just pending a small refactor in the config system, since the current architecture wasn't quite lining up. Hopefully today or tomorrow I'll have it all merged. The GUI integration will follow shortly after, again pending a bit of a refactor. |
|
It works well. But I think it doesn't align with ReShade yet: ReShade has presets in separate ini files, |
2 participants
Summary
Implement initial support for ReShade preset files.
ReShade.iniin the same paths asvkShade.ini.VKSHADE_PRESET_FILEenvironment variable for custom files.presetkey-value store.ReShade Compatibility
ReShade preset support is functional, but currently partial.
TechniquesandTechniqueSortingparameters are currently unsupported. Instead, vkShade uses its ownEffectsparameter and semantics.Testing
Tests have been adjusted and expanded to match config system changes.
All tests pass. Every commit compiles.