Quote:
|
Originally Posted by suBB
:hmm: That was my reason for saying that the ‘suicide run’ basically is an attempt to make visual ID based on radar return of a non-emitting contact. The solution is a strategic / tactical work-around, basically redefining how red taskforce can do without the bear & EW and remain just as effective if not better. The workaround also resolves possible issues in playability where blue surface were being engaged at time of spawn from over 100s of nm with ASMs in response to a linked contact. Now that option is available for both sides really, before it wasn't an option at all.
|
I did some tests regarding 'crappy Air platform AI' in the past and created some mission-specific doctrine files. The problem is of course, that there isn't currently a tool which supports the user of your mission to swap between different doctrine files (like JSGME does it with LWAMI).
Perhaps mission specific doctrine files could support you in:
- switch on/off dynamically the radar or other sensors
- force the bear to turn away from specific platforms (to avoid 'suicide IDs attempts)
I've posted some doctrine snippets which make air to air combat more realistic:
http://www.subsim.com/radioroom/showthread.php?t=123401
In the past months I didn't have time to do further experiments but wanna get back to DW. If I remember it correctly I used for example the altitude/speed of the plane to 'communicate' between scripts and doctrine files. For example if I want to toggle radar on/off I set a very specific altitude for a short timeframe which is interpreted by the doctrine file.