minilogoguy18;5411380It works fine for me without any lag at all, just the trail is too long and i want it applied to only a weapon possibly by making it a line in the sab file.
Again, the lag doesn't apply to everyone, just people with lower end gfx cards.
EDIT: What if it were made as it's own blade color and released with the sword model and it was constrained to use that color? Would others without the model see it?
You can't release a blade color with a saber mod, at least not in this sense (MAYBE in shaders, but I doubt it)
hm I have an idea but that'd require an "If" command in .cfg files sorta like : if saber=soulreaver {if attack=1{cg_sabertrail=1;wait 100;cg_sabertrail=0}
this is pretty wrong , atleast for CFG coding in JA
maybe something like this could work out the requirement would be a "If" command
Sadly, configuration files aren't logical scripts, and the 'wait' command blocks input
to bad if they did we could do so many things or at least make them easier to do
Also easier to break, which is a pretty good reason against it.
Why am I the only person shouting "Hey! Take a useless blade color (such as yellow and replace it with *internalDistortion"?
if you just do a good gfx for the sabertrail it can be a very awesome sword trail. I've seen great sword trails made with jujst the sbaertrail image being edited, no fancy coding
Pwned!;5412397if you just do a good gfx for the sabertrail it can be a very awesome sword trail. I've seen great sword trails made with jujst the sbaertrail image being edited, no fancy coding
There is no fancy coding involved. Just some shader editing. =_=
The internal distortion shader doesn't work like that though. I tried years ago to add a shock wave effect to explosions, but that effect has to be coded.
- 1
- 2