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

fix: Do not set Ruffle's renderer explicitly #1227

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

adamantike
Copy link
Collaborator

According to Ruffle documentation [1], the preferredRenderer option is only needed if a renderer needs to be enforced. When not provided:

By default, Ruffle chooses the most featureful backend supported by the user's system, falling back to more basic backends if necessary.

This commit removes the preferredRenderer option from the Ruffle configuration in the frontend, so that the default behavior is used.

It also removes the noisy logLevel option, which was set to debug.

Fixes rendering issue for Boxhead: The Rooms, reported in #1216.

[1] https://github.com/ruffle-rs/ruffle/wiki/Using-Ruffle

According to Ruffle documentation [1], the `preferredRenderer` option is
only needed if a renderer needs to be enforced. When not provided:

> By default, Ruffle chooses the most featureful backend supported by the
> user's system, falling back to more basic backends if necessary.

This commit removes the `preferredRenderer` option from the Ruffle
configuration in the frontend, so that the default behavior is used.

It also removes the noisy `logLevel` option, which was set to `debug`.

Fixes rendering issue for `Boxhead: The Rooms`, reported in #1216.

[1] https://github.com/ruffle-rs/ruffle/wiki/Using-Ruffle
@adamantike adamantike requested a review from gantoine October 7, 2024 00:03
@adamantike adamantike merged commit 36c77d5 into master Oct 7, 2024
7 checks passed
@adamantike adamantike deleted the fix/do-not-explicitly-set-rufflers-renderer branch October 7, 2024 00:13
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.

2 participants