Community project: AlliED "unknowns" repository

[JeremyaFr]

"Class.txt" and "Conds.txt":

AlliED_modified_files.zip

[Darksaber]

Thanks Jeremy

[ual002]

I think the changes to Allied for my escort order functionality might have to be an in engine change by Troy himself. Otherwise, there is a ticket submitted to YOGME 's github to include that in a later release.

[JeremyaFr]

Hello,
I've created a pull request to include the changes made to Class.txt into YOGEME:

• https://github.com/MikeG621/Platform/pull/1
• https://github.com/MikeG621/YOGEME/pull/19

[Bman]

ual002, thanks so much for testing and documenting all that new information. Does Troy D. answer e-mails ? If he doesn't bother with his program anymore, maybe he can give his sourcecode to XWA community so maybe Jeremy or someone else can update and recompile AlliED. My in-laws are here through April so my free time (XWA) is very limited a/t/m, but I'm looking forward to testing your discoveries with TFTC. Thanks.

[spamad]

Hello all,

I have been experimenting with proximity triggers in custom missions using Allied. After searching the forums, I could not find a definitive list of percents vs distance, so created a scenario that would allow me to work them out.

An A-Wing was positioned at distance from a Nav Buoy, and slowly flown towards it. Multiple X-Wings with the following arrival condition were then created:

[Percent] of [Flight Group]
[A-Wing Blue] must [Be In Proximity Of (AllDestroyed)]
[0] [HSN/B Buoy]

As the A-Wing passed each Percent, it triggered the arrival of an X-Wing.

The highest number in Allied’s ‘percents.txt’ (50) caused the X-Wing to arrive when the A-Wing was at 21.0km from the Buoy. There is a linear decrease of 0.5km per ‘percent’ e.g. 49=20.5km, 48=20.0km etc. At 1.0km, the scale changes, decreasing at 0.1km per ‘percent’. The scales changes once again between 75% and 100%.

I have not experimented with the use of Global Groups or Global Units, but the triggers worked consistently when using Flight Groups.
Here is the full list of percents vs distances tested:

100% / 0.05km
75% / 0.1km
50% / 0.2km
25% / 0.3km
At least one / 0.4km
All but one / 0.5km
The special craft / 0.6km
All non-special craft / 0.7km
All non-player craft / 0.8km
All player craft / 0.9km
10 / 1.0km
11 / 1.5km
12 / 2.0km
13 / 2.5km
14 / 3.0km
15 / 3.5km
66% / 4.0km
33% / 4.5km
Each craft / 5.0km
19 / 5.5km
20 / 6.0km
21 / 6.5km
22 / 7.0km
23 / 7.5km
24 / 8.0km
25 / 8.5km
26 / 9.0km
27 / 9.5km
28 / 10.0km
29 / 10.5km
30 / 11.0km
31 / 11.5km
32 / 12.0km
33 / 12.5km
34 / 13.0km
35 / 13.5km
36 / 14.0km
37 / 14.5km
38 / 15.0km
39 / 15.5km
40 / 16.0km
41 / 16.5km
42 / 17.0km
43 / 17.5km
44 / 18.0km
45 / 18.5km
46 / 19.0km
47 / 19.5km
48 / 20.0km
49 / 20.5km
50 / 21.0km

Hope this helps anyone working with proximity triggers.

[JeremyaFr]

Hello spamad,
Welcome.

I can confirm that your list of distances is correct.
In fact, the distance is calculated as follow:

Code: Select all

if( percent == 0 )
{
  distance = 2035;
}
else if( percent <= 10 )
{
  distance = percent * 4070;
}
else
{
  distance = percent * 20350 - 162800;
}

[ual002]

Well done!

Bman, I think it is safe to assume Troy no longer answeres email or supports ALlIED. It would be great to have him back for a once over of his program... Win10x64 compatability without magic, class and Conds.txt updates, No effect variable updates. I'm sure this thread alone could get him moving again. Conversely, YOGME is shaping up to be a powerful editor. It has the potential to outclass ALliED at this rate. I highly recommend giving it a shot and getting active on its github to help iron out issues.

[Bman]

I will eventually. AlliED is my strongest skillset a/t/m.

