Apply WineD3D renderer from support configs

BU
6d ago
+24-2

Root cause: support cards update dxwrapperConfig.renderer, but ContainerUtils only copied the dxwrapperConfig string while applyToContainer writes the Wine Direct3D renderer registry value from ContainerData.renderer. The affected report therefore saved renderer=vulkan but Wine still logged 'Using the OpenGL renderer' and repeated 'Unhandled interpolation mode 0x3'. This change synchronizes ContainerData.renderer from dxwrapperConfig when that key is applied (app/src/main/java/app/gamenative/utils/ContainerUtils.kt:428) and adds a regression test (app/src/test/java/app/gamenative/utils/CommunityConfigApplicationTest.kt:176).

Summary by cubic

Fixes the WineD3D renderer not matching the configured value when support cards update dxwrapperConfig.renderer, so Wine now uses the requested renderer (e.g. vulkan) instead of falling back to OpenGL.

Bug Fixes

  • Syncs ContainerData.renderer from the renderer key in dxwrapperConfig when that config is applied.
  • Adds a regression test covering the renderer update.

Summary by CodeRabbit

  • Bug Fixes
    • Applying a graphics configuration now updates the container’s renderer when the configuration specifies a non-empty renderer, while preserving the existing renderer if none is specified.