We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).
The RenderWindow class works by attaching to an existing GUI window using its ID / window ?at=default&fileviewer=file-view-default#RenderTarget.hh-105 handle string . This currently works for ogre as it already has built-in ?at=default&fileviewer=file-view-default render window support . The ?at=default&fileviewer=file-view-default OptixRenderWindow class is currently just a stub and doesn't do anything.
RenderWindow
For optix, we currently require the user to save the image data a buffer in memory then display it into their own window (e.g. see ?at=default&fileviewer=file-view-default#GlutWindow.cc-95 this line in simple_demo that captures data into image data object example) which requires users to write more code.
It would be nice to have a common RenderWindow API that masks these differences.
The text was updated successfully, but these errors were encountered:
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
Sorry, something went wrong.
No branches or pull requests
Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).
The
RenderWindow
class works by attaching to an existing GUI window using its ID / window ?at=default&fileviewer=file-view-default#RenderTarget.hh-105 handle string . This currently works for ogre as it already has built-in ?at=default&fileviewer=file-view-default render window support . The ?at=default&fileviewer=file-view-default OptixRenderWindow class is currently just a stub and doesn't do anything.For optix, we currently require the user to save the image data a buffer in memory then display it into their own window (e.g. see ?at=default&fileviewer=file-view-default#GlutWindow.cc-95 this line in simple_demo that captures data into image data object example) which requires users to write more code.
It would be nice to have a common
RenderWindow
API that masks these differences.The text was updated successfully, but these errors were encountered: