[taylor]

Originally posted by DaBrain
But I'm still waiting for the code fix, so I can release the full frame version.

The code is fixed in CVS.  It was part of the way it determined the frame to show.  It previously based this on the default shockwave animation so the number of frames was based on that rather than what was actually used by the POF.  This made it go over the true number of frames, or it got restricted to that wrong frame count.

We just need a new build now.  I'll try and PM you a link to one later today for testing.  I'm not going to publicly release it since I don't have time to deal with any new problems but it will help you work out any final details for the effect until Goober or WMC releases something.

[DaBrain]

Ok, alright. Sounds good.

BTW I don't know what you did to the OpenGL mode, but it runs a lot better then D3D.

[MetalDestroyer]

Wouaw and Wouaw !!! I 'll try it later ^^

[Cobra]

well, i got them working, but it's not much of a shockwave... i think they're too small...

[DaBrain]

The shockwave is really big... Well, I think you should post screenshot to show me what you're talking about.

[Cobra]

i'm about to do that.

[Cobra]

aha... it's not the shockwave's size, the animation's been reversed.



btw, would it be possible to have the shockwave positions randomize themselves?

[EDIT] hey, i got the same error kietotheworld did.

[DaBrain]

The animation was reversed? No...that can't be...

Can you see the shockwave moving into the explosion, or is it just a flare without an noticeable shockwave?

[Cobra]

a flare with no shockwave.

[DaBrain]

Read kietotheworld's last posting and my answer. Maybe you should redownload the effect.

It's important you delete all files. It won't work if you use the old model, eff or frames.

[Cobra]

i deleted everything and started over.

[DaBrain]

Very odd. It's just a glow map. It should work if other glowmaps work for you...


Did you by any chance copy the frames into the /effects folder?

[Cobra]

no, everything's where it should be.

[DaBrain]

Run a debug build and see if this happens:

Originally posted by taylor
If you were running a debug build it would have been hitting an Assert() from bmpman.

[Cobra]

I got a BMPMan from the debug build saying it's loading the frames and everything, but that's it. also, my computer managed through a slowdown to show me that the little flarey part (look in pic) is the one that expands, not the ring itself.

[DaBrain]

I have no idea how to fix it... I don't get it at all.
Sorry.

[DaBrain]

Ok, the next build release will have a fix for the frame count problem.

I've just tested the build taylor sent me and it works perfect even with the 159 frame animation. (BTW it looks sweet!) (... wait 100+ animation... I guess I should run from the coders )

On the other had I noticed there is still a seam in the effect. Looks like I didn't 100% fix the mapping.



Sorry Raa, I guess I was a bit overbearing.
Well, how can I sure I've fixed it? It look 100% fine in Lith.


Well, I'll work on the final release. It should be ready when the next FSO build is released.

[BlackDove]

By the way.

FRAPS please.

I will never have a computer like yours, so I'd like to see it in full motion please.

[DaBrain]

Ok, I'll take a short clip tomorrow.

And BTW my PC isn't very great. I think it's good, but not that good.


Athlon XP-M 2500+
1,5 GB Ram (I work with images, so that's important)
Geforce 6800LE 128 MB (Slower than the 6600 GT)



Don't worry. I'll release a super-cool looking shockwave for low-end PCs tomorrow. Less memory intensive than the stock effect, but way cooler.

[Cobra]

AWESOME! i have to wait a while until i can get a card with enough RAM (damn thing is $130 and there's only one store in town that has it) to use these things.