-
Notifications
You must be signed in to change notification settings - Fork 865
Added Render Graph what's new. #2181
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
Conversation
|
It appears that you made a non-draft PR! |
|
|
||
| ### Render Graph | ||
|
|
||
| HDRP now internally uses a Render Graph system. This has no impact on features visible to the users but it should improve overall memory usage significantly. In the new HDRP template, the GPU memory usage decreased by 25%. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HDRP now internally uses a Render Graph system. This has no impact on features available to you and it should improve overall memory usage significantly. In the new HDRP template, GPU memory usage decreased by 25%.
| ### Render Graph | ||
|
|
||
| HDRP now internally uses a Render Graph system. This has no impact on features visible to the users but it should improve overall memory usage significantly. In the new HDRP template, the GPU memory usage decreased by 25%. | ||
| In case of regression we have missed in our testing, the old code path can be re-enabled in the rendering debug window. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you experience a regression due to the render graph, you can switch back to the original code path using the rendering debug window.
Added Render Graph what's new.