2009/2/5 Tim Moore <timo...@redhat.com>
> It would be most useful to inquire in the Lightwave community what people
> do for
> export to games.
Well this would always depend on the game in question as that is what
generally calls the shots in the main.
> OSG supports DirectX .x files, Flight format, Collada, even
> plain .obj for geometry and textures; those all seem like better candidates
> for
> loading into Flightgear than .lwo.
Well to take that in an assorted order but trying to logically link it all
together:
.lwo is probably directly analogous to .obj it's only a single solitary
object with no facility to contain animation data as far as I know. I've not
got any software that writes the .obj format natively so I can't say whether
it's any better or any worse at doing that job than a .lwo can; I'd be
surprised if the .lwo was found lacking in any way, and can easily imagine
it doing it better than many or even most and at least equal to any other.
DirectX differs from those two as it can and often will contain multiple
frames and animation point info, frequently with several individual objects
collected together and each of their local axis known, honoured and acted
upon. It may be that collada can carry this much info too. So this is more
of a "container" format than an actual object format, for want of a better
description. As I have mentioned before this has an analog in the .lws file
in lightwave parlance.
As for flight format I've never even seen one, where has that been used out
of interest? I've no idea which of these two styles it falls into, perhaps
you could enlighten on that? I'm always interested to know a bit more.
The more I think about all this the more I am wondering if it might not just
be an absolute master stroke if flightgear had it's own xml format for
laying out the various parts to a vehicle and where they all live relative
to each other, where and how they sit at rest, and then, since OSG is on
hand with it's multiple file reading abilities, it's not too far from
plausible to imagine it could even handle a plane made with multiple format
parts assembled by it. Which would be quite a breathtaking possibility,
although the point of it is a bit less than obvious. What it would do though
is allow any format that OSG can handle to be used to put together a fully
working plane no matter what. All this via the existing animation
facilities! Seems like huge value seen in those terms I'd have to guess.
Sorry I may be bit slow responding for the next day or so, I've had some
ill health issues giving me hell today, and have no idea how long it may
decide to play up for. It flares up from time to time and is pretty painful
which wears me down somewhat! Probably be OK again in a day or so. It
normally goes that way.
--
Cheers,
Ian
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
