While testing out the functionality of the RECIP ENG DETONATING simvar, I've noted that while it does seem to work, it seems quite slow. Is this a bug?
I've set up an engine with the new supercharger with enough top end boost to significantly over-boost the engine at sea level. I've then set the detonation_onset parameter in the engines.cfg file to ensure that detonation happens if the engine is over-boosted enough. This engine does not have any anti-detonation systems.
The end result is successful, more or less - the engine immediately starts to lose power. However, trying to monitor this event seems difficult, since the simvar [RECIP ENG DETONATING] doesn't seem to trigger until a little while after it's already hugely noticeable that something is wrong with the engine.
Ideally, it would immediately trigger the simvar, even a few seconds before the engine failure. This would allow detonation effects such as sounds to be triggered, giving the pilot a warning that something REALLY bad is about to happen.
On the same subject, I've noted a similar behavior with the RECIP ENG NUM CYLINDERS FAILED simvar. After the engine has completely stalled, the number slowly starts climbing until all cylinders have failed. Again, ideally, this would be a metered response - if the engine starts detonating, after X seconds cylinders start failing in a staggered fashion, perhaps allowing the pilot to throttle back, and limp to the nearest airport with only a couple of failed cylinders. If this simvar also was immediately responsive, this would allow the sounds to be adjusted appropriately.
Edit: I should also note that the RECIP ENG DETONATING simvar also only seems to work while 'Engine Stress Damage' is turned on in the Assistance Options. While I can understand that this option should allow for the user to turn on or off engine failures, the effects of detonation is something can could still be monitored and acted upon (via sounds, effects) even if outright engine failures aren't desired by the user.