[Papervision3D] ASE parser code

[Peter Kapelyan]

Hi All,

Before I write up my final findings of ASE code - I wanted to post them here so anyone can see so far and guide me.
I found out using "Biturn", a model 3d object converter, outputs some nasty code that Papervision does not like at all.
Out of a 100 vertice file - you will probably need to convert over 400 lines (depending if your object is a unified mesh or not) into something Papervision likes. So I have a couple of questions.

#1 Should I write detailed filings about anything that maybe be quickly changed in the parser code (it seems like it could pass)
#2 Should I write my detailed filings nevertheless - :)

This finding is crucial to me because I use Lightwave (not 3dsmax) to create 3d models - and other programs I can use to bone my models - and UV texture them, and animate them. So to get my file type through all these hoops, and find out the parser STILL doesn't like my code - well..you know...

Here is a brief summary of the problems I encountered with Biturn and the non-Papervision3D code it creates, I needed to edit only 3 chunks of code if it is an unified mesh:

If you look, and edit the ASE code from the bottom up of each of the chunks, 2 steps for each solution, and obviously not editting the whole code but in the chunks themselves:

-------------------------------------------------------
Solution #1
EXAMPLE= *MESH_TFACE  12    36    37    38
replace"   "(3 spaces), with " "(tab)
replace first 9 MESH_TFACE from "*MESH_TFACE*tab*" to "*MESH_TFACE*1space*"
-------------------------------------------------------
Solution #2
EXAMPLE= *MESH_TVERT 0 0.941 0.797 0.000
#1 replace" "(1 space) with " "(tab)
#2 replace ALL MESH_TVER from "MESH_TVER*tab*" to "MESH_TVER*space*"
-------------------------------------------------------
*MESH_FACE leave as is (YAY!!!!!!!!!!!!!)
Wipe sweat off forehead, apply deodorant to underarms, you have one step left
-------------------------------------------------------
Solution #3
EXAMPLE= *MESH_VERTEX 55 -0.833 0.833 -2.500
#1 replace" "(1 space) with " "(tab)
#2 replace ALL MESH_TVER from "MESH_TVER*space*" to "MESH_TVER*tab*"
-------------------------------------------------------

Then Papervison finally likes the Bitturn ASE...or maybe I should just use something other than Bitturn :)
Or maybe the parser can address these simple errors. or maybe I have spent too much time on this :)
Also beyond this - I realize the whole ASE can be stripped of any code that the parser does not need - and have step for which parts to delete which usually leads to at least a 17+% strip of the ASE file...I am sure with a large model it would strip off at least 30% of any code the parser maybe have to load or read online (because it has to all be loaded and read). So....maybe this whole finding will help me when I step up to the DAE plate :)

What do you think? Anyone who cares :)

-Pete






-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://osflash.org/pipermail/papervision3d_osflash.org/attachments/20070321/687aee68/attachment.htm