Fellblade Posted April 10, 2005 Posted April 10, 2005 Well, we have a nice, new way of setting the radar elevation on the Su-27. I preferred the old way, but the closest that I have found to approximating it is by leaving the estimated distance to target at 10km, and alter the elevation from there. The problem is that the new elevation code is... different. I used to have my mouse axes bound to control the radar elevation / slew, and my X-52 mini-stick set to mouse elevation to control it. Slew simply no longer works when bound to a mouse axis, and elevation changes occur so slowly that it's unusable. Am I mission some way of returning to the 'old' radar elevation mode? How are the rest of the '27 drivers out there coping with the change?
gustav Posted April 10, 2005 Posted April 10, 2005 I have problems with radar slew too. The slew keys wont hold, you have to press repeatedly which make radar control a pain.
GGTharos Posted April 10, 2005 Posted April 10, 2005 That's the way it's supposed to work. GCI gives you target contact info and you set the range and relative elevation, then fire up the radar. [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
Fellblade Posted April 10, 2005 Author Posted April 10, 2005 ...unless you're online, with no GCI, when you? The main issue is that you can't bind the radar elevation setting to a mouse axis, as it doesn't move fast enough. If you bind a button to it, you have to repeatedly hit it - you can't hold the button down. This is a problem as well, because if I bind my X-52 controls to repeatedly fire the command... the EOS elevation screws up, because the EOS elevation is working in the same way as it did in 1.02.
GGTharos Posted April 10, 2005 Posted April 10, 2005 It's part of the Sue's and MiG's workload problem, is all I can say. [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
Fellblade Posted April 10, 2005 Author Posted April 10, 2005 Joyous. Time to try and work out how to sort out my controls then. Anyone have a bright idea, do mention it :p
ED Team Olgerd Posted April 10, 2005 ED Team Posted April 10, 2005 That's the way it's supposed to work. GCI gives you target contact info and you set the range and relative elevation, then fire up the radar. This way of radar elevation control on real airplanes was derived from its' employment concept. In typical intercept mission on theese aircrafts you are assisted by GCI operators. They give you elevation/descent in km of target relative to yours aircraft. [sIGPIC][/sIGPIC] К чему стадам дары свободы? Их должно резать или стричь. Наследство их из рода в роды Ярмо с гремушками да бич.
Cat Posted April 10, 2005 Posted April 10, 2005 Ah...realism :) The things we sacrifice for it! Frankly, I still like the new radars better. I don't know why, but they seem more ...intuitive to me than the American radars do. Isn't that weird? Hey, looks like I made the 1.2 test group! That'll be an interesting experience! Miao, Cat
ED Team Olgerd Posted April 10, 2005 ED Team Posted April 10, 2005 Wellcome aboard. ;) [sIGPIC][/sIGPIC] К чему стадам дары свободы? Их должно резать или стричь. Наследство их из рода в роды Ярмо с гремушками да бич.
gustav Posted April 10, 2005 Posted April 10, 2005 Allright, now when I know its a "feature" it's not a pain anymore. :) I have another realism question though. When you lock a target in any of the close combat modes you dont get range, elevation or aspect ratio. Why is this information filtered out? It seems strange. The more imformation the better one would imagine.
Recommended Posts