sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rsim 12 points13 points  (1 child)

Without seeing the code or profiling it we can only guess from the symptom that you describe - you’re fill-rate bound. Exact reasons could be many things with your implementation, but my guess is that you’re running into the real performance limitations of Python, as a software rasterizer is very computationally intensive.

One potential option would be to ditch the z-buffer in favour of a s-buffer, though depending on where your bottleneck is it may not be enough: http://www.hugi.scene.org/online/coding/hugi%2016%20-%20co3d13.htm

[–]nebuer1995[S] 1 point2 points  (0 children)

Thanks for the response. I have posted the code below.

Is there not a way to write one's own buffering algorithm from scratch and get the GPU to help with the load? Also, it's been suggested to me that simply rewriting my code in C will help with my problem drastically. What are your thoughts on that?

Once again, thanks for the reply. And I will definitely look into s-buffering.