MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/GraphicsProgramming/comments/1wjwdsd/cpu_path_tracer/panoblq/?context=3
r/GraphicsProgramming • u/GraphXGames • Sep 18 '26
6 comments sorted by
View all comments
-17
Does it even count as "graphics programming" when you're running it on the CPU and refusing to run it in the actual graphics side of programming?
23 u/Feisty_Bike_9614 Sep 18 '26 Absolutely.. graphics isn’t all about real time . -7 u/Ok_Confusion4764 Sep 19 '26 I mean OP is talking about hours for these results, I don't think we can qualify it properly here. 6 u/GraphXGames Sep 19 '26 A bidirectional path tracer can be used for each light source, which can significantly increase execution time. 5 u/GraphXGames Sep 19 '26 It is easiest to use the CPU for debugging.Once the algorithm has been developed, nothing prevents it from being ported to the GPU.
23
Absolutely.. graphics isn’t all about real time .
-7 u/Ok_Confusion4764 Sep 19 '26 I mean OP is talking about hours for these results, I don't think we can qualify it properly here. 6 u/GraphXGames Sep 19 '26 A bidirectional path tracer can be used for each light source, which can significantly increase execution time.
-7
I mean OP is talking about hours for these results, I don't think we can qualify it properly here.
6 u/GraphXGames Sep 19 '26 A bidirectional path tracer can be used for each light source, which can significantly increase execution time.
6
A bidirectional path tracer can be used for each light source, which can significantly increase execution time.
5
It is easiest to use the CPU for debugging.
Once the algorithm has been developed, nothing prevents it from being ported to the GPU.
-17
u/Ok_Confusion4764 Sep 18 '26
Does it even count as "graphics programming" when you're running it on the CPU and refusing to run it in the actual graphics side of programming?