[Papervision3D] AS3 drawing API - filled 2x slower then wireframe

[John Grden]

are these tests with as2 or as3?

I'm guessing as2, as that Xwing model demo I did had 949 faces and got as
low as 2fps with a bitmap material

On 1/12/07, Tim Knip <tim.knip at gmail.com> wrote:
>
> Did some additional benchmarking on the drawing API...
> man, its too damn slow!
>
> Got a model with 413 verts and 702 faces....
> After matrix-transformation and projection to screen I get:
>
> 1. not drawing => +50 fps...
> 2. wireframe => 15 fps
> 3. solid filled => 6 fps.
> 4. bitmap filled => 6 fps (!!!)
>
> Apparently Flash's raster-code isn't much good?
> I admit: for sure they have other things on their mind (like
> interactivity) then polys p/sec...
>
> Hehehe: I'm thinking of a standalone app where Flex calculates stuff
> and OpenGL displays... wonder what that fps would be....
>
> Carlos: about your idea of using ByteArray: as guys of byterarray.org
> are showing its possible to out-perform Flash's raster-code ;-).
> Texture stuff will obviously slow down things further.
>
> Going to try this week I think, but still gotta use setPixel(s) to put
> stuff 'on screen', afraid that will be the bottleneck (setPixel ==
> drawing-api??)... Or are there other alternatives for putting a
> ByteArray on screen?
>
> Tim
>
> _______________________________________________
> Papervision3D mailing list
> Papervision3D at osflash.org
> http://osflash.org/mailman/listinfo/papervision3d_osflash.org
>



-- 
[  JPG  ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/papervision3d_osflash.org/attachments/20070112/523fbaad/attachment.htm