-
Notifications
You must be signed in to change notification settings - Fork 48
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
Questions/suggestions #71
Comments
To be honest we have never mixed this two API. I don't think it should affect context creation. But lets wait more details from logs.
In the HybridPro extended API (RadeonProRender_Baikal.h) we have function rprSetLogFunction which allows you to set logging callback function.
Could you please to collect traces for this scene? To do this please follow this simple guide.
|
I don't think that there is a particular issue with Dear ImGUI, I certainly do something wrong with OpenGL configuration (context creation flags, order issue with rpr,...). That is why having minimal interactive tutorials with that works with all rpr backends and graphic API (DX12, OpenGL, Vulkan, Metal,...) would be really appreciated. I saw the headers with API for interops with all graphical API, but there is no real documentation on how to setup this (swap chain fences, resolutions issues,...). It might be accessible for an expert, but I don't work with those API every day, and this is why I am looking for a renderer.
I tried this (after rprRegisterPlugin call):
I got a handle to the module, but GetProcAddress returns a nullptr. Here too a documentation about what is RadeonProRender_Baikal (there is nothing that indicate for which backends API applies) and how to use extended API will be welcome.
PS: If I do all these reports is because rpr seems really great, but it is also pretty hard to come in. Due to the documentation and tutorials it still seems to be a pretty private project. |
I will do some new tests of the SDK now that I can use a GPU that support ray tracing (Nvidia 3080 RTX).
It seems that there is a lot improvements made since last time I checked, but the documentation and samples seems to stay a weakness.
Let me be specific:
For the documentation:
For samples:
Last time I checked I got issues depending on the selected GPU (integrated or discret) and backends seems to see GPU in different orders, so having a way to select them by name in the API can be great.
Please notice that I tried the NVidia Pathtracer SDK, which provide a full interactive application directly. It is much more convenient to see what their SDKs are capable to do.
The text was updated successfully, but these errors were encountered: