I’ve been looking recently at Five3D. I like the smoothness of the edges of the shapes, compared with Papervision3D or Sandy. The API is not very mature in comparison, and the sticking point is that it’s purely vector-based, not bitmap-based. This is a good and a bad thing. Good for vectors – including text (see this example by Zack Jordan) but it can’t handle bitmaps, MovieMaterial, VideoMaterial, etc …
What I need for the project I’m working on is to be able to use bitmaps in 3D space with the same smoothness as in Five3D.
cake.have() && cake.eat();
However, it doesn’t have to be *real* 3D … by which I mean a fully realised virtual 3D space with perspective and camera angles and all the rest of it – represented, of course, in 2D. It can just be something that gives an impression of depth, I don’t care if it’s a cheap trick so long as the edges are sharp!
I’ve really enjoyed Five3D- it lets me do a lot of the stuff that I’d like to do with Papervision. The text thing alone is worth using it for a project. But yeah, I’ll agree- there’s not much in the API. But what is there is very elegant and easy to use.
I have to say, though- I’m kinda flattered to be confused with Zeh Fernando in your blog. He does some good stuff.
Hi, I’m glad you like FIVe3D. I just came across this post and I thought I should let you know that there is a new version 2.1 of the FIVe3D package available online with some new functionalities: Back Face Culling, Flat Shading, Z-Sorting, Bitmap3D class, Video3D class, Sprite2D class, Space Drawing Functions (moveToSpace, lineToSpace, curveToSpace). The documentation is on the way but since the code mimic the “display list hierarchy”, it’s not too difficult to figure out the new additions. Any question or input or feedback, feel free to come back to me. Thanks again.
Well now I’ve got to get to know 2.1…
Also, I mentioned the confusion with Zeh Fernando above in the hopes that you would correct the name, since the above example is actually by me. Thanks in advance.
Merci Mathieu! J’espere d’apprener la version 2.1 – en particulier Bitmap3D.
Zack, apologies. Duly corrected. I think it was the initial letter Z that confused me in the first place. Nice example by the way.
Not a problem. I figured that was the issue- and like I said, I was a little flattered anyway.
Continuing the topic, however, I am about to dig into this 2.1 that I’ve been hearing so much about…