Exciting changes for Papervision3D

You’ve probably seen the official announcement on the Papervision3D blog already but I just wanted to summarise here and give my take on the situation.

Of course, Ralph has left, and i’ll miss him. But smart people like him need constant new challenges and I have no doubt that he will move on to bigger and better things! And I seem to be seeing him just as much as before!

Papervision3D 3.0
So we’re moving on with PV3.0, which will be our Flash Player 10 optimised version, rebuilt from scratch. Tim’s already making great headway with some of the core code such as how we handle rotations (with quaternions at the heart of every DO3D) and even some niceness with frustum clipping.

I think we’ve been guilty in the past of a lack of transparency in our process. When we all work hard for a living, it can be hard to make sure that we keep the community updated with what’s going on.

So we’ve decided this time to make the source code for 3.0 available on github as we’re working on it. If you have something to contribute, you can fork the code and have a go. If we like it, we’ll add it in!

New team members
Which brings us to the fact that we want new team members. If you do cool work with the code base we’ll most likely ask you to join us. Already we’ve enlisted Ben Hopkins who caught our attention with some crazy PixelBender experiments. Perhaps you could too?

Backwards compatibility
There are many things that need to be changed in the new version, so we’ve made a rule. That rule is that we’ll keep the API the same as PV2.0 unless there’s a very good reason to change it.

One of the more notable changes is that the axis system has changed, the z-axis now comes out of the screen rather than going into it. This is to bring PV3D in line with pretty much all the other serious 3D engines, and it should also make it easier to port code from OpenGL.

Papervision2.1 support
We realise there are some issues still to resolve in 2.1 and I for one, am going to continue using this branch for some time. So although there is a lot of energy and excitement around PV3, it doesn’t mean we’ve forgotten about the older code base.

I’m really really excited about these changes, and the renewed sense of energy that it brings. I believe the Papervision team members are among the best Flash programmers in the world, and it’s such a privilege to be a part of it.

20 replies on “Exciting changes for Papervision3D”

i love that this is a volunteer team, thanks.

i wish i could help more, i’m not smart enough.

i love that you’re attempting to make it backwards-compatible.

thanks for everything!

Hey that’s great you’re using GitHub – I have been using it for almost a year and I’m loving it. Git is awesome but – like most great things – there’s a bit of a learning curve… but I think it’s worth it. *forks repository*

Any word on whether the Papervision X engine may still be a possibility for… ? The demos I saw at FITC (Toronto) were quite impressive.

I’m still learning 3D math, etc. , but I figure checking out the code and playing with it will be a great way to learn. Thanks for sharing 🙂

Hi Seb!
I will follow the PV3 develop carefully. I learn a lot by seeing PV3D code.
About the new convention of z axis, it will be really better, PV3D 2.0 uses the left-handed triad (with z axis going into the screen) everywhere except in the uvmapping, that is governed by the right hand rule // // (i think it was for compatibilities with collada, it’s right?). Using the z axis coming out of the screen, the axis convention will be uniformed. It will be really better for physics implementations, because a great quantity of concepts and equations are based in the right hand rule.
Best regards!

I too wish I could help more – PV3D has been an incredible inspiration to me, and a driving force to further my OO AS3 skills. Whenever a new project arises at work, I’m the first one to suggest PV3D! Thanks for all your efforts and I look forward with great anticipation at trying v3!

As you guys are busy rebuilding the engine from scratch. Are there any new features that you plan on adding into the engine (besides the optimization which is great btw)?

Great news, thanks for letting us know! If you need help with anything let me know 🙂

@David Jumeau The FoE book isn’t gonna happen now – they were a bit previous in putting it on Amazon! I’m still interested in writing a PV book, but if I do it won’t be until later next year.

pv3 sounds like promising to save as3 developers’ life. The current branch has lots of issues such as unused code in the class files, and too old documetantion.

Comments are closed.