The frameStart and frameRate have to do with animated textures. I would try
0 or -1 for both of those unless you want your beam to be animated.
nHaloTexture is the index of the texture file you want to use for the halo.
I'm not sure but putting this at -1 or 0 might mean no halo.
flLife is the time you want it to live.
The nModelIndex is the model of the texture you want to use.
Look at the IVModelInfo:
//You'll want to make sure your texture file is loaded
g_Engine->PrecacheModel( "effects/laser1.vmt" );
//Then you can get the index of it via the GetModelIndex.
modelinfo->GetModelIndex( "effects/laser1.vmt" );
This is a common texture and might already be precached, but it's nice to
make sure.
I haven't tested any of this. But it's my best guess.
Keeper
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Adams
Sent: Tuesday, September 04, 2007 10:19 AM
To: hlcoders@list.valvesoftware.com
Subject: Re: [hlcoders] serverside plugin visible tracelines?
cool, i found that interface for ieffects. but when calling the beam
function, it takes like 10 parameters.
virtual void Beam( const Vector &Start, const Vector &End, int nModelIndex,
int nHaloIndex, unsigned char frameStart, unsigned char
frameRate,
float flLife, unsigned char width, unsigned char endWidth,
unsigned
char fadeLength,
unsigned char noise, unsigned char red, unsigned char green,
unsigned char blue, unsigned char brightness, unsigned char
speed) = 0
i cant find any documentation on what modelindex, haloindex,
framestart, framerate, flLife, etc mean. If i try to run with just 0
values and make a beam, nothing happens, if i try to put a 1 in model
index the game will crash when i make a beam. does anyone have any
info on how to use this?
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
