GregP Posted November 8, 2014 Posted November 8, 2014 I've noticed that in the 1.2.11 open beta, when you assign 'Radar Range' to an axis, the range will only vary from 10.0 to 150.0. But when you assign that function to a button ('Target Specified Size Decrease/Increase') the range can vary from 2.0 to 150.0. I've tried this on multiple controllers and different axes, so am quite sure it's nothing in my control setup that causing this problem.
GGTharos Posted November 8, 2014 Posted November 8, 2014 I believe the 2.0 is an error, the lowest number should be 10. I'll forward this, thanks for the report. [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
GregP Posted November 8, 2014 Author Posted November 8, 2014 Actually, now I'm thinking it may be modeled correctly; at least, consistently with what the manual states: p. 59, discussing launching on AOJ locks: "If the entered target range is longer than the range of the chosen missiles for this altitude, then missile launch requires either that the entered range is manually reduced with [RCtrl--] until the "ПР" symbol appears, or that launch authorization override is enabled with [LAlt-W]." So I take that to mean that using the Radar Range axis lets you get down to 10.0 km, but if you want to launch on an AOJ lock and can't get the missile to launch because its range is less than 10.0 km, you can 'trick' the missile into launching by saying that the estimated range is now less than 10.0 -- as low as 2.0. Seems a bit redundant though since we already have Launch Authorization Override.
Recommended Posts