Sinky

Press the 'A' key.

I completely agree with you. Running flawlessly here also, regular uninstall, restart and install. While I've programmed in many languages for years, I've never created an uninstaller, surely it can't be that hard to uninstall your files...

Ah I see. My mistake. :)

I've only managed one test so far and 3 of 4 mavericks missed for one reason or another, couldn't seem to replicate the "bad lock" so these were on what I think were good locks, upon flying closer in I was having more success. Will possibly be doing more tomorrow. I'm at the conclusion so far that the range at which you launch is the main factor, think my tests were around 6.5 miles.

Neg, running a 5770 with 11.4 and I'm getting black screen flickering when looking near the sun with HDR turned on. Haven't read the whole thread but I'm guessing that's the flickering everyone is referring to.

I had a scan through this forum and I haven't seen this mentioned before, apologies if it has been. It would be nice to have the F10 satellite view available from inside the mission editor, I believe it would help immensely with the positioning of units. Stops us having to spend 5 minutes loading the mission all the time just to make sure that the T-80U you placed in a new area hasn't sprouted a tree out the top of it.

Have you considered playing with your curves for you joystick axis's? Make's all the difference, you can achieve extremely smooth flight. It is not cheating at all, the real pilots have controls at the same sensitivity as a curve of 0 ( I think ). The fact that their control stick extends from the floor makes all the difference, the longer it is the more precision you have at the top end, something we don't get with our flight sticks. 'Least that's what I was told.

Have you tried tilting the cameras head? It was possible on TrackIR 4, don't know about version 5 though.

Going to do some tests with the D model firstly firing four off in the first bad lock and then four in the good lock, see if it makes a difference. Edit: Found an interesting thread on the forums. It appears the Maverick employment with regards to symbology may be incorrect at current. http://forums.eagle.ru/showthread.php?t=71672 From what I can gather on that post a steady cross should indicate a good hit chance and a flashing cross should indicate that the Maverick might break lock during it's flight to the target.

No harm in me checking :). They fly daily I think so it's much easier to remember. If I don't fly for one week I forget how to start her up. I've forgot that procedure around 6 times from taking little breaks.

There is a tiny gap just before they touch, here two screenshot's, the target is 100% locked in both screenshot's. I had to re-lock the target as I got in closer ( resulting in a good lock ), the 7.1 mile lock was confirmed since the tracking gate was shaking indicating a lock. Sometimes it will change to a good lock on it's own. I'm not an expert and I haven't read up on this, but my guess is that it's indicating the quality of the lock.

Bare with me whilst I take a screenshot to explain, it's 100% not in force correlate, doesn't work on D Mav's if I recall.

There used to be a few mod's for a mint green HUD in Flaming Cliffs. This proves that it was editable and might still be editable. I'm sure if colour blind people are having problems then someone would make a mod, if it's still do-able that is.

:megalol: Good training for dodging those Zeus's, no?

Target Management Switch defaults to Left Ctrl + Directional Keys. TMS Forward Short means press the combination once, Forward Long means you hold it for a few seconds.

Are you waiting for the tracking gate to indicate a GOOD lock? You can lock it and the tracking gate's ( or lines ) won't touch each other in the centre. I usually wait for the gates to close on the target which I'm guessing is indicating a good lock. There's a gap in the centre before you lock a target, if that gap is still there upon locking it then you should wait for it to close.

I'm able to change from CCIP to CCRP with no problems. I think he just forgot to set up his GBU-12 profile so that it defaulted to CCRP, like you said. On the ground I always set up GBU-12's profile into CCRP with auto lase turned on at 12 seconds.

If I remember correctly, in civil aviation anyways, if you have no visual on the runway as you pass over the inner marker, you get the hell out of there. It might have been your set minimums and not the inner marker, I can't remember. It's been years since I flew civil flight sim's.

I see, thought I'd just forgot how to turn it down in the period I was away from the sim. Great video zamboni.

No problem. I just prefer to do it this way, the only time I really create flight plans is if I have two groups of separate targets and I want to group them in a nice way. For example, I may want to group my spotted air defence's in a separate flight plan to that group of tank's it's protecting.

Nearly, all you have to do is on the UFC press the Function key and then the number 8 key to access MARK mode. Then you can cycle the mark points, when your done just press Function + 7 to go back to your original flight plan with your original steer point selected. There's no need to really add it in since it would take a while to explain in the annotations. Maybe stick it in the description as an after thought.

Yeah it's no biggie anyways. :)

Thanks for the contribution to help the influx of new pilots :thumbup:. Would have been nice if you stated that instead of creating a flight plan you can also go into MARK mode using the UFC which is a lot faster.

There is a fix for this but using it means that your light's won't project onto surfaces. So, your landing and taxi light's won't light the taxiways at night. Small price to pay in my eyes.

It can take out missiles being fired at it but can it also take out a GBU-12 for example? I suppose it can detect the fact it's being lased so it could probably take it out. That leaves us with IAM's, which I doubt it could ever detect.