Electromen Posted May 22 Share Posted May 22 I'm using the same .Plan file and also tried a new project created in X16. The Physically Base Rendering is considerable slower. Video Card is Nvidea 4080. Anyone else notice this? Link to comment Share on other sites More sharing options...
Solution Renerabbitt Posted May 22 Solution Share Posted May 22 3 hours ago, Electromen said: I'm using the same .Plan file and also tried a new project created in X16. The Physically Base Rendering is considerable slower. Video Card is Nvidea 4080. Anyone else notice this? as it should be, you are performing 3 path trace bounces as opposed to 1. But you can set AMDFidelity to a higher value to improve performance or decrease your bounce rate 2 Link to comment Share on other sites More sharing options...
buzzsaw204 Posted May 22 Share Posted May 22 3 hours ago, Electromen said: I'm using the same .Plan file and also tried a new project created in X16. The Physically Base Rendering is considerable slower. Video Card is Nvidea 4080. Anyone else notice this? yes, much more choppy. hope thats resolved in Full release. Link to comment Share on other sites More sharing options...
Electromen Posted May 22 Author Share Posted May 22 7 hours ago, Renerabbitt said: as it should be, you are performing 3 path trace bounces as opposed to 1. But you can set AMDFidelity to a higher value to improve performance or decrease your bounce rate Thank You, Setting it to 1 improve performance. Link to comment Share on other sites More sharing options...
DanDeBroeck Posted May 22 Share Posted May 22 PBR was re-implemented as a fully path traced model in X16. In short, a path traced implementation more accurately calculates lighting in a scene by simulating consecutive light bounces via ray tracing. Simulating these additional light bounces do require more rays to be cast than the prior implementation, as @Renerabbitt pointed out, which does have an impact on performance. The new path traced model results in higher fidelity renderings and resolves one of the most common complaints from the prior implementation, light bleed. While reducing the bounce counts may improve performance it will negatively impact the fidelity of your renderings. Setting the opaque bounce count to 1 and checking "Approximate Additional Bounces" should essentially get you back to X15 quality and performance, but will reintroduce common issues like light bleed. As @Renerabbittalso mentioned, another option to improve performance is setting the AMDFidelity super resolution to a higher value. AMDFidelity super resolution renders the scene at a lower resolution and then upscales the result for presentation. This approach, using the default bounce counts, will likely result in higher fidelity renderings than reducing the bounce counts and enabling "Approximate Additional Bounces". 2 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now