Jump to content
  • Advertisement
Sign in to follow this  
rajesh_nest

Unified shader model 4.0

This topic is 4034 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I have two doubts. ( 1 ) In shader model, I read that no differences between pixel & vertex shaders. What does it really mean? Does it mean that ( a ) Pixel shader and vertex shader can swap their functionalities.i.e Vertex shader can process pixels and pixels shader can access vertex ( b ) A common shader code syntax. Please inform me. ( 2 ) what is resource virtualization and what significance it has for GPU programmers. RRN

Share this post


Link to post
Share on other sites
Advertisement
the "unified" thing is just a hardware feature. it just means that the GPU only has processors. not specific ones for vertex and pixels, so for example you dont have to load balance between your vertex shaders and pixel shaders yourself.

Share this post


Link to post
Share on other sites
Quote:
Original post by rajesh_nest
( 1 ) In shader model, I read that no differences between pixel & vertex shaders. What does it really mean?

It more or less means that they have the same computational model (registers, instructions) and access to resources (textures, constant buffers). In terms of current hardware implementations they also share the same computational resources (ALU's, texture units).

They are still different in their functionality (their place in the pipeline), and they have different inputs and outputs, but in previous shader models the abilities of VS and PS were different (sometimes very different), and this is no longer the case.

Share this post


Link to post
Share on other sites
Quote:
Original post by ET3D
in previous shader models the abilities of VS and PS were different (sometimes very different), and this is no longer the case.


Abilities - Could you eloborate.


RRN

Share this post


Link to post
Share on other sites
I elaborated on that in my post. If you want more information, go to the DirectX documentation under "DirectX Graphs \ Direct3D 9 \ Reference \ Asm Shader Reference" and read more about the abilities of the various VS and PS models.

Share this post


Link to post
Share on other sites
Quote:
Original post by rajesh_nest
( a ) Pixel shader and vertex shader can swap their functionalities.i.e Vertex shader can process pixels and pixels shader can access vertex

No, pixel shaders still process pixels and vertex shaders still process vertices. It's just that both of them now have the same capabilities - both can load from textures, both can access the same resources and both have unlimited instruction counts.

Quote:

( b ) A common shader code syntax.

Pretty much, yes.

Share this post


Link to post
Share on other sites
or you can say, now "vs/ps" are only names of Code, not Hardware unit. there's no such hardware unit as "vertex shader" or "pixel shader". there's only "shader".

Quote:
Original post by Sc4Freak
Quote:
Original post by rajesh_nest
( a ) Pixel shader and vertex shader can swap their functionalities.i.e Vertex shader can process pixels and pixels shader can access vertex

No, pixel shaders still process pixels and vertex shaders still process vertices. It's just that both of them now have the same capabilities - both can load from textures, both can access the same resources and both have unlimited instruction counts.

Quote:

( b ) A common shader code syntax.

Pretty much, yes.


Share this post


Link to post
Share on other sites
Ideally. Vendors are allowed to choose whatever architecture they want, as long as the logical programming model is matched. Each architecture has its own set of advantages and issues over the other.

In general, I feel all the hype about this "unified" (cores) thing nothing more than a marketing weapon.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!