Can this SONY patent be the PixelEngine in the PS3's GPU?

One question does all of these sony graphics patents are going into the ps3?

 

They are ideologies that are going to be integraded in the PS3 GPU.

 

I believe they are asking you about XDR DRAM.
As in off processor memory.

*Smile*
It's interesting. Some of the terms on your list seem familiar.

It's better to learn what they mean. Not just group them into a list.

16x FSAA.. heh, I'm curious how much memory you will say.

 

Ok I'll go with jvd estimate 6x FSAA that's good for the next gen.

 

How come there are no PRO aliasing methods? Why does everyone always have to be against it?

 

Please explain what you mean by PRO?

 

Twas a joke.

 

The balance between the ops is dictated by the hardware to programmer, not the other way around. Generally speaking, if lots of texture makes sense on your target platform, you will use them, if it doesn't, you will not. There's nothing inherently good on using one approach or the other just for the sake of it.

Well if you were switching primitive contexts, each switch would effectively stall the pipeline inside the APU, which I think would be much more of a performance issue than the cost of memory copy for the context switch.
Anyway if during fragment shading APU would mimick a pixel shader exactly (not really know info about context of incoming pixels), you could probably just send them data from different primitives at the same time...

 

You are preaching to the converted Fafalada, I am not discussing the ratio of Math Ops and Texture Fetches ( the balance between the ops ).

I am saying that I see, compared to what you see on PlayStation 2, Xbox and GameCube, more textures being used in next-generation games ( not as lok-up tables per-se, just to add detail and variety to the scene ) as well as better texture filtering ( Anisotropic Filtering and Tri-linear ).

AFx4-16 and Tri-linear being default ( hopefully ) would increase the load on the Texture Filtering Hardware as we would increase the number of samples it has to take and blend which might mean longer latency for each Texture Fetch.

Do you really see graphics engines in the next-generation using even less texture variety than what you see in PlayStation 2 games ?

 

I wasn't really referring to console stuff that much as the shaders there are barely worth their name compared to what's coming up. So while you will likely do a couple more texture lookups relative to those too, the total shader ops will increase exponentially...

Btw, texture variety isn't exactly relevant to number of lookups. If you have tons of memory you can have a different texture for every rendered object - only using a single texture lookup

 

No joke, man... Jennifer Garner is a hottie! (Ok, so perhaps her mouth is a bit scarily-large, but still.)



...right, I'll be quiet now.

 

IST, yes, in November 1999, the GeForce1/GeForce256 (NV10) came out with 4 pipes, and it was announced in August or September of that year.

I was merely mentioning what was out at the time of PS2's announcement and PS2's release in Japan, I didn't note when exactly those PC chips came out.

 

Let me guess... a bucket loads!

Maybe he meant to have typed 16x [pipeline & 4x] FSAA??

 

I am Pro aliasing when I want staircases in my game!!

 

Hmm... very true! Otherwise everyone could just keep slipping down them!

 

Five year later...., thanks for the anwser ERP (and PC-Engine also).

 

Hm, I believe that's what the current graphics synth uses...