Originally Posted by Hezzy002 (Post 1695041)

Wait, no math or rendering as in a 64x64 loop without transformation or rendering? What else are you doing? It sounds like something odd is going on if you're getting significant performance drops from things other than what should most intensive parts.

Unless I'm misunderstanding what you meant by math and rendering, of course.

Putting each polygon on its own layer, or at least ensuring neighboring polygons don't have the same layer should prevent Graal from trying to sort them. Normally Graal sorts images by their bottom left corner, which, at least on some of the older clients, caused huge performance drops because it was done every frame without regard to the previous frame (It should store the new, sorted data so the majority of the stuff is still sorted).

Dynamically scaling up would drastically increase performance and visual quality..

Originally Posted by DustyPorViva (Post 1695047)

My mistake, it was disabling everything other than the polygons. I ran a 64*64 loop and only displayed polygons, with nothing else going on in the loop, and that's what caused the massive slowdown. Even without textures applied. I will have to try the layer thing, but I doubt it would make much of a difference in extreme cases. The fact that I can render an entire level with this perspective with no slowdown(while only have some minor visual distortion), is quite an accomplishment in Graal, imo.

Originally Posted by Hezzy002 (Post 1695049)

I wonder.. is there a way to render the entire scene with just one, massive polygon? It would be possible if you can manipulate the UV coords independently of the vertex positions. If you could pull that off, your performance would literally skyrocket.

Originally Posted by DustyPorViva (Post 1695050)

Oh, and also even if you use one polygon, you can't emulate distance with it.

Originally Posted by Crow (Post 1695051)

Why not?

Originally Posted by DustyPorViva (Post 1695055)

Because you can only apply one texture to a polygon, and you'd need the have the Y scale of the image vertically get smaller towards the horizon. At least, that's how I figure. Either way Graal doesn't like skewing textures on polygons.

Originally Posted by Hezzy002 (Post 1695056)

If you can set the UV coords independently from the vertex positions like I said earlier then you can do the exact same thing you're doing now with a single polygon. How do you set the UV coords?

Originally Posted by DustyPorViva (Post 1695059)

Originally Posted by DustyPorViva (Post 1695059)

I don't think you can. Regardless, this is what it looks like when you apply an image to a skewed polygon:

The issue was brought up with Stefan a long time ago, but I don't think it will ever be fixed.

Originally Posted by Hezzy002 (Post 1695061)

You said it an earlier post you could :/

Anyway, if you can't set UV coords independent of their vertex positions, then the only increase in framerate that'll really help you is reducing the amount of draw calls. In your case that pretty much means the only thing you can do is reduce the amount of polygons. You should really scale the quality up from high to low as it approaches the horizon, though, with this technique it's the only room for speed improvements as far as I can tell.

Originally Posted by DustyPorViva (Post 1695099)

Managed to get this much done just before bed. Finally implemented rendering gmaps. It's still a bit buggy(some levels seem to not be rendering, some divide by 0 issues with some polygons), but I'm very glad I got past that hump.

Originally Posted by MattKan (Post 1695122)

This is quite interesting. Will we finally see a Graal 3D? :)