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

feat: Allow three.js renderer options to be configurable #259

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Smidgens
Copy link

@Smidgens Smidgens commented Dec 2, 2021

Description

When the videojs-vr plugin instantiates a three.js WebGL Renderer, it uses hardcoded values. This change will allow users to override these defaults. This would be beneficial for performance reasons, such as disabling antialiasing or tweaking power preference.

Specific Changes proposed

  1. In the defaults options object in plugin.js, there is now a property called threeRendererOptions containing values previously hardcoded.
  2. The renderer is now instantiated with options_.threeRendererOptions which is a merged result of the default values and those supplied by the user (if any), similar to how Omnitone is set up.

@Smidgens Smidgens changed the title Customize three.js renderer options Override three.js renderer options Dec 2, 2021
@mister-ben mister-ben changed the title Override three.js renderer options feat: Allow three.js renderer options to be configurable Dec 18, 2023
WCPetersen added a commit to WCPetersen/videojs-vr that referenced this pull request Feb 10, 2024
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.

None yet

2 participants