Can someone post thier .gsc files that includes FX. I have followed all resources and have come up empty. I even tried setting up the COD4 way to no avail.
Might have something to do with the createart folder???
if it is what goes in there??

You are not the only one having issues. Be patient and build the geos for now.
The treyarch-wiki is not working at the moment so just wait for an update there.

If it makes you feel better I did recreate the stock map set up for my FX by using createfx too and nothing worked.

its good to know others are havin issues.....thought it was me lol

Bug in the public tools for FX?

So far seems like omission at the moment.
No comments from the powers that be yet.

Got it working.
Will post a tutorial tomorrow on my site

Extra thanks goes to sparks for helping me out solving the issues.

4mori_rabbit writes...

does this work for mp maps as well?

post it here too please

I dont know what all these anti-community guys are doing with their "lets keep it secret so others only get head aches". So, to thwart that, here is my method:

As many of you have discovered, attempting to dynamically spawn your FX like we did in COD4 isnt working in COD5 "as is" because COD5 doesnt use the createfx folder. You can completely remove it, or void the GSCs in there and it makes no difference to the map's FX.

That means, that the arrays defined in createfx aren't built and so have no effect on scripts to trigger FX. So, we have to build our own array's using the code IW gave us.

This is from mp_airfield.gsc. I kept the precache FX level definitions used in Airfield, and did this:

main()
{
----------------- snip -----------------------

	createFX( "oneshotfx", ( 1843, 2485, 10 ), ( 270, 0, 0 ), level._effect["mp_fire_medium"], 1 );
	createFX( "oneshotfx", ( 1843, 2485, -10 ), ( 270, 0, 0 ),level._effect["mp_smoke_column_tall"], 0.05 );

}

createFX( type, origin, angles, FXid, delay )
{
	FX_ent				= spawnstruct();
	FX_ent.v["origin"] 		= origin;
	FX_ent.v["angles"] 		= angles;
	FX_ent.v["up"] 			= anglestoup( FX_ent.v["angles"]);
	FX_ent.v["forward"] 	= anglestoforward( FX_ent.v["angles"] );
	FX_ent.v["FXid"]		= FXid;
	FX_ent.v["delay"]		= delay;
	FX_ent.v["type"]		= type;
	
	if( FX_ent.v["type"] == "loopfx" )
		FX_ent thread loopfxthread();
	if( FX_ent.v["type"] == "oneshotfx" )
		FX_ent thread oneshotfxthread();
	
	
}

loopfxthread()
{
	PlayLoopedFX( self.v["FXid"], self.v["delay"], self.v["origin"] );
}

oneshotfxthread()
{
	self.looper = spawnFx( self.v["FXid"], self.v["origin"] );
	triggerFx( self.looper, self.v["delay"] );
}

This gives you this:



That's a medium sized fire FX, and a smoke column billowing out of it.

The code is by no means finished, and is in fact a "WIP", but by this method, you can have a oneshotfx or a loopfx.

You could have the code anywhere. Its organisation can be anything you want. As it is, I kept it at the foot of the GSC, but you could have a seperate FX GSC file, and have the lot in there.

edited on Dec. 2, 2008 05:34 am by Tally