Console Memory Thread
polycounter lvl 18
Every console developer is different I am sure. With my company, memory is always on the minds of us all. My question is, how do other companies deal with MEMORY issues?
For instance, our general way of thinking here is, make the environments and game play as imaginative and full of life as possible, then down size the memory. To me, thats a good start but tends to be really painfull when deadlines are super tight and all nighters are every night almost.
Who else relates to this and who else's company that they work for do things differently? I'm primarily trying to gain a better understanding of how other companies approach this issue.
For instance, our general way of thinking here is, make the environments and game play as imaginative and full of life as possible, then down size the memory. To me, thats a good start but tends to be really painfull when deadlines are super tight and all nighters are every night almost.
Who else relates to this and who else's company that they work for do things differently? I'm primarily trying to gain a better understanding of how other companies approach this issue.
Replies
You will know what resolution meshes you can get away with and what texture sizes you should be using.
And then you go back and rip some out.
Instancing geometry like trees (if your engine supports it), so that only one tree is held in memory, but displayed multiple times. The trick then is to get the lighting right so that it fits in all situations