Chilli is a plugin for GtkRadiant. It is used to display bezier spline paths in GtkRadiant, and to export them to a SPD (SPline Data) file.

Screenshot

Chilli showing a flyby path on q3f_2machse.

Usage How to use Chilli and the 'path_spline' entity is documented in the Q3F entity docs. I'll put that section out of the docs also here for those too lazy to look it up ;)

path_spline
This entity is used in combination with the Chilli plugin for GtkRadiant to make bezier spline paths.

The fields are:

targetname	Name of this entity, used for targetting.
target	Target entity, this is the next entity in the spline path.
pathname	The name of the spline path this entity is a member off. Chilli and Q3F support up to 16 different paths. (Remark: the path used for the flyby camera ALWAYS needs to have the name 'flyby'.)
origin	Origin of the entity.
dir	Direction of outgoing path. This is a vector key, meaning the value is like "0.2 -0.3 0.6" where the numbers are respectively X Y and Z directions.
speed	In Q3F an entity can follow a spline, from this path_spline entity till the next one in the path, the entity that follows the path will have a speed of 'speed' units/second. Also this is used to control the shape of the path (Try this in GtkRadiant to see how different numbers affect the path).
roll	In Q3F an entity can follow a spline, at this path_spline entity it will have a roll of 'roll' degrees. Positive roll is clockwise, negative is counter clockwise. The entity that follows the path interpolates it's roll between path_spline entities.
lookat	At this path_spline point, the camera will be targetting this static entity. Best is to use an info_null for it.

The path_spline that has spawnflags 1 will be the first entity on that path. At least one of the path_spline entities needs this spawnflag for the path to be valid.

When you've created a path in GtkRadiant, you can use the option "Scan and Go..." in Chilli to see the path in radiant itself. If the statuswindow reports checksum errors, one of the fields above (all path_spline entities in a path must have all of the keys) is missing, the path isn't closed, or an other error has emerged so a path cannot be rendered properly.

To use the paths in a map, use the "Export SPD..." option in Chilli to export a <mapname>.spd file, which can be read by Q3F to use the paths in the code. The SPD (SPline Data) file will be exported to the same dir as your .map file exists in. For Q3F to be able to read it, it must exist in the same directory as the <mapname>.bsp file is in.

History v1.1f
-----
- Fixed a crash bug if you tried to 'Stop' Chilli before it was started.
- Updated plugin interface to GtkRadiant 1.1-TA-beta.

v1.1e
-----
- Added 'lookat' key to path_spline entity.
- Updated SPD file version to 4. SPD file now supports the lookat key.

v1.1d
-----
- Updated SPD file version to 3. SPD file is now in plain ascii.

v1.1c
-----
- Added support for spawnflags 1 to define a path_spline entity as the first of a path.

v1.1b
-----
- Fixed bug with sorting of splines before writing them to the SPD file.

v1.1
----
- Updated SPD file version to 2. It now includes the names of the exported paths.

v1.0
----
- Initial release.

Download Get Chilli from here:

Chilli v1.1f - 51.5KB

To use Chilli you need GtkRadiant 1.1-TA-beta, available from www.gtkradiant.com.

Credits Chilli is coded by Arnout 'RR2DO2' van Meer. Please send me all bugs you can find, suggestions are also welcome.

Special thanks to TTimo, Mickey, Maj, G_DeWan, SmallPileOfGibs and all the others from TF IRC #curry.