Skip to content

Optimization for Stage3DBatcher ...#318

Open
volkipp wants to merge 2 commits intoaduros:masterfrom
volkipp:stage3dbatcherfix
Open

Optimization for Stage3DBatcher ...#318
volkipp wants to merge 2 commits intoaduros:masterfrom
volkipp:stage3dbatcherfix

Conversation

@volkipp
Copy link
Contributor

@volkipp volkipp commented Jan 26, 2015

I believe this should fix #314. I've created a stress using 2000 animated MovieSprites. With these changes I'm getting a solid 60FPS. Without the changes, I top out at about 20FPS. Hopefully this doesn't introduce any weird bugs, but so far it's been solid for me on my projects.

The stress test demo I'm using can be downloaded here:
http://clients.seven2.com/out/batcher-stress-test.zip

@markknol
Copy link
Contributor

I'm not into these batchers but shouldn't the same conditions be done in the WebGLBatcher?

@volkipp
Copy link
Contributor Author

volkipp commented Jan 26, 2015

@markknol I looked at doing the same thing in WebGL batcher and it doesn't seem to work quite the same way, and doesn't suffer from the same performance hit as Stage3D. I think it has to do with the requirement of clearing out textures when changing rendering contexts in Stage3D, which doesn't apply for WebGL. All I did was check to see if we are using the same texture root (therefore the same texture in the GPU), and make sure we don't call flush when it's not needed. My understanding of what is going on there is a little fuzzy, so it's possible it's just me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flambe doesn't batch the textures created using the "subTexture" function.

2 participants