AFAIK, at this time, loadouts designed for HC are issued from H4 forms or designed by DB... designer.

AFAIK again, there aren't fixed rules about designing, at least, about range and DATA determination.

If AFAIDK, there are rulles, the following wouldn't be usefull at all, but, please, let me thrust that the time i took to design it isn't wasted for nothing.

 

What i suggest it to determine fixed multipliers that will influence DATA and range based on real life values and H4 rules.

So i took the "Performance effects for Turbofans and Turbojets at cruise" issued in the rules book and adapted it.

 

Here is what it gives:

 

% of Max Payload Carried | Range/DATA Multiplier

 

0-15% => *1 (no changes)

16-60% => * 0,8 (80%)

61-100% => * 0,6 (60%)

 

 

What do u think about it?

Is it realistic?

 

Jan

Interesting. Give me an example. Apply your formula to an F-16

Okay, here are the DATA values for the Rafale.

 

Base is 30.

up to 15% of the max payload, nothing change;

above and up to 60%, DATA is reduced to 24;

and from 60% to 100%, DAT is reduced to 18.

 

Now about Range values:

 

Rafale C:

Base range: 1000

up to 15% of the max payload, nothing change;

above and up to 60%, Range is reduced to 800;

and from 60% to 100%, DAT is reduced to 600.

 

Rafale B

Base range: 980

up to 15% of the max payload, nothing change;

above and up to 60%, Range is reduced to 784;

and from 60% to 100%, DAT is reduced to 588.

 

Rafale M, equal to Rafale C. In fact the Rafale M have 15kg less fuel than C version.

After designing some loadouts, it seems that this rules should have more "steps" because there is a hughe gap between 16 and 60% and the loadouts that 59% of the payload only have the same multipliers that a loadout that weight 17%.

IMHO, it should have a step every 20%, or even 10%.

What do u think about it?

Okay, i just redisigned all the Rafale's loadouts (every version) and it seems that dividing payload multipliers by 10% steps are far more accurate than the former solution (0-15, 16-60, etc.)

It results in a better representation of versions differences (between land and carrier based versions, there is now a real difference in loadouts ranges and DATA).