Skip to content

fix: Fix game settings specific filters not doing anything#3179

Open
ferafiks wants to merge 4 commits into
stride3d:masterfrom
ferafiks:config-overrides
Open

fix: Fix game settings specific filters not doing anything#3179
ferafiks wants to merge 4 commits into
stride3d:masterfrom
ferafiks:config-overrides

Conversation

@ferafiks
Copy link
Copy Markdown
Contributor

@ferafiks ferafiks commented May 16, 2026

PR Details

Previously, the specific filters in the game settings asset didn't do anything. This PR fixes that.

Originally, there were two static fields in PlatformConfiguration that were never set: RendererName and DeviceModel. From what I assume, the former was meant to be the graphics adapter description (which now is being set) and the latter, the CPU model. I couldn't find a place where Stride stores the CPU name, so I removed it.

This PR also changes the previous unimplemented behavior: instead of trying to find the first matching configuration from a certain group (default, only platform filters, platform filters + specific filters), the engine now tries to find the last one.

Types of changes

  • Docs change / refactoring / dependency upgrade
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My change requires a change to the documentation.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • I have built and run the editor to try this change out.

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

Successfully merging this pull request may close these issues.

1 participant