editor Q re: aircraft screen

[n01487477]

[*]Firstly, when changing the endurance variable, it is a hit miss affair, all other variables save correctly, this one does not.
[*]Secondly, why is 1-10 device different from 11-20, and why isn't it explained ? why when I change the drop tank in slot 9, and keep a different drop tank in slot 19, 2 different drop tanks are listed when showing the aircraft? I thought as it says

Each Aircraft type may have up to 10 weapon systems. Different arm devices in 2 and 11 will result in device 11 ???

[*]Thirdly (confusion) Lets look at range calculations, unlike witp, where

Code: Select all

int maxRange = (ac.GetEndurance() + droptank) * ac.GetCruiseSpeed() / 3600;
 		int normalRange = maxRange / 4;
 		int extendedRange = maxRange / 3;
 

According to the new editor manual:
Cruise Speed is the normal (cruising) speed (in mph) of this Aircraft type.
Endurance This is the number of minutes the plane can fly before running out of fuel.

So I would assume by changing these variables that the range would change, but realistically it has no correlation to the range settings which we now make manually...(on the right #1)

Taken the example in the pic
@cruise: 230*(450/60) = 1725 miles = 1498 nm..
@full: 336*(450/60) = 2520 mile = 1955 nm..

So it has nothing to do with the cruise and endurance ... only when taking away the figures on the right ... hmmm ?

[*]What are these buttons (#2) for, just to reset to 0? I'd rather it calculate the above...

[BigJ62]

p.10 editor manual "Buttons in all views that are adjacent to fields serve two purposes one is for labelling the field and the
other for quick insert of a value that can be assigned to that button via right clicking. The values are
persistent between application lifetimes.".
 
The range fields actually set range for a/c not the old way from witp. The air team can explain better than I.

[n01487477]

Yeah, but ... I'd rather it properly calculate the field, cause unless you want to adjust each one [&:]???

Secondly, not all planes in scenario use these values and therefore some default back to:

final double mile_to_nm = 0.868976;
double maxMiles = theCruiseSpeed * ((float)theEndurance/60);
double toNM = Math.ceil(maxMiles * mile_to_nm);
double rangeDtMax_temp = Math.ceil(toNM / 40);
theRangeDtMax = (byte)rangeDtMax_temp;

So if the fields on the right override the system why have both ?

Also, what about the editor saving incorrectly ?

[BigJ62]

Not aware the editor not saving correctly, can you be a little more specific?

ORIGINAL: n01487477

Yeah, but ... I'd rather it properly calculate the field, cause unless you want to adjust each one [&:]???

Secondly, not all planes in scenario use these values and therefore some default back to:

final double mile_to_nm = 0.868976;
double maxMiles = theCruiseSpeed * ((float)theEndurance/60);
double toNM = Math.ceil(maxMiles * mile_to_nm);
double rangeDtMax_temp = Math.ceil(toNM / 40);
theRangeDtMax = (byte)rangeDtMax_temp;

So if the fields on the right override the system why have both ?

Also, what about the editor saving incorrectly ?

[n01487477]

As I said in my first line the endurance variable is a hit a miss affair, sometimes it saves at other it doesn't ... maybe its linked to the rng settings ??? 

Another issue where do you define, upgrade options ? like the 1~10 Upgrade values in the DB or cvs files from witpload ?

[michaelm75au]

Endurance no longer affects range, as they are set individually now.
And it can be modified in-game when calculating flight time.

The new 3 range figures (max, extend,normal) should be used, with another 3 to represent drop tank ranges.

Device 1-10 represent normal range weapons, 11-19 weapons at extended range (20 is assumed to be the same engine are 10)

The upgrades are in the drop down list "Upgrade" - it shows 00-10 upgrades.

[BigJ62]

I tested saving nvalues in the editor and it seems to be saving correctly, I'm going to need a very specific example like I put 10 in the field but editor saves it as a 12.

ORIGINAL: n01487477

As I said in my first line the endurance variable is a hit a miss affair, sometimes it saves at other it doesn't ... maybe its linked to the rng settings ??? 

Another issue where do you define, upgrade options ? like the 1~10 Upgrade values in the DB or cvs files from witpload ?

[n01487477]

Thanks MichealM,
Still not all are set individually, and I'm looking at how that effect things, but thanks for the heads up...

BigJ62,
Please have a look at the pictures I supplied, but if that is not sufficient I can wrap up a scenario for you to see ...

Cheers
Damian

[BigJ62]

AFAIK that is not a problem with the editor. How those values are used in game can best be answered by the air team.