[ual002]

Same.

[keiranhalcyon7]

I've used both for debugging the XWC missions, and I generally find AlliEd more user friendly, but to be honest everything I've done in AlliEd I could also do in YOGEME (and one particular thing - setting teams to be neutral to one another, as opposed to either allied or enemy - can only be done in YOGEME). They're not that different; the same mission building principles apply, just with a different interface.

[Mark_Farlander]

The highest number in Allied’s ‘percents.txt’ (50) caused the X-Wing to arrive when the A-Wing was at 21.0km from the Buoy.

This sounds interesting.
I've seen that a fighter cannot engage a target (I mean "Attacking target" on the CMD) farther than 21.0 klicks from him.

However, once the fighter has chosen his target ("Attacking target" on the CMD), he doesn't disengage even if such target goes farther than 35.0 klicks.
I've tried a mission with 4 TIE Interceptors pursuing my X-Wing. Of course I redirected all recharges to engines to do the test.

[keiranhalcyon7]

Do you know what that [0] field does? Because a priori I would have guessed *that* would be the range field.

[JeremyaFr]

Hello,
Here is what I found for the escort order formation list:

Code: Select all

0:	-3072	3072	3072
1:	0	3072	3072
2:	3072	3072	3072
3:	-3072	3072	0
4:	0	3072	0
5:	3072	3072	0
6:	-3072	3072	-3072
7:	0	3072	-3072
8:	3072	3072	-3072
9:	-3072	0	3072
10:	0	0	3072
11:	3072	0	3072
12:	-3072	0	0
13:	0	0	0
14:	3072	0	0
15:	-3072	0	-3072
16:	0	0	-3072
17:	3072	0	-3072
18:	-3072	-3072	3072
19:	0	-3072	3072
20:	3072	-3072	3072
21:	-3072	-3072	0
22:	0	-3072	0
23:	3072	-3072	0
24:	-3072	-3072	-3072
25:	0	-3072	-3072
26:	3072	-3072	-3072

The data is written at adress 0x05B6E48 (1B5A48), 0x05B6E80 (1B5A80), 0x05B6EB8 (1B5AB8).

[ual002]

THAT SWEET SWEET RAW DATA.

I came up with this, checking against my best observations to create a spreadsheet I think I have an understanding of the anchor points as they translate.
https://docs.google.com/spreadsheets/d/ ... sp=sharing



If any more numbers have data I will gladly translate.

[keiranhalcyon7]

Interesting... three fields with three possible values each suggests 27 rows. The pattern suggests that the first four rows (0-3) are missing, and should be

Code: Select all

0:	-3072	3072	3072
1:	0	3072	3072
2:	3072	3072	3072
3:	-3072	3072	0

and also that the last row (27) is superfluous (indeed, it duplicates row 13). Are these rows simply missing from the exe's table?

Also, I wonder what the significance of the value 3072 is. Did you guys find a way to control the tightness of the escort formation?

[ual002]

No, on the tightness. My table was never completed.... I just never got down to 0-3 or higher than 27. I tried 44 once and it was a really far out distance... I suspect 3072 is distance from escortee. Updating the spreadsheet with 0-3 Now.

[keiranhalcyon7]

I see the pattern now. Here's an over-engineered cheat sheet.

[JeremyaFr]

Hello,
I've edited my list to include the 4 first rows. I've also removed the line 27 (0 0 0).

[JeremyaFr]

Also, I wonder what the significance of the value 3072 is. Did you guys find a way to control the tightness of the escort formation?

This controls the distance between ships. If the size of the ship is >= 3000, the distance is multiplied by 16.

[ual002]

Ok so this explains why the escort order on large freighters seems to push the ships out really far.

Nice visual representation.

[Bman]

Nice. Ual002, could you update your spreadsheet to reflect Jeremy's final edits? Your spreadsheet with keiranhalcyon7's image above makes a great template to keep for mission editing. Thanks.

[ual002]

I honestly thought I did. Could you explain?

[keiranhalcyon7]

I think he means the picture in your post above viewtopic.php?p=154062#p154062

[Bman]

Yes, I got the spreadsheet. Thank you.