Search the Community

Issue Information ⦁ Issue ID #000030 ⦁ Issue Type Issue ⦁ Severity 0 – None Assigned ⦁ Status 12 – Working as Intended ⦁ Version 2009.083 ⦁ Fixed in Radar LOS calculation errorPosted by Grumble on 21 July 2013 - 01:33 PM Radar LOS is not calculated correctly, radars detect targets over the horizon and LOS. Most recently I observed this in HDS3 9.0, I hoped to be able to "sneak out" my Tel Aviv Hawkeye from under the Damascus SAM umbrella by pairing it with a ground attack a/c. (Otherwise the Hawkeye is spawned at high altitude immediately at take off, which I guess is a compromise for AEW, but a painful one.) The trick works, the Hawkeye-Skyhawk twosome starts at low but Damascus is still detecting them and launches SAMs. The test scenario demonstrates this by launching the pair from Nevatim, load the scenarios as RED, Damascus immediately detects the E-2C at 149nm, well beyond true LOS. The -l radar log confirms the wrong LOS. 100001 search.c:881 - Radar Emitter=Damascus Target=E-2C Hawkeye, TargetRange=149, Radar LOS = (BaseLOS x weather_mod + 128)/256 100001 search.c:882 - Radar LOS of 246nm = (246nm x 256 + 128)/256 --> Radar LOS=60644/256 100001 search.c:888 - A RCS=164 TName=E-2C Hawkeye AName=Damascus Range=149 Die=37 aPD=70 100001 search.c:961 - B RCS=164 ARng=300 Arng=300 SRng=60 Srng=60 100001 search.c:1020 - Detected E-2C Hawkeye with Air Radar of range 300 with PD 70, Roll=37 100001 search.c:1040 - Type and Height of target known Tested with 2009.050,076 and 083, I have not yet installed 086 but I guess the radar model was not changed. Issue-030-Radar-LOS-calculation-error.pdf LOS.zip LOS 1.zip

Issue Information Issue ID #000033 Issue Type Issue Severity 0 – None Assigned Status 23 – Fix Accepted By Reporter Version 2009.083 Fixed in 2009.094 Long range AA missile intercept geometryPosted by Grumble on 26 July 2013 - 11:59 AM Long range anti air missiles occasionally follow very strange and unrealistic intercept paths. Looks almost as if they were flying to a precalculated intercept point and then turn towards the target, which could be normal for long range AA but this behaviour is not consistent (usually the missiles are tracking their targets all the way, see Gammon example) and the intercept points also seem wrong, like too far away, often beyond the target. The targets are often loitering, the problem could be linked to the loitering-at-cruise-speed issue. I could not yet recreate this with a test scenario (tried but missiles work ok in the small test scenarios) but here are 3 examples with battleset scenarios. Phoenixgeom: Group AIA launches Phonixes at group ZNA, missile group ALM flies strange zig-zag course to ZNA, distinctly changing course two times. Phoneixgeom2: Group AIA launches Phonixes at group ZNA, ZNA loiters on high but with 590kts speed (e.g. it's cruise speed) when AIA launches ZNA changes it's course to 48 degree from 209 degree, missile group ALM flies *over* and passes ZNA, then turns back to it. (The missiles' intercept point looks like it could be the point where ZNA could have been if it had been really cruising.) Gammongeom2: Missile group ZLM is attacking AHA, flies to a point where AHA was a minute earlier, then turns to track AHA. Gammongeom1.hp8 is a savegame from 1 minute earlier, before AHA reached it original patrol destination and started to loiter, however I can not recreate the situation recorded in Gammongeom2.hp8. Still the issue can be consistently observed in Gammongeom2. Issue-033-Long-range-AA-missile-intercept-geometry.pdf AAgeom.zip Phoenixgeom.zip

Issue Information Issue ID #000014 Issue Type Issue Severity 0 – None Assigned Status UNFILED Version 2009.083 Fixed in AP gun ammo expended, but remaining ammo it's not "0", is "65473" shots!!!Posted by broncepulido on 13 April 2013 - 09:40 AM Testing the old River Plate 1939 scenario with a modified DB I see after the 280 mm AP ammo in the Graf Spee forward turret should be theorically expended, the remaining ammo it's not "0" AP shots, it's "65473" AP shots, and the turret is keeping fire!!! In the adjunt Word file I've captured some screenshots detailing best the comportment. Also, I included the modified DB I was using (for sake of simplicity, because I think is simply another overflow issue) and a saved game. Issue-14-AP-gun-ammo-expended,-but-remaining-ammo-it's-not _0_,-is-_65473_ shots!!!.pdf Gun Ammo size Error.zip Gun Ammo Amount error 2.zip

Issue Information Issue ID #000032 Issue Type Issue Severity 0 - None Assigned Status 10 - Confirmed Version 2009.083 Fixed in Loiter at cruise speedPosted by Grumble on 26 July 2013 - 10:41 AM Aircrafts loitering at med or high altitude change indicated speed to cruise speed after saving then loading the game or cancelling an attack order. E.g. when the a/c prompts to launch weapons but the player cancels it. (there are probably other situations when this happens, these two are the most apparent) The a/c holds position and Throttle remains at "Loiter" but the Kts number changes to the a/c's med altitude cruise speed. Test scenario, load savegame 1 Group ACA loiters high, speed 405kts, order it to loiter at med (or high), ACA indicated speed changes to 300kts, save and then load the game, ACA speed is 405kts again order it to loiter at low, save and then load the game, ACA speed stays at 300kts load savegame 2 ACA is intercepting ZYA on high altitude and will prompt to launch AAMs in a few seconds, cancel the launch, cancel the "Return home" prompt, ACA starts to loiter but speed is 405kts Change ACA altitude to low before launch, after cancelling ACA loiters at 300kts speed Issue-32-Loiter-at-cruise-speed.pdf LOITER.zip