Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - jdindia

Pages: [1]
1
Feature requests / Batching and other graphical improvements
« on: March 07, 2009, 02:18:05 am »
I started my current project using SFML, but relatively early on I shifted to raw OpenGL in place of SFML sprites; keeping SFML for window creation and image loading.  I quite like the clean code style of SFML, in stark contrast to the make-shift disaster that I slowly hacked together over the course of my project.

However, SFML doesn't really do what I want.  I'd like state sorting/sprite batching, and looking forward I'd really like to be able to play with render to texture and perhaps even shaders.  I can imagine things like texture compression and built in sprite animation eventually being convenient as well.

Most of the recent changes I've seen to SFML have been in non-graphical areas, which is fine.  I'm curious what the level of interest is for graphical additions like I've suggested.  From my brief poking around in the sprite and renderwindow internals, I don't see how batching could be added without significantly changing things.  I could be wrong.  I see some of what I've listed on the roadmap.  Does that mean Laurent has design ideas, or just a general interest in the feature?

I have a pretty clear idea of what I want to be able to do.  I'm even willing to help SFML get there since I'll being doing some of this stuff anyways.  I'm just not clear on what direction SFML is heading in or whether the help is wanted.  =)  I can honestly see a fancy batching rendering system being confusing and 'ugly' in comparison to what SFML already has.

2
Graphics / Why does each sprite set the projection matrix?
« on: November 29, 2008, 05:58:08 am »
I've recently started using SFML in a platform game.  Because I had polygonal textured tiles, I had to do a bit of source browsing to make sure my OpenGL calls wouldn't cause trouble with the generic SFML sprites I was using.

I discovered that the SFML RenderWindow Draw call was setting the projection matrix and then calling the drawable's render function.  This seems a bit strange to me.  I'd expect SetView to change the matrix and then everything else to assume it had been set properly.

Pages: [1]