|
Cuda's WB Resources | Custom Gunsights |
You can customize the gunsight reticle in WarBirds. All planes will default to the original "cross" reticle unless a custom reticle is specified for a particular plane.
Custom gunsights are defined in text files which are named using the same naming conventions as the aircraft's art files, using a ".gst" extension (for example, p381.gst or p383.gst for a custom P-38 Lightning gunsight in 640 or 1024 resolution, respectively).
A defgst1.gst (or defgst3.gst for 1024 resolution) file can be placed in your directory to define a custom gunsight for all planes without their own specific gunsights. For example, when you choose a plane, WarBirds will first look for a custom gunsight with that plane's name. If it finds none, it will then use the defgst1.gst or defgst3.gst if present. If it does not find that, the plane will use the original standard "cross" reticle.
If you ask the experts for advice on how to create a good gunsight most will agree that you should include a center dot to help you finetune your aiming. They also frequently like to have some aiming points for deflection shooting and ground attack as well as marks to help them determine range etc.
A) Steal - Go to the Gunsight Gallery and pick out one you like. Copy the source code into a text document and save it in you WB directory... For more specific instructions on file names etc, see Custom Gunsight Help.B) Assemble from components - Use the Gunsight Toolkit and copy the source codes of the pieces you'd like into a gunsight file. Make sure to check for instructions on file syntax, file names etc. in the Custom Gunsight More Help.
C) Write from scratch - There are several applications out there that give you a "GUI" interface for designing your gunsights. You can also write the code from scratch in any text editor. For a list of editors, click here. Detailed instructions on how to write the code from scratch can be found in the Custom Gunsight More Help.
The Gunsight Gallery Maintained by Cuda