dirkdeftly

9th January 2003 06:12 UTC

I think this deserves a "PLZ HLP!!!1"
Okay...Here's the story:
I was working on this preset (Fistfight) for about an hour last night, getting everything nice 'n perfect, and while checking it, I switched from docked to windowed mode. Winamp crashed. Note that I was not editing code or adding any components or refreshing an editor window or anything like that - I was switching window sizes. This shouldn't cause any anomolies in the actual calculations (since I don't have any size-change triggered events). I reopened it, and it was on another one of my presets - the preview from TFF2.0, if anyone's interested - and Winamp crashed again. Assuming it was a problem with AVS and not my presets, I restarted. The preview from TFF2.0 works now, but Fistfight still didn't. I checked for too many variables and/or division by zero - there was none. I tried deleting vis_avs.dat, it didn't work. Can someone please tell me what's going on - if there's a problem with the preset (and if so, what), or if it's just my system?

anubis2003

9th January 2003 12:13 UTC

It crashed on my computer too. Said something about colormap. To tell you the truth, I don't know why it is crashing.

nixa

9th January 2003 19:34 UTC

Works fine for me. The only asumption I can make is that there is some resolution bug in the colormap.
Btw. its a very nice preset.

dirkdeftly

9th January 2003 19:48 UTC

how can you tell? were you able to get it running?
i really want to figure out how i can get it running, at least temporarily, so i can fix the problem; right now AVS crashes when I load it.

<edit> This is really starting to piss me off: I moved colormap.ape out of the AVS directory (so it wouldn't load), and the preset worked fine. I proceded to delete the Colormap entry, and it continued to work just fine. However, when I remade the Colormap, it worked fine while i was watching it - but once I tried to restart it, it crashed! Does anyone have any idea how I can fix this??? </edit>

<edit2> The saga continues. I was just able to load the preset without a problem, and reset it, and change window sizes, and everything. Even under different songs. Ay'm sho kunfyuszhedd.... </edit2>

<edit3> Well, it crashed again, but this time I was editing the superscope. I guess I'm not gonna do that anymore. </edit3>

Tuggummi

10th January 2003 07:32 UTC

Atero, my preset "White Frame" originally had a colormap, but it crashed every time i tried to open it. While i was editing it it worked fine and the colormap would work fine, but save it and re open it and it would crash. Renaming the colormap, taking away the "unknown render" away while at it seemed to be the only way to remove the colormap and make the preset work again.

I don't know the solution, but the problem seems to be the colormap. Just don't use it :p

dirkdeftly

10th January 2003 14:03 UTC

yes, well, the problem is: colormap rox. and i wouldn't want to have to bug unconed into debugging it, since he's pretty much dropped AVS entirely (as far as I can tell) and has moved on.
(read: i want to find an easy solution that will let me be confident in the fact that i can release this preset (which, if you haven't noticed, kicks ass) without people bitching at me cos it freezes.)

UnConeD

10th January 2003 16:39 UTC

Try http://acko.net/index.php?or=3 , it *might* work better.

dirkdeftly

10th January 2003 19:22 UTC

Ahh, okay, I thought you'd deserted us ;) (hadn't seen you 'round for quite a while - well, a few days, but still!)

Didn't work any better - I think that's the version I had before :(

Zevensoft

11th January 2003 10:31 UTC

Here's some bytes from the start of the color map, it seems there might be a stray byte.

h[243][217][3]
Color Map[0]
[0][0][0][0]
[0][0][0][0]
[0][0][0][0]
[0][0][0][0]
[0][0][0][0]
[0][0][212][2]
[0][0][4][0]
[0][0][0][0]
[0][0][1][0]
[0][0][0][0]
[0][0][1][0]
[0][0][3][0]