Brun

Killjoy, The Maverick seeker in the A-10 does work, but the controls need to be mapped to the radar rather than TDC axes. As far as I can remember, this is the case for the standard Su-25 as well (might be wrong on that one). It's both illogical and infuriating, having to constantly change setups in order to fly different aircraft but unfortunately I haven't seen any mention of this being changed in the upcoming patch. Best keep yer fingers crossed. B

RTFM (Read the Foxy manual!). You can map the rWin (and all the other funny ones)key using the appropritate USB code, regardless of whether it's on your keyboard or not. And yes, you could also re-map the keys. If you've no need for the easy-radar option (ctrl-i) switch that with the PRF command. EDIT - that easy radar thing might be shift-i, but you'll have to check for yourself cos I'm at work (tho not working, obviously ;) )

My preference is to leave the Lock On axis options as default (linear, no deadzone) and set things to my tastes in the CPP. Why? Just seems easier to tweak/change configurations that way, especially since there's no per-aircraft input options in Lock On. Really wish there were to be honest.

Still can't un-bug (no pun) targets using CTRL-TAB in F-15 TWS mode. Once a target is bugged, the only way to un-bug it is to either lock it in STT and then unlock it, or toggle the radar off-on. Given that it's easy to select the wrong target in cluttered airspace, I was hoping that might've been addressed. I guess this isn't strictly a bug, but I reckon it should still make it onto the 'stuff what needs fixing' list.

I hope it does get addressed, it just seems an odd oversight that could've been easily corrected. As for the axis settings for pitch and roll, I use the Cougar's control panel rather than the in-game one which makes it much easier to swap them around. I think ED need to look at implementing a load/save feature for the configs in future. I'm sure I'm not the only person that makes a lot of changes to the default settings, and haing re-installed Lock On an awful lot of times, it's something that I'd definately have appreciated.

Definately agree about the lights, the attenuation is far too strong at the moment. Understand you're point about about the smoke, but I reckon more of it would probably mean fewer fps. You don't need a poll to find out that wouldn't be popular. ;) My suggestions: Additive transparency on the HUD graphics - this has been mentioned before, complete with examples. Specularity mapping in the graphics engine - Currently the biggest omission from the visuals in my opinon, all the aircraft have the same 'shininess' over the entire airframe. Specular maps would make a huge difference. Surround sousound - Despite the sound sources (in-cockpit at least) being fairly static, I'm sure the sound engine would benifit from having more depth. Think AAA shells tearing into the rear fuselage of your A-10, and suchlike. I'm sure there's loads more stuff, but that's what's come off the top of me head.

Just discovered something that's going to become very annoying. Since 1.02 I've been using the Cougar's microstick (emulating the mouse) to control the target designator/TV seeker etc. For A-G use in the A-10 and Su-25 the axes had to be mapped to 'Radar Slew' which while seeming rather illogical, worked perfectly well. However, while going through the Su-25T training missions, I've just found out that control of the 'Shkval' doesn't work with the input options configured as above, but instead the axes must be set to 'TDS slew'. Therefore, switching aircraft necessitates having to re-configure the input options, which is pretty silly, considering how easily it could've been avoided. Also, there's something odd going on in the options screen itself. While setting up the axes per flight mode, in the 'ground' mode it's showing the axes mapped to both Radar Slew and TDS Slew. This isn't actually the case though, otherwise the above problem wouldn't exist. Other than that, 1.1 is all good so far.