PPT.ini values are different from Korea…seems off
-
@Red:
What would one expect from a ppt file ?
Detection rng, engagement rng, min abort rng?
Kto if i remember right is engagement range. But it was detection before 4.33.
Plus it May also depend on terrain database.HEH heh……where the Mountains at…
Cheers,
tired demer
-
@Red:
…. Detection rng, engagement rng, min abort rng?
Kto if i remember right is engagement range. But it was detection before 4.33. …Makes sense for several of the SAMs listed, but not for the two or three exception Halcyon points out.
-
@Red:
What would one expect from a ppt file ?
Detection rng, engagement rng, min abort rng?I’m not expecting anything. I just want to know what values they’re using so I can adjust my tactics in ITO.
I didn’t see any documentation in the ITO/Docs folder that outlines these ranges…and if it is there I totally missed it. -
I’m not expecting anything.
I asked because while defining these ranges, we debated which range to use. so the expectation is valid. Some individuals would prefer detection, some others WEZ and some no trespass zone.
On top of all that you don’t want to be too accurate either because that may screw the gameplay.Can’t speak for ITO, but most ranges in KTO were tested. Yet WEZ may also depends on many other factors, altitude, ecm use, etc etc
Finally, the PPT ini is user selectable. some squads use their own value.
So it’s a very flexible thing, and easily overlooked when doing a terrain. but i don’t think we’ll have common value all around the theater spectrum. -
@Red:
I asked because while defining these ranges, we debated which range to use. so the expectation is valid.
Red Dog is perfectly right. SAM RING drawn on pilot’s charts are the engagement ring and not the detection range.
Both depends on actual altitude but detection vary much much much more. Those rings are used to avoid to enter into the missile threat zone.
During Dev, there was also the question about using in-game actual ranges or using the RL published ranges (wich are usualy above in-game range) … The problem here is the in game, the range is more or less always the same wich is not the case IRL because will depends on operators tactics/experience/ability/fear/target speed and geometry/decisional matrix … etc …
IRL, ring are usually the max engagement range of the system (FCR limitation).
-
@Red:
I asked because while defining these ranges, we debated which range to use. so the expectation is valid. Some individuals would prefer detection, some others WEZ and some no trespass zone.
On top of all that you don’t want to be too accurate either because that may screw the gameplay.Can’t speak for ITO, but most ranges in KTO were tested. Yet WEZ may also depends on many other factors, altitude, ecm use, etc etc
Finally, the PPT ini is user selectable. some squads use their own value.
So it’s a very flexible thing, and easily overlooked when doing a terrain. but i don’t think we’ll have common value all around the theater spectrum.Red Dog is perfectly right. SAM RING drawn on pilot’s charts are the engagement ring and not the detection range.
Both depends on actual altitude but detection vary much much much more. Those rings are used to avoid to enter into the missile threat zone. ……
Good points. FWIW, I prefer (nominal) engagement ranges, using in-game values.
I think, though, that Hal is looking for the ITO rationale (since the KTO rationale was explained earlier) to understand the differences and ‘oddities’ in the ITO ppt file.
-
I think, though, that Hal is looking for the ITO rationale (since the KTO rationale was explained earlier) to understand the differences and ‘oddities’ in the ITO ppt file
educated guess:
copy and paste from the KTO ppt file, before 4.33 overhaul. the default KTO 4.32 ppt file had longer documented ranges than 4.33.
What i see from the above comparison make me thing about the 4.32 ppt file (especially the 165 Nm Sa-5 range)
but i’m sure the ITO guys will answer with more precision -
165nm for SA-5, 108nm for SA-12 seems like someone forgot to put a decimal point.
IRL SA-5 nominal max range is about 165NM (it can’t be in Falcon4)
-
I added a third column for 4.32 values to verify my educated guess
4.33 KTO || ITO || KTO 4.32
SA2 109370.083007813 SA-2 (18nm) || SA2 164055.5 SA-2 (27nm) || SA2 164055.5. SA-2
SA3 54211.000000 SA-3 (8.9nm) || SA3 85065.83 SA-3 (14nm) || SA3 85065.83 SA-3
SA4 115446.198730469 SA-4 (19nm) || SA4 182283.9 SA-4 (30nm) || SA4 182283.9 SA-4
SA5 328110.249023438 SA-5 (54nm) || SA5 1002562 SA-5 (165nm) || SA5 1002562 SA-5
SA6 60761.1572265625 SA-6 (10nm) || SA6 78989.7 SA-6 (13nm) || SA6 78989.7 SA-6
SA8 24304.462890625 SA-8 (4nm) || SA8 39494.85 SA-8 (6.5nm) || SA8 39494.85 SA-8
SA9 24304.462890625 SA-9 (4nm) || SA9 24304.52 SA-9 (4nm) || SA9 24304.52 SA-9
10 303805.786132813 SA-10 (50nm) || 10 297730.4 SA-10 (49nm) || 10 297730.4 SA-10
11 72913.388671875 SA-11 (12nm) || 11 103294.2 SA-11 (17nm) || 11 103294.2 SA-11
12 267349.091796875 SA-12 (44nm) || 12 656222.1 SA-12 (108nm) || 12 656222.1 SA-12
13 18228.3471679688 SA-13 (3nm) || 13 24304.52 SA-13 (4nm) || 13 24304.52 SA-13
15 37821.0 SA-15 (6.2nm) || 15 39494.85 SA-15 (6.5nm) || 15 39494.85 SA-15
17 147638.0 SA-17 (24.3nm) || 17 115446.5 SA-17 (19nm) || 17 115446.5 SA-17
19 24304.462890625 SA-19 (2S6) (4nm) || 19 32811.1 SA-19 (5.4nm) || 19 32811.1 SA-19
AAA 48608.92578125 AAA (8nm) || A 48609.04 AAA (8nm) || A 48609.04 AAA
HWK 85065.6201171875 Hawk (14nm) || H 139751 I-Hawk (23nm) || H 139751 I-Hawk
NKE 328110.249023438 Nike (54nm) || N 182283.9 Nike (30nm) || N 182283.9 Nike
P 303805.786132813 Patriot (50nm) || P 522547.2 Patriot (86nm) || P 522547.2 Patriot
ROL 24304.462890625 Roland (4nm) || ROL 26127.36 Roland (4.3nm) || ROL 26127.36 RolandConclusion: it’s a copy paste of the 4.32 KTO PPT file
-
IIRC it’s actually from one of the later 4.33 RCs, can’t remember which.
You can copy and paste 4.33 over if you prefer, just don’t override the custom stuff