NativeCamera - Use the main camera on iOS rather than virtual camera #1136
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change makes it so that the NativeCamera plugin on iOS will use the devices main/primary camera for the VideoTexture. Previously it was picking the virtual (dual/triple) camera's first. The dual and triple cameras are a virtual camera that will swap between the different physical sensors on the device based on the zoom factor. Generally speaker they are the better camera to choose IF you are also in control of the zoom factor. That isn't currently the case for the Babylon implementation so it will be better to choose the main camera sensor instead of one of the virtual sensors.