|
bsq -> [FIXED B479][Not Fixed] AMSL and AGL Confusion? (12/11/2013 9:46:10 PM)
|
In a similar vein to the issues about missile cruise heights (as reported here http://www.matrixgames.com/forums/tm.asp?m=3482884 ) I have noticed that there is confusion between the measure of altitudes.
I cannot post a file with this, because I am suffering from the bug that causes the game to lock after a few seconds (and frankly I am past the point when I can be bothered with the 'quick fix' whilst waiting for your build to drop)
So here's what I see (consistently).
Sub launches UGM-109's at Syrian facilities (inland). Not many of them make it and I am wondering why, especially as I have now 'grounded' the Syrian AF during these strikes.
Once they are within 10 nm of the coast, I switch to Syrian side to see whats going on. Sure enough the Syrian radars have detected the tomahawks. I try to engage with missile battery manually - get told the missiles are below 65 feet, the minimum altitude for my SAM of choice - so far so good.
Switch sides, check the tomahawks and yes they are 60 feet AMSL...
Let it run and they are now over land... Now they start to explode...
Switch sides to Syria, sure enough the SAM is now firing at the missiles BECAUSE they are now flying 60 feet AGL, which at that point is 375 feet AMSL and the AI thinks they are in envelope - which they are not! OOPS!
So if SAMs and other sensor stuff is modelled AMSL and altitudes of cruise missiles is AGL - we have a problem [:D]
PS - The (not so) Quick Fix for the crash bug
The only way I fix this bug that causes the game to lock after a few seconds is to completely re-boot my computer and I am not continually doing that, so I get one test out of the scenario and then I just go back to editing it until the next time I have to really have re-boot the computer - seems to me like it crocks your whole system and not just that instance of the game - which would be why you are seeing so many people reporting 'it locks every time I run x or y scenario'
|
|
|
|
