[Black Wolf]

Originally posted by Galemp
Willikers.

Is that, like, genuine firey glowy goodness I see?!

Is that genuine, glowey Galemp I see? Where'd you spring from?

[DaBrain]

Originally posted by Raa
Those seams you have are because you need to pull the boundaries of the UV map inward. The effect you're getting is because the edges of the UV snippet are extending past the boundaries of the image, and are displaying the black portion from what would be the left side. (I hope this is understandable)

Ok... I didn't really understand it, but it's fixed now.


I've no idea how to fix the other bug. The maps (frames) that appear after the actual animation are not the files from the maps folder, but maps in the memory. (and glowpoint maps...)

What maps are displayed depends on the player ship. If I use the Ulysses, the Ulysses map and glowpoints appear. If I use the Ares the Aeolus appear.

It's very strange and I'm pretty sure it's a code bug.

[Taristin]

Originally posted by DaBrain


Ok... I didn't really understand it, but it's fixed now.
 

Ok. Hopefully, this'll help you.  Notice how UVing works? While it may normally seem that you are working within the constraints of a single image's borders, it is not that way at all.

The number 1 represents how the image is tiled.

See the green rectangle? Where it overhangs off the edge of the tile? When a peice of UVing overhangs off the edge of the image, it is, essentially, looping over to the begining again. (see the green triangle?)

Now imagine that the blue pie-slice-shaped section is your shockwave's UV selection. If it goes too far over to either the right, or the left, it will, in essense, do just as the green corner did from the green rectangle. Which is why you had the seams. Those seams were the edge of the orange tile abruptly ending, and the begining of the next tile (the same map) which I assume is black.

Understand?

[DaBrain]

Yeah, that's what I figured out.

My main problem is to find the right buttons in the mapping software.


I didn't understand what you ment with the posting before your last posting, but I was able to figure out what to do on my own.
(Yeah, now I feel proud... a bit. )

[DaBrain]

Test release

I need someone to test this. Maybe this will help some coders to find a bug in the code, or it will help my to find a problem with my PC/FS2.

It works best with OpenGL. I got absolute perfect performance with OpenGL. No frame drops. Also this weird bug doesn't appear every time.

But please test OpenGL too.

Note: This is a test release. Unless everything works fine, you should consider to wait. The timing of the shockwave is not very good. I'm still working on the tables. Ah, and I had to delete 50% of the frames...

If you got performance problems, please tell me your system specs.

You should use the newest build (by Goober).

Test release download (Link removed. Please download the second release on the next page)

[Psychonaut]

The shockwave don´t work for me. I´ve tested it in OGL and D3D. It produces the same problem you described above. A huge shockwave (very huge) and some strange flickering with some semi-transparent ship-textures right after the effect. I´ve tried the shockwave.pof from your prior release, but that looks really weird. I´m not really into this stuff, but maybe it has something to do with the .pof??

Sorry, that i can´t help.

[DaBrain]

The old *.pof won't work. It has a different UV map.

Thanks for the testing. I don't think it has anything to do with the pof, but I'll test that.

[DaBrain]

It works fine without the animation.

I think I know the problem now. It's the code change WMCoomlon made. Looks like the animation doesn't have enough frames to work with that correct.

I'll try to add some frame, so the animation has as much frames as the old one had. That should fix it.


Edit: Yeah, that fixed it... now the problem is the timing is pretty much off... hmmm dunno what to do about it. Deleting every second frame is ok, but it's not ok, how it is now.

Edit2: Happy happy.








Edit3:

Test release 2

Test release 2 download
(With better table.)

[taylor]

The frame issue just has to do with WMCoolmon's slight drinking problem.  All of the developers have tried to help him with this but we haven't really had any luck.  I'm planning to get with his family and get them involved.  Hopefully that will be enough to convince him that he does have a problem and to seek help.  Friends can only do so much.

* eagerly awaits WMC's response *


Seriously now...

If you were running a debug build it would have been hitting an Assert() from bmpman.  Basically the change WMC made to keep the glowmap in line with the shockwave progress had it going over the actual number of frames.  This is also why you were seeing a ship texture sometimes.  Easy to fix though so no big deal.  I'll commit it when I get back in front of my workstation later this morning.

[DaBrain]

Still, I'd like to thank WMCoolmon for his help. Without his help, the shockwave effect wouldn't have worked for another few months.


I guess I should run debug builds when I have a problem.
Sounds logical, but I forgot it.

[Kie99]

I've got a problem with this shockwave.  This is all that happens, after this effect flares up, then goes down again, nothing happens.

[DaBrain]

Oh, I see the problem. Wait a minute.

Edit: Ok, delete all shockwave stuff and redownload the test release 2. I've replaced the rar.

It should work fine.

This was just a small naming error.

[taylor]

Originally posted by DaBrain
Still, I'd like to thank WMCoolmon for his help. Without his help, the shockwave effect wouldn't have worked for another few months.

You'll get no argument from me on that.  He's definitely worth his weight in, um, something.  He'll laugh at the intervention joke or hate me for it but it's just a private joke that I haven't played out yet (you'll have to read the CVS commit logs a few months ago to get the joke anyway).  

I guess I should run debug builds when I have a problem.
Sounds logical, but I forgot it.

It does help, especially for mission designers, but I don't think it really would have given you much insight into this particular problem.  You would have known that there was a problem but it wouldn't have helped us fix it any better.

[DaBrain]

Uhm... just a question to you guys. Does the second release work correct?

[Turambar]

it kinda slows me down a little, but this is on my new laptop, i'll try it at home later, see how it works and let you know

im using the 7-28 build

[DaBrain]

Laptop cards often havn't got much video ram. I bet that's the problem.

Shared memory is pretty slow, so if the card runs out of memory, it could cause a slow-down.

Well, don't worry, I'll release an effect that looks pretty good and uses less ram than the stock shockwave.

[Kie99]

The Second release works fine for me, no noticeable slowdown..

[FireCrack]

I experienced slowdowns ith your old 2d shockwaves, but this one runs great!

[AqueousShadow]

Man. Anyone else thinking that one of his shockwaves should be the new splash screen?

[DaBrain]

Originally posted by kietotheworld
The Second release works fine for me, no noticeable slowdown..

Originally posted by FireCrack
I experienced slowdowns ith your old 2d shockwaves, but this one runs great!

Some good news.


The second relaese should work fine. You can all download it if you want to. I just didn't want anybody to dowload a not-working release.

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