help with an assertion error

Users who are viewing this thread

Fujiwara

Sergeant at Arms
If anyone can help with this, you have my deepest thanks.

http://i46.photobucket.com/albums/f127/texan_otaku/oddbug.jpg

Can anyone help decipher this error? As you can see from the picture, I have just completed creating a character, and just clicked done. The overworld map menu can be seen at the bottom, along with the current day. The problem is that this is intermittent, so I'm unsure where to start looking in my Python code. The error states that 'i' should be > 0 but < num_ids, so I get the feeling I've exceeded whatever num_ids is, but I have no idea what, and since it's intermittant, I don't know where to start looking. Help?!
 
I took a look, haven't seen that assertion err before.

What have you changed in your module? That is obviously where you need to start, but if you've already checked that out yourself, you should share that info with us.

sv
 
I've seen it before... I think it might be an ID out of range error, e.g. say you only have 25 kinds of troops "trp_" , and you refer to troop number 28. Go to your scripts and make sure you didn't accidentally swap one of the arguments somewhere.
 
Ive seen it a few times, just cant remember why. I usually only change 2-3 things before I compile, then I always know where the problem is and just go look to see what I f'd up.
 
Maybe it's related to the tutorial triggers, namely the "this is the world map" one. You might try cutting out the tutorial stuff to see if that does it.

EDIT: I'm think this since the exact timing of the tutorial messages fluctuates. If not, it might be some other early trigger firing.
 
Well, I edited out the tutorials trigger, with no apparent change. I also found this error after the first one I posted earlier:

http://i46.photobucket.com/albums/f127/texan_otaku/oddbug2.jpg

This one is beyond me. Data chunks???

EDIT: as an aside, I do have a considerable number of triggers firing at start-up, almost all of them begin variable declaration/initialization. They are simple enough, just the standard:

(0.0, 0, ti_once, [], [(assign,"$variable",value)]),

Could that be part of it? Should I adjust the timing of these?
 
That could well be it. Why do you have those in multiple triggers though? You should be able to have all your declarations and assigns in a single trigger.
 
Right now they're separate for organization's sake, though it looks like I'll have to mash it all together. On the good side, I went through my troops file and found some formatting errors in the skill assignment ('knows_common,knows_trade_3' vs 'knows_common|knows_trade_3') that I'm surprised made it past the complier. After correcting those, stability seems to have improved. And I'm taking AW's advice and making one or two changes at a time before compiling and testing :cool:
 
2 more errors from the same build, at the same place, after the 2 Fuji already listed:

error13ig.jpg

error29td.jpg


This is trying to create a class taht previously would cause a fatal crash with a white screen, but on this third or fourth time, it went into the game as if it were just fine. So I'm wondering if the fatality of these errors depends on the skill distribution, which is the only thing that's likely to be different between the attempts.
 
Back
Top Bottom