I'm in the process of converting my application from crystalspace to soya. However I've got one issue I'm not sure how to resolve. I've spoken with jiba a bit about it but figured I'd bring up on the list to get more input.
Here is a sample level load file from my app. This loads a map from a specific project directory. It also adds a mesh of a bookshelf from a common package. <?xml version="1.0"?> <level> <map name="default" url="chapter/theMark/maps/cottageRoom" /> <mesh name= "testShelf" url="common/models/basicBookshelfWood" x="10" y="0" z="15" /> </level> This common package will contain commonly used models and textures used in several projects. Things like chairs, cups, books, tables, beds, weapons, standard NPC characters, standard creatures, etc, etc. I want to distribute a standard adrius-common-0.0.1.tar.gz that contains pieces each sub project can reuse. This way they only need loaded once. And any future improvements to models will be available to all chapters (a chapter = a complete game) However Soya3D currently expects to only use a single set of four directories from which to pull everything. This seems to make it impossible for me to seperate out the commonly reused items and maps from the chapter specific items. It also means that in a big project those four standard directories are going to get very full and file names might conflict. I'd like to see Soya3D be more flexible for cases like the above and I'm willing to do the work to make it so if people think it's a worthwhile addition and if the primary developers say it's possible. I've not yet dug into the code to see what this would involve so I may be way off base here. My initial thoughts are to make soya3d treat filenames that start with a path seperator as absolute. Thus if a filename is listed as /path/to/my/thing then any saved .data file would be saved in /path/to/my/ Any any suggestions, input, advice would be appreciated. I've also been working on a new blender2soya.py based upon the soya import_blender.py. It adds a blender GUI front end to the script, support for a envinoment variable SOYA_PROJ to set the project directory, and removes currently unsupported options like the camera objects and lamps automatically. I'll be adding in support for setting soya atmosphere settings inside blender in a mannor similar to the way the blend2cs project does it for Crystalspace. I'll probably also be readding support for lamps and cameras to define startup cameras. If there are any other features people would find usefull please let me know and I'll see what I can do. I'm a newb to both blender API and soya so no promises :) Take Care, james ->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-< James Thompson 138 Cardwell Hall Manhattan, Ks 66506 785-532-0561 Kansas State University Department of Mathematics ->->->->->->->->->->->->->->->->->->---<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-< -- Pour vous desabonner envoyez un mail a [EMAIL PROTECTED]
