Problems with new exporter
by Jay Barnson · in Artist Corner · 02/08/2006 (12:29 am) · 4 replies
I'm getting an error exporting the "example.blend" example:
I am also having problems with my homebrewed models - it's only exporting the highest detail levels, and skipping the rest. I never fiddled with detail levels in the earlier versions of Blender & the exporter, so I don't know if it's a new issue or simply something that I'm doing wrong. I tried to export the example model to see if it worked correctly on that one, but that's when I got the above crash.
I'm also having trouble getting it to recognize a collision mesh. I've done it successfully before with the exporter, so I don't know what's going wrong right now. I'm a n00b, so I may be experiencing standard newbie issues (or just a bad installation).
Using Python version 2.4
'import site' failed; use -v for traceback
Dumping output to file 'C:\gamedev\Media\Pesticidal\example.log'
Exporting...
Dumping output to console
Exception exceptions.AttributeError: "DtsStream instance has no attribute 'buffer8'" in <bound method DtsStream.__del__ of <DTSPython.Dts_Stream.DtsStream instance at 0x0128CCB0>> ignored
Traceback (most recent call last):
File "C:\gamedev\Tools\Blender\.blender\scripts\Common_Gui.py", line 908, in button_event
c.onAction(evt, curMousePos, -1)
File "C:\gamedev\Tools\Blender\.blender\scripts\Common_Gui.py", line 348, in onAction
control.onAction(evt, newpos, value)
File "C:\gamedev\Tools\Blender\.blender\scripts\Common_Gui.py", line 133, in onAction
if self.callback: self.callback(self)
File "<string>", line 968, in guiBaseCallback
File "<string>", line 774, in export
File "C:\gamedev\Tools\Blender\.blender\scripts\Common_Gui.py", line 817, in update
self.cProgress += self.stack[-1][1]
IndexError: list index out of rangeI am also having problems with my homebrewed models - it's only exporting the highest detail levels, and skipping the rest. I never fiddled with detail levels in the earlier versions of Blender & the exporter, so I don't know if it's a new issue or simply something that I'm doing wrong. I tried to export the example model to see if it worked correctly on that one, but that's when I got the above crash.
I'm also having trouble getting it to recognize a collision mesh. I've done it successfully before with the exporter, so I don't know what's going wrong right now. I'm a n00b, so I may be experiencing standard newbie issues (or just a bad installation).
About the author
Jay has been a mainstream and indie game developer for a... uh, long time. His professional start came in 1994 developing titles for the then-unknown and upcoming Sony Playstation. He runs Rampant Games and blogs at Tales of the Rampant Coyote.
#3
02/08/2006 (1:23 am)
Thanks. I just installed Blender to test... and I got the same error message. However after changing the path everyting seems to work fine :-)
#4
He solved the problem with the example easily enough here :)
My problems (I like to report them in a thread like this in case anybody does a search for similar problems) were as follows:
On the collision, I'd accidentally set modeling for double-sided polys. I musta hit a hotkey sequence by mistake, because I wasn't even sure where the double-sided button WAS. Apparently this was interpreted as some inside-out box by the exporter, and thus ignored.
For the detail levels, it was my Failure To Follow Instructions. From the instructions that came with the exporter:
The problem was that I wasn't naming the objects after the template. So even though I had objects under different detail levels, the exporter couldn't tell what object they were a detail level for, and would discard them.
Very Good Stuff.
Jay Barnson
Tales of the Rampant Coyote
02/08/2006 (7:16 pm)
Okay - I just wanted to add another THANK-YOU to Joseph for helping me out by donating his personal time.He solved the problem with the example easily enough here :)
My problems (I like to report them in a thread like this in case anybody does a search for similar problems) were as follows:
On the collision, I'd accidentally set modeling for double-sided polys. I musta hit a hotkey sequence by mistake, because I wasn't even sure where the double-sided button WAS. Apparently this was interpreted as some inside-out box by the exporter, and thus ignored.
For the detail levels, it was my Failure To Follow Instructions. From the instructions that came with the exporter:
Quote:The first detail level (the one with the highest size) is used as a template by the exporter.
All other objects in the remaining detail levels must be named after the objects in the first, and any stray objects will be discarded with a warning.
The exporter determines the template(or DTS Object) name by splitting the object's name using a ".", e.g.:
"myHead" is associated with the DTS object "myHead"
"myHead.001" is associated with the DTS object "myHead"
"glassWindow.001_Sort" is associated with the dts object "glassWindow"
... and so on.
The problem was that I wasn't naming the objects after the template. So even though I had objects under different detail levels, the exporter couldn't tell what object they were a detail level for, and would discard them.
Very Good Stuff.
Jay Barnson
Tales of the Rampant Coyote
Torque Owner Redacted