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

Move stereo/omnidirectional camera features to core extension(s) #17

Closed
jeffamstutz opened this issue Apr 20, 2022 · 1 comment · Fixed by #41
Closed

Move stereo/omnidirectional camera features to core extension(s) #17

jeffamstutz opened this issue Apr 20, 2022 · 1 comment · Fixed by #41
Labels
ready for proposal A formalized proposal to change the spec.

Comments

@jeffamstutz
Copy link
Contributor

This proposal seeks to move the omnidirectional camera and stereo rendering features to be core extensions. This is because they are niche features that implementations are likely to ignore if they don't already exist as an engine feature. Furthermore, the existence of these features may imply supported use cases that engines may not be interested in, such as VR. Thus moving them to be core extensions, this keeps a standardized interface while making them ultimately optional for implementers.

The proposed extension names are ANARI_KHR_CAMERA_OMNIDIRECTIONAL and ANARI_KHR_CAMERA_STEREO_RENDERING respectively.

@jeffamstutz jeffamstutz added the ready for proposal A formalized proposal to change the spec. label Apr 20, 2022
@jeffamstutz
Copy link
Contributor Author

This issue collapses into issue #20.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for proposal A formalized proposal to change the spec.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant