[General Battuta]

see above

[Shivan Hunter]

Often, the effect starts [long] before the beam hits a ship (sometimes, at ranges of several klicks, there's no beam effect at all- just an explosion, with a beam that seems to be 'pointing' at it). Honestly, either the beam itself has to attenuate to the point that it's not destroying a juggernaut at the end of its range, or the effect should be removed.

Good effect on paper but at long-range it just doesn't work out well.

[Hero_Swe]

This needs to be taken out of BP AND the MVPS. I mean who in their ****ing right mind decided this was a good thing?!

[Hippo]

awesome when the distance is right, but terrible when it isn't

[Mongoose]

Blech.

[Klaustrophobia]

i didn't even notice this effect was there, so i guess that makes me neutral by default.

[Snail]

I haven't been a large fan of it.

[Rodo]

Should cut also the range of the beam, if that's not gonna be done then the beam should remain visible.

[blowfish]

Should cut also the range of the beam, if that's not gonna be done then the beam should remain visible.

In this implementation, beams begin to fade beyond their maximum targeting range.  Damage ends where the beam ends.

[Colonol Dekker]

Does not like.

[Qent]

IMHO the fade effect should be detached from the +Range of the beam.

EDIT: Oh this is BP FSU not SCP. Oh well I still want that.

EDIT2: Moved.

[General Battuta]

Can someone confirm that beam fade is in the MediaVPs?

If so could it please be removed in a hotfix ASAP? This is a critical compatibility issue.

[Fury]

No it is not, not any less than any other changed tbl or tbm since .10. Beam fade is good, it would be better when we actually can control fading. 30km long beams is ridiculously stupid looking.

[Fury]

IMHO the fade effect should be detached from the +Range of the beam.

This is the only sensible post in this topic so far. Yes, control for beam fading has been requested but no work on it has been done yet.

Alternative to this are 30km long beams, which look even more ridiculous.

[NGTM-1R]

Alternative to this are 30km long beams, which look even more ridiculous.

Yes, because it's not like any campaign ever relied upon the supposedly limitless range of beams or anything!

Derelict didn't do that at all!

[Fury]

1. Even without limited beam range, tabling in every major version of mediavps may change substantially enough to break older mods.
2. Derelict has not been checked for compatibility and updated if necessary for mediavps 3.6.12. Therefore any incompatibility with beams or otherwise is moot.
3. Derelict can continue using older mediavps without any issues whatsioever, as long as you yourself bother keeping them around.

[The E]

Just because the mediavps can break compatibility doesn't mean they should. In cases like these, where the desire to improve the visual quality collides with the desire to keep the gameplay intact, the gameplay should always take precedence.

[Fury]

Yes, but only retail campaign gameplay and compatibility if you ask me. Accounting for every possibility what mods may have done doesn't seem like a sane idea. If mods want to do things certain way, tbm's are there for that.

[pecenipicek]

if you are asking me about what breaks the game more for me is those thrice damned flashes on EVERY DAMN EXPLOSION!


i prefer my bombs not blinding the **** out of me.





as for the beams at hand, this feature is a needed one for TAP, so yeah

[Qent]

* Qent prefers 30 km-long beams.

But I think the "compatibility issue" is that the MediaVPs change balance to create a visual effect (since retail beams did full damage out to 30 km).