Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


Palette Based Rendering?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
9 replies to this topic

#1 TheAnti   Members   -  Reputation: 253

Like
0Likes
Like

Posted 05 April 2012 - 04:45 PM

I was wondering... if the idea of storing color information inside vertices was replaced with storing an index and supplying an array of colors/material on a model basis, would there be any significant performance difference or reprecussions?

The reason I ask is this system seems a lot more flexible and I think you would be able to use much more material information on a vertex level inside the shader.

Sponsor:

#2 InvalidPointer   Members   -  Reputation: 1444

Like
0Likes
Like

Posted 05 April 2012 - 08:05 PM

How would you interpolate said values across a face?
clb: At the end of 2012, the positions of jupiter, saturn, mercury, and deimos are aligned so as to cause a denormalized flush-to-zero bug when computing earth's gravitational force, slinging it to the sun.

#3 phil_t   Crossbones+   -  Reputation: 4109

Like
0Likes
Like

Posted 05 April 2012 - 10:42 PM

Well to interpolate properly you would need to do the index -> color transformation in the vertex shader.

Of course any kind of lookup table (an array shader variable, or a texture lookup in the vertex shader) is going to have a performance impact, but without trying it out in your scenario it's hard to say what it would be.

#4 Chris_F   Members   -  Reputation: 2466

Like
1Likes
Like

Posted 05 April 2012 - 11:23 PM

Why do you think this is even necessary? Do all your meshes have color data? Is it severely impacting the size of your meshes? Is vertex size having a large impact on your performance? Is there nothing better you could spend your time on improving?

Seems like a case of premature optimization, and I should know, I admit to having wasted much of my own time on it before.

#5 Krohm   Crossbones+   -  Reputation: 3261

Like
0Likes
Like

Posted 06 April 2012 - 01:17 AM

I was wondering... if the idea of storing color information inside vertices was replaced with storing an index and supplying an array of colors/material on a model basis, would there be any significant performance difference or reprecussions?

On GeForce6? I hardly believe so. On some Intel like GMA950? Possible. On D3D10 silicon. No way.
Will it be significant? I would expect no difference.

The reason I ask is this system seems a lot more flexible and I think you would be able to use much more material information on a vertex level inside the shader.

Flexible? I'm not on it. Indexing has some uses, but definitely not that. More information to the VS? I don't see the point.

Chris++

#6 TheAnti   Members   -  Reputation: 253

Like
0Likes
Like

Posted 06 April 2012 - 04:48 AM

I'm wasn't so much thinking about a performance boost, I was just wondering if the theory is sound.

I tend to use a lot of vertex coloring and it seemed to make sense in the event that I wanted to swap out the certain colors of something while rendering the same model instead of copying the entire model over or changing the color of everything.

I've never seen it done before so I assumed there was a a reason not to do it.

#7 InvalidPointer   Members   -  Reputation: 1444

Like
1Likes
Like

Posted 06 April 2012 - 06:37 AM

I'm wasn't so much thinking about a performance boost, I was just wondering if the theory is sound.

I tend to use a lot of vertex coloring and it seemed to make sense in the event that I wanted to swap out the certain colors of something while rendering the same model instead of copying the entire model over or changing the color of everything.

I've never seen it done before so I assumed there was a a reason not to do it.


Oh, OK, that makes more sense. Look into vertex data streams/input layouts, you can instruct the input assembler to pull the vertex color from a separate chunk of memory from the rest of your data. You'd just bind a different vertex buffer to your 'vertex color data' slot and leave the rest of it untouched.
clb: At the end of 2012, the positions of jupiter, saturn, mercury, and deimos are aligned so as to cause a denormalized flush-to-zero bug when computing earth's gravitational force, slinging it to the sun.

#8 TheAnti   Members   -  Reputation: 253

Like
0Likes
Like

Posted 06 April 2012 - 08:00 AM

Ah that seems like a clean approach, thanks!

#9 BornToCode   Members   -  Reputation: 950

Like
0Likes
Like

Posted 12 April 2012 - 04:34 PM

Yeah, you can do that, the only thing is that you would need to perform the interpolation the pixel shader end by passing the two colors from the vertex shader to the pixel shader as varying variables. That way it will interpolate the two values.

#10 Ashaman73   Crossbones+   -  Reputation: 8001

Like
0Likes
Like

Posted 12 April 2012 - 11:51 PM

I've never seen it done before so I assumed there was a a reason not to do it.

I think that this skipped, because at times where you use vertex color, you often needed the register for other tasks (i.e. skeleton animation data). The most recent approach in this direction is to use gradient mapping at the pixel shader level to recolor a model. Take a look at Shading a Bigger, Better Sequel: Techniques in Left 4 Dead 2, there's the gradient technique of L4D2 explained.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS