Guest User

Untitled

a guest
Oct 19th, 2017
73
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.95 KB | None | 0 0
  1. Evilreaver posted:
  2. < Any explanation is gonna get out of layperson-land after a step. Suffice it to say that the code for rendering creatures is bad to the point of disgrace. >
  3.  
  4. I don't think it's that hard to explain. When you're building a 3D engine, you want to do everything in large batches:
  5.  
  6. code:
  7. < Setup; A HUUUUUUUUUUUUUUUUUUUGE list of crap in the world; Finish.>
  8. This is because setup and finish are expensive. What they've done is:
  9.  
  10. code:
  11. < Setup; One thing; Finish.
  12. Setup; One thing; Finish.
  13. Setup; One thing; Finish.
  14. Setup; One thing; Finish. >
  15.  
  16. ...
  17. So you spend a lot of unnecessary time messing with small objects, leaving your video card's umpteen bajillion processing units largely idle while the CPU is sweating pumping out one thing at a time. Add to the fact that the actual math being used is itself grossly inefficient, and you have a recipe for crap performance in a game that has roughly the same number of polygons as one TF2 gun.
Add Comment
Please, Sign In to add comment