The modification of
COMBATFS.CFG "COLLISION_SECS=-2" is not clear. It
appears to affect collision distance, but I'm not entirely convinced of that. It may just modify the frequency at which the game verify the possibility of a collision between aircraft, hence giving the impression that two a/c passing-by each other at high speed are less likely to go boom!
AAC uses the "Head to Head" (H2H) "fix". The readme file says;
Below are the sizes of the stock collision bubble and the size that they will be changed to by this file:
Stock AC Stock Size H2H Size
B-17g 15 (0Fh) 06 (06h)
B-24j 16 (10h) 06 (06h)
B-25j 10 (0Ah) 05 (05h)
bf109e 06 (06h) 04 (04h)
bf109g 06 (06h) 04 (04h)
bf110 09 (09h) 05 (05h)
C-47 14 (0Eh) 06 (06h)
Do17z2 10 (0Ah) 06 (06h)
FW190a 06 (06h) 04 (04h)
He111h 11 (0Bh) 06 (06h)
Hurricane MkI 06 (06h) 04 (04h)
Ju87a 06 (06h) 04 (04h)
Ju88a 06 (06h) 04 (04h)
Mosquito 08 (08h) 05 (05h)
P-47D 07 (07h) 04 (04h)
P-51D 06 (06h) 04 (04h)
Sopwith Camel 05 (06h) 03 (04h)
Spitfire MkI 06 (06h) 04 (04h)
Spitfire MkIX 06 (06h) 04 (04h)
Tempest 06 (06h) 04 (04h)
V1 05 (06h)??? 03 (04h)
As you can see Ivan, these numbers are more conservatives than yours.
I know that I have used "1" with my jeep project with very good results; smilo and I were making "near head to head" passes during tests.
The nature of the collision "bubble" is also debatable; is it really a "bubble"? Could it be a "box"? The fact that only one number is involved would suggest a radius measurement. But we may be wrong.
I also wonder if distances are the same on the ground and in flight. I don't know if its only me, but it looks like they're is a change, especially in MP games, between a/c seen rolling or flying from the outside view.
AF99
always sets the model at "5". Hex-editing is therefore a "must" for any serious modeler. That said, my Taifun is actually still at "5"...
The next a/c I release will not! But I'm still far away from any a/c release.