This question may be a bit off track for OSG but it is something that I
think can be used by OSG developers.
I have collected many 3D models through the years and I am at a point
where I have lost track of everything I have so I am building a database
of the models. Since the models are mostly models that I have pulled
from various sources on the web this database will apply to many OSG
developers.
I have been thinking about the things that we as simulation / game / 3D
visualization developers would care about when we are planning a new
project. I have come up with the following list of attributes
Model Name
Model filename
Model creator
Model creation date
Model source (where can/was the model downloaded from, i.e. Avalon,
3dcafe etc)
Model Scale
Model use limitations
Thumbnail / icon picture filename
Larger picture filename
Time period / era that the model belongs to (dinosaur --> prehistoric)
Year real world item was created (ie the year a particular car was made)
External model fidelity (This might be somewhat subjective but could be
a number from 1 to 10 that indicates how close in appearance the model
is to the real world item)
Internal Model fidelity (this would only apply to models that can be
viewed from the inside
Rating (possibly similar to the movie rating system)
Model format (OBJ, MAX, 3DS, etc)
Number of textures
Number of polygons
Some of these attributes can be defined programmatically and others will
require human assessment.
I have been able to find the number of vertices using OSG but I have not
found out how to count the polygons. Which number would be a truer or
better number to store in the database to reflect the load the model
will have on the simulation.
I can get a list of the parts that make up a model which would be useful
for animations but that is so variable that I don't see a good way to
store that information in a database other than as a potentially very
long string.
Are there any other things we can use OSG to extract from the individual
models that should be included (scale, smoothness etc)?
Are there any other fields in general that should be included to make
this database useful to the OSG community?
If there is an interest in such a database the list can be posted on the
OSG site for the community to use and update after the initial creation.
Bruce
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not the intended recipient, you may not use, copy, disclose, or distribute this
message or its contents or enclosures to any other person and any such actions
may be unlawful. Ball reserves the right to monitor and review all messages
and enclosures sent to or from this email address.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
