Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compare with three.js #39

Closed
no-zzz-un opened this issue Apr 2, 2013 · 3 comments
Closed

compare with three.js #39

no-zzz-un opened this issue Apr 2, 2013 · 3 comments

Comments

@no-zzz-un
Copy link

I'm using THREE.js for a 2d game project.

It seems like the webgl batching performance optimisation, and the interaction manager, are where pixi.js distinguishes itself from other libraries.

Are there other points? THREE.js feels like overkill for my project and I'd prefer to use something specifically 2d oriented.

@GoodBoyDigital
Copy link
Member

Cool!

THREE.js is easily the best engine to use for 3D. In 2D land pixi.js is a pretty good alternative as its specifically built to handle 2D so its a lot faster simply because theres less to do (eg no depthBuffer).

Pixi.js is optimised for mobile and great care has been taken to ensure that the webGL renderer and Canvas renderer look exactly the same which is a nice bonus too :)

Its is also specifically a render engine so you can use it a part of your game engine / app framework rather than it being your engine/framework if ya see what I mean?

@englercj
Copy link
Member

Considering this question answered.

@lock
Copy link

lock bot commented Feb 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants