Blender .Scene Exporter

reimpell · Post by **reimpell** » Wed May 11, 2005 7:50 am

turkeypotpie wrote:I'm still seeing the same problem.

Maybe you need to press the reload button of your web browser. The fix is trivial: In the export method in the class ObjectExporterTree you have to change the line "for exporter in self:" into "for exporter in self.rootExporterList:".

turkeypotpie · Post by **turkeypotpie** » Wed May 11, 2005 10:50 pm

Yeah, must've been a sticky cache. Works fine now

Thanks for your work on this; it's a very nice thing to have.

I've got a slightly OT question about the (non-dotscene) exporter ... or maybe this is just a blender thing. Can lightmaps be generated and exported?

I noticed that blender has a 'Texture Baker' script, but this only attempts to render the material to the texture, ie. it doesn't take into account lighting or shadows.

I also noticed that the radiosity can be exported via vertex colors, which is nice, but requires simple geometry like walls to be subdivided greatly in order to get a nice effect.

reimpell · Post by **reimpell** » Wed May 11, 2005 11:03 pm

turkeypotpie wrote:Can lightmaps be generated and exported?

AFAIK the ogrefsrad addon project can handle dotScene files.

reimpell · Post by **reimpell** » Sun Jun 05, 2005 6:14 pm

With version 2.37, Blender no longer fakes the orthographic camera mode. If you need orhographic cameras, please update your dotScene export script to revision 1.3 or newer and Blender to version 2.37 or newer.

dermont · Post by **dermont** » Mon Jun 06, 2005 5:32 am

I'm using windows, blender version 2.37 and export script revision 1.3.

I start the script, select my objects for export and click on the select export dir button <Select>, nothing happens. Only after exporting to the default path am I then able to select a path.

Also I have trouble exporting the world environment, in _WriteEnvironment the world.mode always seems to be zero. The only way I can get it to export is by replacing:

(world.mode & 1) with (world.getSkytype() & 1)
<fog .. mode=linear ..> with <fog .. mode='linear' ..>

reimpell · Post by **reimpell** » Mon Jun 06, 2005 8:12 am

dermont wrote:I start the script, select my objects for export and click on the select export dir button <Select>, nothing happens. Only after exporting to the default path am I then able to select a path.

Thanks, it's a bug in Blender's BPy introduced in 2.37. I'll write a workaround.

dermont wrote:Also I have trouble exporting the world environment, in _WriteEnvironment the world.mode always seems to be zero.

Works here, if "Mist" is enabled in the world buttons.

dermont wrote:<fog .. mode=linear ..> with <fog .. mode='linear' ..>

Yes, thanks again!

dermont · Post by **dermont** » Mon Jun 06, 2005 10:45 am

Yep, sorry didn't have "Mist" enabled. I was also wondering if, as part of future release, you were intending to include physics attributes using the physics properties from the Game Logic buttons and/or scripts. Then it would be possible using pyode / blender's ode(?) and some scripts to encapsulate say, OgreOde, and use blender to test out physics / ragdoll stuff etc.

reimpell · Post by **reimpell** » Mon Jun 06, 2005 4:59 pm

dermont wrote:I was also wondering if, as part of future release, you were intending to include physics attributes using the physics properties from the Game Logic buttons and/or scripts.

You can already export all logic properties using the "Logic Properties" export option. For the physics settings scattered around Blender's interface, I haven't decided yet. Anyway, the exporter is designed so it can easily be customized.

reimpell · Post by **reimpell** » Tue Jun 07, 2005 1:42 pm

reimpell wrote:
dermont wrote:I start the script, select my objects for export and click on the select export dir button <Select>, nothing happens. Only after exporting to the default path am I then able to select a path.
Thanks, it's a bug in Blender's BPy introduced in 2.37. I'll write a workaround.

Revision 1.4 should work.

dermont · Post by **dermont** » Tue Jun 07, 2005 2:04 pm

Works fine, thanks.

Post by **nfz** » Sun Aug 14, 2005 9:06 am

I finally got around to merging my Blender to Lua scene exporter with the GUI portion of ogredotscene.py. Really nice job on the GUI classes Reimpell.

Here are some notes on some things I found in ogredotscene.py.

I noticed that when exporting a scene that has entities parented to another entity, the child entities get exported twice in the dot scene file. I traced the problem back to ObjectExporterTreeIterator class. In the next() method, self.stack.extend(exporter.getChildren()) adds on the children to the stack but ObjectExporter.export() already iterates through the children therefore double output for children.

I commented out the line that had self.stack.extend(exporter.getChildren()) and no more double export of children.

