Real 3d in Html - updates

April 29, 2008 — flaim

updates to html3d

Hello,

The update includes:

- z-sorting for html objects (see this page),

- simple mouse interactivity,

- optimized z-scaling of fonts,

- optimized speed (redesigned communication with js).

 

The complete updated source is here.

Known issues:

- Antivirus software (checked with KAV) causes major slowdown when checking Javascript (only Internet Explorer browsers) …use Mozilla if you have Kaspersky turned on - fixed that

- slow…as hell ;) - it’s better now :)

have fun,

FLAIM

***** RECENT UPDATE ******

I’ve optimized the code and changed the files in this post (both the sources and example link) - everything is 500-800% faster than in the previous post. Thanks to the optimization the issue with Kaspersky disappeared also :)

… have fun :)

Posted in actionscript, as3, lab, math. Tags: , , , , , , .

4 Responses to “Real 3d in Html - updates”

  1. joshteam Says:
    April 30, 2008 at 6:12 am

    Very Very Cool, is this a JS/HTML Alternative to PaperVision in Flash?

  2. flaim Says:
    April 30, 2008 at 7:21 am

    Thanks Josh,

    Not really - this method uses papervision to render coordinates for js/html. All the 3d calculations are made in flash - the html/js layer is used only for rendering/display.

    FLAIM

  3. joshteam Says:
    May 2, 2008 at 6:58 pm

    That is very cool, I showed it to our flash dever here who uses PaperVision. Is there any type of performance gain for doing this. we both agreed this is a VERY cool programming feat, but trying to think of a pragmatic use of it.

    Thoughts?

  4. flaim Says:
    May 4, 2008 at 6:37 pm

    hey josh!

    There is no performance gain :) there is a major slowdown when doing this (80-200 points with x,y,z - or vertexes of a model is a maximum for most browser when rendering via div/html :)))
    There are also many other disadvantages -
    1. rendering triangles using divs would be really slow so any meshes are only theoreticall than usable..I’ve tried that :)
    2. Rendering lines is also very slow (for those who would like to make a wireframe material) - the fastest algorithm i’ve got does a single div-line in 16-18ms on a decent machine in ie7 (the fastest js dom available for now). Rendering a cube in wireframe needs 12 lines 24 frames per second :( - so this idea is crap too :)

    And some advantages:
    1. it’s fancy and cool to have a html/div working 3d on a website :) in form of a menu or sth. I’m building a 3d rotator right now - it handles it well :)
    2. it’s quite fast with filled and coloured divs - rendering a 100 is not a problem.

    FLAIM

Leave a Reply

« Real 3d in html / javascript / pv3d

Simple Maths in AS3 part 4 - drawing polygons »