GregP

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.

Maybe the lack of skin uploads is due to skinners waiting (in vain now?) for LoMan 3.4, so they could ensure their skins are compliant? I expect the deluge to begin any day now, once those 1.1 CDs start to arrive and everyone finally has Flaming Cliffs.

Hey BRD, are you using LOBrief 1.12? I just reinstalled it and when I go to load your mission into LOBrief, I get errors saying 'Problem in the DLL DllFctBrf.dll for the reading of the description!' and then 'The file mission is not a valid mission solo!!' and that's it. The LOBrief readme translation is a little confusing, maybe I'm doing something wrong - could you quickly outline the process for using your BRF and MIS file together?

Well, I guess I suck with the Sue because on my first 5 attempts last night I couldn't get under 1:55. But thank you, Andrew, for making a fun little course here. Can't wait to get home and give it a few more shots tonight. :)

I too was very impressed by the airshow. I wasn't sure I'd be able to get up in time but when 6:45AM rolled around Saturday morning, I leapt out of bed and ran to my computer! (6PM Moscow time = 7AM San Francisco time). It was a treat to watch and I too recorded a track for watching later, even showed it to a friend later that night. I think this was a great demonstration of where we can take this medium. Looking forward to the next show, thanks VFTC!

Are you using the 1.1 demo or full version? Because I've only heard about default zoom being too far in when people were using the demo. Anyway, I recently upgraded from an original TIR to a TIR3Pro. Upon installing the Version 4 software, however, the new TIR3's behavior was very strange near center - pressing my 'center' key would move the view NEAR center but not perfectly on it, and would then drift around center over the next few seconds. It was not the crisp snapping-directly-to-center behavior I was accustomed to with my older TIR. After posting on the Naturalpoint forums, and having a few other people mention they were having the same problems, no one offered any suggestions. I was about to give up and go back to my old TIR, but then decided to try the Version 3 software - and that fixed it! I've got the proper centering behavior now. So, the point of all that (finally :)) was that I could post my profile here but it wouldn't be immediately useable for you, if you're running the Version 4 software with your TIR3. But this may help anyway, as you can set the speeds at each point like I have: Point Speed 0 0 2 0 5 0 10 6 20 10 30 14 40 18 50 19 Smoothing: 90 This isn't perfect, the motion is a little too sensitive right outside the center, but it's working OK for me for now.

A legitimate question, but makes you realize how far the series has come, doesn't it? I remember in Flanker 2.0 we didn't even have rolling wheels ... :)

WOW! Nice page, lots of great information there. Zoomboy you seem to be doing it all these days! Thanks a lot, from a guy who's had ZERO flight time in the T since 1.1 came out (Real Life distractions) but DOES have internet access at work to at least READ about it .... :)

I recently bought a 24" LCD that runs 1920x1200, which is 1.6. I set the graphics.cfg file to do this, but one annoyance I've found is that LockOn seems to periodically reset the aspect ratio to the default 1.33333373, requiring me to reset it to 1.6. This may only happen the first few runs of the game though, as I noticed it when installing but haven't had to do it the last few times I've flown.

McFly, I think the answer is, no, the first picture is not a bug, because your radar has switched to HOJ mode, which is a passive mode. You can sort of 'lock on' to the jamming, but your HDD can't pinpoint where the bandit is, so it can't draw anything there for you.

You've got your microstick controlling the A/A TDC in the Su-27, -33, MiG-29, and simultaneously controlling the A/G TDC in the Su-25 and -25T? If so how did you assign the axes, in-game or in SST?

bump Nobody else is bothered by this? Would be nice to hear ED's reasoning behind this, as it just doesn't make any sense. Why should ONE of seven flyables have a different control scheme than the rest?

TekaTeka, I haven't had more than about 10 minutes to fiddle with 1.1 since it came out, so I don't know the answer to this fairly simple question: does the HUD color change function (Ctrl-H) not work anymore? Or are you just showing a better default color?

Hmm, good find, Brun. I spent quite a bit of time with 1.02 and the 1.1 demo trying to get my Cougar microstick mapped to the HUD TD in both A/A *and* A/G modes, and finally got it to work by assigning to TDC slew in A/A and radar slew in A/G. I haven't had more than 5 minutes of time in 1.1 yet so I hadn't discovered what you found yet ... but I agree this is REALLY frustrating, as there's no reason it should be different for the T. Thanks for posting though, as it would have driven me crazy to find it NOT working in the T when I first tried it. I really hope this gets fixed/changed soon ...

Alright, it DOES work - you can control both the A/G laser designator cursor (using 'Radar slew') and the A/A TDS with the mouse.