Output of position and orientation for scene nodes does not take into acount the different axis between Blender and Ogre but I don't use the dot scene loader so this may not be a problem in the dot scene loader since it may use the same format for position and orientation as Blender. I do the following in the exporter so I can read it directly into Ogre format:

Code: Select all

matrix = objectMatrix*inverseParentMatrix
# position
pos = matrix.translationPart()
fileObject.write(self._indent(indent+1) + \
  "<position x=\"%.6f\" y=\"%.6f\" z=\"%.6f\"/>\n" % (pos.x, pos.z, -pos.y) ))
# rotation
rot = matrix.toQuat()
fileObject.write(self._indent(indent+1) + \
  "<rotation qx=\"%.6f\" qy=\"%.6f\" qz=\"%.6f\" qw=\"%.6f\"/>\n" % (rot.x, rot.z, -rot.y, rot.w))

Post by **nfz** » Sun Aug 14, 2005 9:23 am

I guess I should have read this thread all the way through ie page 2. The parenting problem had already been picked up and you used a slightly different fix to the problem ie changing self to self.rootExporterList. But then overriding __iter__ for ObjectExporterTree class is a waste of code since it never gets used

.

It turns out that I was at rev 1.3 of the exporter instead of 1.4 in cvs, I thought I updated before starting the merge of the projects. All well, I learned more Python and Blender python API so it wasn't a waste.

sgrgc · Post by **sgrgc** » Tue Aug 30, 2005 12:49 am

it is a good plugin.
you can post it to elysiun forums so they can help too

RCRuiz · Post by **RCRuiz** » Thu Sep 08, 2005 6:03 pm

It will sound a little out of subject but, why not write your blender scene data (ligth, camara, mesh, etc) directy on to a .h to be load it directly to our application?. No .scene need it.

Un Saludo

Post by **jacmoe** » Thu Sep 08, 2005 6:17 pm

So you want to recompile your .scene loading app for every level?
I don't think so.

RCRuiz · Post by **RCRuiz** » Thu Sep 08, 2005 9:41 pm

mmmmmm let me explaing, the way that I work now (maybe is the incorrect way) is that I do all my models, apply radiosity , apply uvm (if necesary), I create my scene directly using scenemaneger puting extra ligths, camara positions and everything else that my scene need inside of a class and if I need a new scene I create a new class , and so on. All my scene classes are in one .h so the creation and destruction of a "n" scenes are compile only one time.

Now , what I'm saing is that is relativly easy to do a py that create or add info to the .h file.

Yes, I know that I can not modify any of my scenes configuration with out recompile but I do not think thats necesary, do you?

Un Saludos

ogx · Post by **ogx** » Mon Oct 17, 2005 1:54 pm

i found a dotscene export problem:

i think the dotscene script dont export the range of light attenuation of spot and point lamp it is always remain (lightAttenuation range=5000.0)

reimpell · Post by **reimpell** » Mon Oct 17, 2005 2:52 pm

ogx wrote:i think the dotscene script dont export the range of light attenuation of spot and point lamp it is always remain (lightAttenuation range=5000.0)

Blender's "Spot" lamp does only have a "Clip End" if "Buf. shadow" is enabled. The other lamp types don't support clipping and are therefore exported with Ogre's default range.

Marco_ma · Post by **Marco_ma** » Thu May 31, 2007 9:26 am

HI !
I am a student of computer science at the university of Udine and a I love Blender

I try to use Blender whit Ogre.

This is my Workflow

1- export whit dotscene the scene
2- export whit ogremeshexporter the single object (whit Game Material actived)

3 - use OgreXMLconverter from OgreCommandLineTool for convert the mesh.xml in .mesh (cube.mesh.xml in cube.mesh)

This is my first try :

http://linediconsine.googlepages.com/Bl ... ported.zip

but the player based on Ogre say that I have a problem about dotsceneoctreescenemanager.

I never developed the palyer so, I want to undestand where is the problem (exporter , bad work process... etc)

Thanks for helps !

Ogre + Blender sound Great ;D

artheseus · Post by **artheseus** » Sat Jun 09, 2007 3:02 am

Is the exporter compatible with blender 2.44?

I'm getting the following error when trying to export: 'Blender Lamp' object has no attribute 'getName'

artheseus · Post by **artheseus** » Sun Jun 24, 2007 11:11 pm

Hello? Is this thread dead?

Post by **jacmoe** » Mon Jun 25, 2007 4:08 pm

Yes. And not it is locked.

**** locked ****

Ask in this topic instead:

http://www.ogre3d.org/phpBB2/viewtopic.php?t=3360

*stickied*

Ogre Forums

Blender .Scene Exporter

Re: script updated?

Ortho camera mode