Closed GoogleCodeExporter closed 9 years ago
Both features sound great!
I believe that were trying to not use external resources like Ogre material
scripts.
Unless they can be extracted from within the blend file. I have the start of
parsing
internal resources setup, see gkTextManager, the only problem is being how to
tell
what type of resource the TX data block contains. The simplest solution would
be to
parse the data block name and search for the correct script extension (
.material
.lua, .py ).
For material scripts the gkBlendFile::_registerImage function will also need to
be
modified to register all internal IM data blocks, so the user could specify the
IM
data block name in the texture unit section of the Ogre material script.
Original comment by snailr...@gmail.com
on 22 Feb 2010 at 6:30
Original comment by silveira.nestor@gmail.com
on 24 Feb 2010 at 1:54
Original comment by silveira.nestor@gmail.com
on 24 Feb 2010 at 2:07
Original issue reported on code.google.com by
silveira.nestor@gmail.com
on 22 Feb 2010 at 4:36