Trying version 2.0.4.0.

That's unbelievable! Not only the bug of radius of action remained, but now was even worsened!

I invented a work-around to make compatible the odd way to compute radius of action of Asura's Dgen_mod with reality by reducing to 40% the full range (measured in game). So a Fw 190A, for instance, gets a 226 km of full range and will have a drop tank when target distance is beyond 226/2=113 km (this is the odd way DGen_mod computes radius of action, but I can't change it!). Indeed, it gets the auxiliary tank, but the target may be far beyond also of the extended range!

In a

*transport intercept* mission, I got target at more than 200 km, when the

*DGen_mod.log* file reads: "range 226 km - DT need - set DT type 1 - new range 349".

**349**! And HOW it should reach a target at 217 km and RTB (for a total of

**434** km - not taking in account idling over the target) with 349 km of range?

If only it would have got the

two drop tanks set (available for Fw 190A)! But it looks auxiliary tank sets are given randomly, and not relevant to distance.

Can't understand why to add a lot of gadgets (like Rhubarbs operations, which I was unable to get working, though) while neglecting to fix old bugs like this; on the contrary, adding new ones, like

*Scramble* missions no more picked by generator (only

*ScrambleO* missions are seen now, but they cause the complete blockade of my rig, forcing me to turn it off to get out).

Curiously, Asura continue visiting this forum (last time was yesterday), but giving no assistance!