Facebook Twitter YouTube Frictional Games | Forum | Privacy Policy | Dev Blog | Dev Wiki | Support | Gametee


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Building Little Parts vs. Big Parts
Acies Offline
Posting Freak

Posts: 1,643
Threads: 60
Joined: Feb 2011
Reputation: 73
#4
RE: Building Little Parts vs. Big Parts

Oh, there is a misinterpretation around the 600 triangles thing. That is regarding a polycount article - and how the GPU reads models. What it said is basically that somewhere around 600 triangles (depending on GPU) it doesn't matter if you optimze more. So <600 triangle models are basically requiring the same amount of performance. http://www.polycount.com/forum/showthread.php?t=50588

Performance-wise I think it's better to have one large texture, instead of several smaller ones. So in the instance of creating a room, it's better performance-wise to have all the room models in a 2048 texture rather than smaller textures. This has to do with something called 'drawcalls'.

However if the export of the room is made by bundling a lot of textures to one mesh I would rather recommend having them split up, for performance reasons.

Ultimately it's a matter of how you like to work. If you enjoy making the rooms as 'finished' models - do that. I find it nicer to split them into modular pieces, for the sake of 're-usage' later.

[Image: mZiYnxe.png]


(This post was last modified: 10-01-2013, 04:20 PM by Acies.)
10-01-2013, 04:19 PM
Find


Messages In This Thread
Building Little Parts vs. Big Parts - by Alex Ros - 09-30-2013, 11:21 PM
RE: Building Little Parts vs. Big Parts - by Acies - 10-01-2013, 04:19 PM



Users browsing this thread: 2 Guest(s)