[WMCoolmon]

Originally posted by Kalfireth
That just doesn't look very realistic. I mean... there's no obvious reason for the shockwave to go from white to light blue and then suddenly to orange and dark red. It just doesn't seem to merge very well.  

It's half-scientifically sound, since red-orange-light blue is the order of low energy->high energy.

[Scuddie]

By that statement, the blue should be on the outside, and the orange red be on the inside, no?

[TrashMan]

too many colors = too cartoony.

Hell the beam cannons and turrets, shields and engine glows are enough.

Now there's flak color, explosion color, shockwave color and God knows what's next!

Window color? Cockpit color? nebula trail color?

[MetalDestroyer]

No, space color, ships color :nerd: :crazy:

[DaBrain]

I love the coders.

All shockwaves work 100% correct now:

Try this build.
http://www.hard-light.net/forums/index.php/topic,34181.0.html

Happy.

[MetalDestroyer]

Should we need your tbl file from the first released or not ??

[Psychonaut]

So i´m just comming from my two-week vacation and DaBrain makes it look like a whole new game again. I swear, i will never play FSOpen without these shockwaves again AMEN.

[Boomer]

too many colors = too cartoony.

This coming from the people who included a cell shading feature in FSO?

[DaBrain]

Originally posted by MetalDestroyer
Should we need your tbl file from the first released or not ??

Well, I use it.

I've not investigated this issue though.

[Flaser]

Originally posted by Scuddie
The blue one looks awesome, but it also looks like it doesn't belong.  The orange/red one looks awesome, but it also looks overwhelming.  I still think that if you put the two together, it would look perfect.  A redish orange flaming head of explosion followed subtley by a blue trail would work perfectly, IMO.

EDIT:  I was thinking of something like this:

Kalifireth, actually that's the most realistic shockwave I ever saw.
Closer to the epicenter, the matter is hotter, therefore it produces more high energy emission (ergo lower wavelenght, ergo closer to the blue part of the spectrum).

[Fineus]

Then I don't like reality

But that's my personal taste. Doesn't matter. Go ahead and do what looks / works best.

[Ace]

I actually like it. More or less accurate, and reminiscent of both the blue FS1 shockwaves and the firey ones now popular.

[MetalDestroyer]

Hey Dab, i found a little bug in Open GL when playing in Nebula.
I don't know why i got that, but i just have the model, the ani doesn't work very well in nebula.
In this picture, i use the Red Shockwave. I didn't try to play with the blue one.

Take a look :

[Scuddie]

I would actually say that looks pretty awesome in nebulae...  If not for the large opaque figure in the 2nd pic.

[WMCoolmon]

DB: What are the table changes that I need to do to have the 3D shockwave working right (The blue one?)

Actually, my plan is to have this effect for missile shockwaves, and the blue 3D effect for ship shockwaves, so there may be some combining needed. mv_adveffects hasn't been lagging enough lately.

[FireCrack]

I think it would be best to go the other way around, because GTVA missiles (bombs atleast) are said to use antimatter warheads and i always imagined an antimatter shockwave as being blue-white. But that's why tables are so modifiable i guess.

[DaBrain]

@MetalDestroyer It works fine for me, but I use D3D. I'll try OpenGL.

This problem only appears in nebula missions?
It's probably a code bug then I fear.

Originally posted by WMCoolmon
DB: What are the table changes that I need to do to have the 3D shockwave working right (The blue one?)

Actually, my plan is to have this effect for missile shockwaves, and the blue 3D effect for ship shockwaves, so there may be some combining needed. mv_adveffects hasn't been lagging enough lately.

Well, I didn't change much... I've only edited the 'shockwave speed' value in the ships.tbl, but I'll have to tweak that a bit for the 3d shockwaves I think.

It's shouldn't require any other table changes.

Maybe mutliple shockwaves require entries in the weapon_expl.tbl, but I don't know. You're the coder.


Edit: I think I can approve the bug MD found.



The distance to the shockwave seems to affect the opacity.

[WMCoolmon]

Well, multiple shockwaves are in as of the latest build, and should be a simple matter of specifying "$Shockwave name:" as the very last shockwave variable in any ship or weapon entry that supports shockwaves. Should behave exactly the same except you can use shockwaves other than "shockwave01".

Of course there's a max of 8 different shockwaves per mission, including the default.

[taylor]

Originally posted by MetalDestroyer
i found a little bug in Open GL when playing in Nebula.

Caused by fogging.


@WMCoolmon:  I'm not going to have time to test this any time soon so I'll pass it off to you since it's your code.

Add MR_NO_FOGGING to the shockwave model_render() flags and see if it helps.  You'll probably want to test it in D3D too just to make sure it doesn't do strange stuff there but I don't think that it will.  This is basically the same problem as the laser nebula render error which only seemed to hurt OGL before.  Just making sure that it's rendered without fog should be enough to fix it.  Non-model shockwaves are rendered without fogging already but POF versions will have fog turned back on before render unless you tell it otherwise.

[WMCoolmon]

Added it to CVS...don't know if it'll fix it, but i doubt it'll break it since I already use it in the lab.