GregP

Seriously ... Is it possible that this point is somehow related to the above: "Implemented new joystick profile system. Now player can use several joysticks of same type and name. Each joystick instance have a unique configuration file." If not, what does this mean? Does anyone actually use 2 or more of the same joystick in-game? I don't understand what they're talking about here.

21 bucks.

Jeez MonnieRock, with a top-of-the-line system like that ... seems like you can probably afford to just go out and BUY yourself an F-18! :) Why wait for ED?

Ah, that's great to hear, thanks Kula66!

Bumping this back up - I was really hoping one of the devs could comment on this and whether it plans to be fixed sometime ...

I ordered the VE addon for my TrackIR3Pro from eDimensional about 2 weeks ago and a few days ago I got a secret-sounding e-mail from them, introducing the TIR4 (minus any details however) and saying that if I wanted to wait another few weeks, I could instead order this version. Since I just bought the TIR3Pro a few months ago, and just built a new system, I haven't got the extra money to get the TIR4. And it would be nice to know some actual performance details first too. :)

If this will somehow let us get around having to change the joystick axis response in LockOn whenever switching from the Su-25T (linear response) to any other plane (curved response) or vice versa, I'm all for it.

Great, thanks! gregpugliese(at)hotmail(dot)com

BGP, I disagree. The way it's treated right now is inconsisent: widescreen resolutions are offered, but the aspect ratio does not get re-calculated correspondingly. Instead you have to go into graphics.cfg and change the aspect ratio yourself - and whenever you go back into the Options/Graphics menu again, the aspect ratio gets reset, even if you don't change the resolution. This isn't something that needs a UI button; it should just be in the code. The aspect ratio should automatically be calculated and applied according to whatever resolution you choose.

Hmmm, you may be right, Nate Dogg. Will check it out tonight.

Gorgeous work! Thanks!

Hey devs, Would it be a simple matter to have Lock On automatically figure out the aspect ratio for a chosen resolution, and apply that to the graphics.cfg file, rather than forcing the user to do it manually? I run 1920x1200 (= 1.6) and every time I re-enter the Options screen, the aspect ratio resets to 1.3333. This gets EXTREMELY annoying, since I need to enter the Options screen every time I switch into or out of the Su-25T (to change the joystick axis response curves) or the A-10 (to change the HUD cursor slew axis assignment to Radar Slew, as this is the only plane that does not use TDC Slew for this function). Additionally, could the above two considerations be fixed? i.e. have separate axis response curves for all the different planes, and change the A-10 HUD cursor to be controlled by TDC Slew instead of Radar Slew?

So ... what I'm hearing is, we need to reinstall F2.5? :) Sounds like it would be worth it just for that mission alone.

Ideally we'd see not only control axis assignments selectable for each plane, but also axis responses too, as the devs recommend using linear response curves for the -25T but standard 'curved' curves for all the rest. Sort of surprising that this feature is not already in there. But at a minimum, changing the A-10 to have TDC control the seeker would make sense.

Heh heh ... yup, I remember that too. :) Haven't done much cobra'ing in Lock On, but if this full flip is possible I might give it a try.

Speaking of things to wish for in a patch regarding controller settings, it would really make sense to change the A-10's controls so that 'TDC Slew' controls the TDC instead of having 'Radar Slew' control it ... or the other way around, whichever way it actually is, I can't remember. :) But the A-10 is the ONLY plane to have this backwards whereas all the other planes use the same control to move the TDC. Gets annoying having to change this HOTAS axis assignment whenever I want to fly the A-10.

This link worked for me, looking forward to trying them out. Thanks!

Thanks for the suggestions guys. However to answer your questions, yes I'm verified that all AP functions were off, as I was flying the plane just fine right up until I hit 'o' to turn the Shkval on. Also the same thing was happening in the quick start mission. Anyway, I solved it, by totally defaulting all my controller inputs and then reassigning all of them. Something weird is going on with my setup. I spent about an hour today trying all kinds of different combinations of setups until I finally get it straightened out. I think the main problem was binding my mouse to controller axes. Doing this in different ways kept screwing up other controller functions. Finally I got it stable. One weird thing - I thought the consensus seemed to be, that if you wanted to use the mouse to slew the HUD TDC, you had to set your mouse axes to control 'TDC' for A/A modes but 'Radar slew' to A/G modes ... and I've just found that not to be true, although I'm SURE I had it this way before. Now I can set the mouse to control TDC and it works for both A/A and A/G - well at least for the Su-27 and Su-25T; I guess I should try the F-15 and A-10 just to be sure. Anyway, that actually makes things easier, as I don't need to change any controller mappings when switching from A/A to A/G aircraft (aside from changing the axis response curves for the Su-25's). EDIT: Through testing I figured out what the weird TDC inconsistency was that I remembered - it's for the A-10. This is the only aircraft for which, even though the same keyboard keys are used as all the other a/c (;',/), in the controller axis setup, you must assign the mouse to 'Radar slew' instead of TDC in order to have them work correctly. That's definitely a bug.

Well this is a new one - After not flying for a while, I hopped in my 25T tonight and gave the TV-guided training mission a try. For some reason, as soon as I switch on the EOS, my controls go dead - no aileron or elevator control whatsoever. Also my mouse, which I have mapped to my Cougar microstick through Foxy, and then the mouse in-game, does nothing. But as soon as I switch that EOS off, I'm OK again. Anybody else ever come across something like this? I'm a pretty competent Cougar user so I don't think I've screwed anything up on that end. I map all the axes in-game anyway, and I haven't changed anything in a while. Right now my setup is: Cougar Axis1: Pitch Cougar Axis0: Aileron Cougar Axis2: Thrust CH Pedals Axis2: Rudder Mouse Axis0: Radar slew horiz Mouse Axis1: Radar slew vert

Well for a given true airspeed, with altitude your IAS should be decreasing, right? Density's dropping, so your IAS, which assumes sea-level (or takeoff) density, is going to show a lower airspeed as altitude increases for a given true airspeed. Therefore, if the HUD wants to show you the IAS to fly at, that number is going to be decreasing as altitude increases. Although now that I read your post again, maybe you weren't actually asking for an explanation of why this was, but instead why is the HUD modelled that way? In that case I'd assume because the HUD is showing IAS? Or is it CAS? Now I'm confused too. :)

Woah - it this THE Snacko from the Falcon4 world?

Hmmm ... can't think of anything else to try. Sorry. But you're right, you should at least be able to map most of these things to key presses, that's what I was doing for a long time before I finally mapped them in-game.

That's strange, I've got my RNG axis controlling MFD Range, mapped through the in-game axes menu. A few things to try/check: 1) Make sure you don't have a RNG axis assignment in your Cougar profile, then set the axis in-game. 2) Try assigning your RNG axis in one of the specific modes, like 'Nav' or 'BVR' instead of 'All'. 3) In-game, can you assign the RNG axis to control something else? And/or can you assign the ANT axis to some other axis (just to check if these axes can be assigned to anything at all?)

It's not that hard to get Loman 2.1 to work with FC, you just have to mess around with the ini file (or cfg, can't remember) and add an entry for FC similarly to the way other games are added. I did this, created a separate addons directory for 1.1 addons, and I've had no problems so far using with both 1.02 and 1.1.

Thanks for the help, BRD, will give that a try when I get home and then hopefully I can go for a leisurely tour. :) Edit: Creating my own .BRF per your instructions worked, don't know why it wouldn't let me just load yours. Anyway, now I'm read to tour! Thanks, Brit_Radar_Dude.