Search results

They still do ... fixed point is most likely implemented using shaders and from what it looks like they have uvs on mediump.

From what I hear, ImgTech folks have reference drivers but generally it is up to licensee to integrate/rewrite them to suit their platform of choice ( TI in this case) For instance, Apple folks are already on their , I think 5th or 6th, major driver version - it took them almost 2 years to get...

Just the opposite. When it comes out (2-3 SGX generations from now) out it will slower and more buggy ...

You must be living in some other reality cause the way I see it , the whole thing shapes up to be an absolute disaster and frankly, being an outsider ( who actually ordered Pandora 2 years ago and kind of forgot about it ), spaceballs appears to be the voice of reason here, not the other way around.

If you target your code for OpenGL and GLES then that's a good idea .. on the other hand if you are using your desktop machine purely as a "GLES emulator" then using a wrapper library ( like the one from Imagination Technologies) is much more convenient ( they directly support a lot of...

No, it is not. You just download an emulator library running on top of Open GL and you are basically done.

From what I have heard on the iPhone (SGX based iPhones to be precise) GLES 1.x is emulated with shaders but not your vanilla GLSL shaders but something more native ( perhaps optimized native asm code ). In fact, someone from Imagination Technologies even suggested that trying to write your own...

Fixed pipelines on SGX devices are implemented using ... shaders so I doubt you will get much better results.

SGX natively is using tri-strips... in fact,as far as I know, everything you submit is converted by the driver into tri-strips. Of course, you are right, some models using tri-strips will result in a lot of batches or tons of degenerated tris... personally, I use tri-lists sorted into a...

Don't expect miracles ... in terms of shader processing SGX 530 can be about 1000 times slower than a decent PC based graphic card. Not in this case, but I see it all the time, people pick up shaders from some PC based book , dump it on SGX and expect miracles.

Pretty much ... the "a bit more slowly" part is a bit misleading though ... if you were to take a decent Nvidia card and run it at 800x480 it would probably run about 100x faster in terms of basic fillrate/vertex throughput so you gonna have to cheat ...

Nah, these wer just fake numbers ... essentially vertex counts calculated out of triangle counts ( admittedly useless data and I got rid of that since then)

Assuming no fancy shaders (and a reasonable backend implementation , meaning decent batch counts etc ), you could count on being able to display around 50-60K polys at around 30 fps - of course that's a very rough estimate ... there are many other things in play. PS. With a very basic shader...

No alpha-test just alpha-blend and there is a quad underneath . Everything is sorted based on a custom mask which in this case sorts based on blend states/texture changes and some other stuff. The models themselves are using indexed triangle lists exported with my own exporter (POD) from...

This test was ran in GLES 1.x mode using their internal shaders which presumably are reasonably optimized but that's beside the point .... I suspect the issue here is not how many triangles you can render but how many vertices you can submit for rendering - this was the bottleneck with the...

This was just a simple test to see if VBOs actually work as advertised on the latest iPhone ... and they do as you can see ... the top image marked as VBO is the same geometry submitted using VBOs while the bottom one is using generic client arrays. It used to make no difference on the older...

On the new iPhone 3gs ( which is using quite a bit faster version of the same chip - SGX 535) you can realistically expect about 40 K worth of polys per frame while running at 30-40 fps. I was able to display about 45K worth of untextured but lighted triangles running at 40 fps ( 9 counter...

Opps... sorry .... somehow ended up posting multiple copies of the same stuff ( Chrome was freaking for some reason )

I can tell you my experience from iPhone 3gs which is using the same CPU. Essentially, I am using a lot of handwritten asm VFP/NEON code to handle various transformation + C versions of the same code. The compiler on 3gs is actually generating NEON code ( not very optimal and not vectorized but...

I can tell you my experience from iPhone 3gs which is using the same CPU. Essentially, I am using a lot of handwritten asm VFP/NEON code to handle various transformation + C versions of the same code. The compiler on 3gs is actually generating NEON code ( not very optimal and not vectorized but...