Strange Export Error

[andylegate]

Okay, so I'm trying to apply a envmap to my waveset, and now I'm getting an error I've never seen before. It happens at the end of the export, while it's trying to write the texture prp file.

I'm using a .jpg made with a rendered blender pic (I used Blender to make the envmap).

Here's the error from the console..

Code: Select all

@ Saving page Textures -1
Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_Export.
py", line 169, in open_file
    export_age(agename,basepath,selection,merge)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_Export.
py", line 88, in export_age
    page.save()
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_ResMana
ger.py", line 141, in save
    self.prp.write(f)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_File.py
", line 670, in write
    o.writeobjects(buf)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_File.py
", line 423, in writeobjects
    o.write(buf)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_File.py
", line 340, in write
    self.data.write(buf)
  File "C:\Program Files\Blender Foundation\Blender\.blender\scripts\prp_MatClas
ses.py", line 2215, in write
    self.fFaces[i].write(stream,0) # "Really" is set to 0, to avoid writing hsKe
yedObject code
IndexError: list index out of range


[D'Lanor]

IndexError: list index out of range is a common error. The part that looks strange is just a comment.

Since it is a waveset object maybe you did not bother to UV map it. But I guess you have to do that for the environment map.

[andylegate]

Ooooookay. I tired uvmapping the envmap....

And got a different export error, this time at the waveset itself, about no textures being applied to the faces.

Okay, sure, the only thing I had applied was the envmap.

Sooooo. I added a texture too.

And now I'm back to the same error as my first post.....sigh.

[Paradox]

I fixed this error a while back in my contrib version, it was something about the texture not ending up in the Texture.prp file properly, and then PyPRP was trying to write a null object. I suppose I should see if I can actually start merging some of my contrib stuff into trunk.

[D'Lanor]

Has anybody ever made an envmap this way? I think until now we all just let PyPRP create a dummy. I have no idea what kind of envmap ref PyPRP wants but this is what it does.

Code: Select all

...
        # allow ref to alternate envmap
        altEnv = FindInDict(objscript, 'visual.waveset.envmap', None)
        if(altEnv != None):
            # refparser time
            resmgr = self.getRoot().resmanager
            refparser = ScriptRefParser(resmgr.findPrp("Textures"), str(self.Key.name), 0x0005, [0x0005,])
            envmap = refparser.MixedRef_FindCreate(altEnv)
        else:
            # make a dummy dyanmic envmap for the waveset
            envmap = plDynamicEnvMap.FindCreate(self.getRoot(),obj.getName())
            envmap.data.export_obj(obj)
        self.fEnvMap = envmap.data.getRef()
        # now we create a default waveset
...


Edit: oops, crossposted with Dox.

[andylegate]

ah HA!

Not my fault then, okay.

But I stopped holding my breath for a bugfix version, 1.5.1 a LONG time ago. Seems all anyone is doing is for 2.0. Ah well.

[Paradox]

Seems all anyone is doing is for 2.0. Ah well.

Actually, 2.0 is mostly just a concept right now with no functionality at all...

[andylegate]

Okay....uhm.....then I guess I'll ask:

PyPRP 1.5.0 was released back on 03 July. Since then, we've (or at least I) have seen many posts and comments that fix a lot of bugs with 1.5.0.

Any idea when a 1.5.1 is going to come out? The nightly build shows stuff added up until August, then it stopped. Then something back on 25 October, prp_DrawClasses.

Only reason I ask is since last year at this time, plugin versions had been coming out at a fast pace, and then suddenly stopped. Some of us have been wondering is all.

[Nadnerb]

I blame the mythical "2.0" for sucking the enthusiasm out of developing the existing PyPRP... while not really accomplishing anything in itself besides mesh imports.

And also non-summer life for eating up time, and the cancellation of MORE (fine, indefinite hold, same difference) and... the economy for probably setting the conditions that forced Cyan to do that, for which you can blame the bankers who gave out idiotic loans because nobody regulated them, for which.. ah.. yeah.. I blame the universe.

I don't know when anything will be done on PyPRP.. I think dox is the only person to actually change pyprp in the last few months, and it's all been in his personal build that does everything the better more consistent way... but that means that it does enough things differently that it'd be fun quelling the screaming when the wiki doesn't match up with the plugin anymore..... again.

As for myself, I have two pretty large ages that I haven't worked on in months... one made with techniques that have been outdated by the new plugin and would require an overhaul/duplication of effort, and another which looks very nice, but crashes plasma for no discernible reason.

That's a bit of a tangent, have I depressed anyone yet?

[andylegate]

Nah......can't expect everyone to be running around acting like kids with new toys going "Yay!" all the time. We all get into slumps, depressed (especially with Cyan's news, and the world in general), have Real Life interfere, etc, etc.

However, this does bring me back to something I thought of, oh back in the spring when I was chatting with all the devs. "A Handful Of Men"

Okay now that I've destroyed the PCness of that..heheh. Just a handful of people work on the plugin, and while that can make the logistics of it being easier, it does make it at the mercy of people's moods / availability.

Then again, I've never seen any of the Dev's turn ANYONE away that was willing to help and knew what they were doing (so that counts me out, hehehe). I don't know if there are anymore people out there that might be willing to lend a hand, or what the problems that come with that (say Joe Dev has to stop for a couple of months, so Jane Dev offers to help....but Joe's stuff is like short hand that only he understands, and Jane has to figure out Joe's mess first before she can do anything, or make it go further).

You all have put in a tremendous amount of time and effort, basically working magic for those of us that care to learn how to Age build. There is no denying that. So if we whine......well I apologize anyways. I'll still whine though, hehe.

It just feels like we're almost there.....no one can say we aren't like MILES from where PyPRP 0.5 was! At the same time, it feels like we're almost at the top of the mountain....just a few things left to get working, and then we can do just about everything that Cyan was able to do with their plugin and Max.

Sometimes though, it's hard to find the info. Like the Passindex thing......I found a OLD thread, that lead to another thread, that finally lead to Marcello's Journal, where he posted that Trylon had helped him with some Alcscript that helped with transparent objects near wavesets. It's the ONLY place that the info is posted.......