Rev 119 export errors

Announcements and discussion regarding any projects related to Cyan Worlds' Plasma Engine including (but not limited to) CyanWorlds.com Engine, Drizzle, OfflineKI, PyPRP, and libHSPlasma.

Rev 119 export errors

Postby D'Lanor » Tue Apr 01, 2008 5:27 pm

I downloaded the "bleeding edge" PyPRP version. When I tried to export my age there were the following errors.

In alc_DrawClasses.py: 2 indentation errors, lines 1181 and 1187

After I fixed those the export stopped dead at:

Code: Select all
Traceback (most recent call last):
  File "<string>", line 173, in open_file
  File "<string>", line 88, in export_age
  File "D:\Blender\.blender\scripts\alcresmanager.py", line 602, in export_all
    plDrawInterface.Export(self,obj,scnobj,name,SceneNodeRef,isdynamic,softVolumeParser)
  File "D:\Blender\.blender\scripts\alc_DrawClasses.py", line 1552, in _Export
    drawi.data.export_obj(obj,SceneNodeRef,isdynamic,softVolParser)
  File "D:\Blender\.blender\scripts\alc_DrawClasses.py", line 1771, in export_obj
    pmat.data.export_mat(mat,obj)
  File "D:\Blender\.blender\scripts\alc_MatClasses.py", line 564, in export_mat
    self.FromBlenderMat(mat,obj)
  File "D:\Blender\.blender\scripts\alc_MatClasses.py", line 433, in FromBlenderMat
    animlayer.data.FromBlender(obj,mat,mtex,chan)
  File "D:\Blender\.blender\scripts\alc_MatClasses.py", line 2545, in FromBlender
    frame = alc_AnimClasses.hsMatrix44Key()
AttributeError: 'module' object has no attribute 'hsMatrix44Key'
"It is in self-limitation that a master first shows himself." - Goethe
User avatar
D'Lanor
 
Posts: 1980
Joined: Sat Sep 29, 2007 4:24 am

Re: Rev 119 export errors

Postby Robert The Rebuilder » Tue Apr 01, 2008 5:36 pm

Those two lines you mentioned in alc_DrawClasses.py are in plDrawableSpans.import_mesh() and are not used for export. Was it alc_DrawClasses.py, or another file?
Can we rebuild it? Yes, we can - here's how.

MOULagain KI# 1299

Myst Movie coming soon - spread the word!
User avatar
Robert The Rebuilder
 
Posts: 1383
Joined: Sat Sep 29, 2007 7:24 am
Location: Virginia, US

Re: Rev 119 export errors

Postby D'Lanor » Tue Apr 01, 2008 5:47 pm

Could be. I always delete the pyc files when I update so I guess Blender was rebuilding those for alc_DrawClasses (due to importing this module) when I exported.

Edit: Weird. The second problem fixed itself when I restarted Blender. There is still something fishy about the module imports I suspect.
"It is in self-limitation that a master first shows himself." - Goethe
User avatar
D'Lanor
 
Posts: 1980
Joined: Sat Sep 29, 2007 4:24 am

Re: Rev 119 export errors

Postby Paradox » Tue Apr 01, 2008 6:22 pm

I did move quite a few of the import statements to the bottom of the file as suggested by a few people on the forum (D'Lanor included if I recall). It's possible that I might have moved one of the wrong ones, but alc_AnimClasses.py has always had some issues of its own.
"And one day I woke to find the future held no place for me. I was unwanted in a world, that with my hands I'd helped to build. Where once was honesty and pride, I now stand broken and alone."
Paradox
 
Posts: 1261
Joined: Fri Sep 28, 2007 6:48 pm
Location: Canada

Re: Rev 119 export errors

Postby D'Lanor » Wed Apr 02, 2008 1:58 am

No, that was not me. I don't like imports at the end. And apparently it did not solve anything.

What we have learned now is that these errors occur only after a fresh installation. So next time this happens to somebody we can give the workaround to restart Blender and try again.



The indentation errors are fatal and need to be fixed though, if that wasn't done already (I cannot check since I am at work).
"It is in self-limitation that a master first shows himself." - Goethe
User avatar
D'Lanor
 
Posts: 1980
Joined: Sat Sep 29, 2007 4:24 am

Re: Rev 119 export errors

Postby belford » Wed Apr 02, 2008 9:03 am

Moving the imports to the end was my comment. You may not like it, but in some situations of two-way importing, it's necessary.

(That is, the solution may require it. I'm not saying "blindly move all the imports", because that can cause different troubles. Or just not work, if you don't move the relevant ones.)

The "fresh installation" thing is probably because Python writes a .pyc file the first time it successfully imports a file. So if you import starting at the right point, and it works, you're fine after that. But you still have a bug. Either figure out how to make it work the first time, or get Blender to import the right module first.
belford
 
Posts: 344
Joined: Sat Sep 29, 2007 7:18 pm


Return to Plasma Development

Who is online

Users browsing this forum: No registered users and 2 guests