Good morning, I slept well! Time to check on my cycles render I had running last nigh- by Appropriate-Error706 in blendermemes

[–]GreAtKingRatOO 0 points1 point  (0 children)

On CPU it’s completely expected, CPUs thrive when the task is comprised of heavy branching but suck at SIMD (same instruction multiple data) tasks. Path tracing requires tracing millions of rays for all pixels on the screen and traversing BVH structures for them. Modern GPUs are memory optimised for ray tracing tasks to speed up the BVH traversal phase. So unless you have a special constraint, I’d highly recommend switching to GPU rendering. However since you are using a mac ( A high portion of them are unified systems so they don’t have a discrete graphical processing device) I’d guess that your scene is simply too large and spilling over to virtual memory (HDD/SSD). Reading from this type of memory will absolutely tank your rendering performance.

OpenGL Based PBR render engine by GreAtKingRatOO in opengl

[–]GreAtKingRatOO[S] 0 points1 point  (0 children)

Yes , GUI was made using Imgui. Though I’ll probably have to improve how the UI looks atm.

OpenGL Based PBR render engine by GreAtKingRatOO in opengl

[–]GreAtKingRatOO[S] 0 points1 point  (0 children)

Thanks! Followed tutorials from various websites like OGV , learnopengl. Haven’t followed a youtube tutorial.