169th_Crusty

I might be able to join the "masses" on the 29th if the there`s any room left. How many leaders signed in so far? BTW, whatever happend to Crimean Wars or are there any other "wars" brewing out there. Any activity with planning, ATOs, organized flight packages? Anything...? In my entire Lockon career I`ve only had a chance to participate in one such mission (169th intrasquad war) and that was the best Lockon time I`ve ever had.

Lol, yep comrad Tito knew how to get things done!

Was it something he said about this fine piece of software from starforce?

Crusty Club is growing:) ...you sure we haven`t met... on TS;)

Yep, it is funny. Or maybe it`s not. When I installed 1.12a on my "original" FC installation, my TIR worked fine without deleting any files. Then, after disabling some ports in BIOS, I needed to reactivate starforce. (Enabling these ports again or using backup reg. didn`t help!) I backed my reg. key then wiped everything out (wrote "zeros" to my hard drive before formating and reinstalling OS) and used my backed up reg. key to activate 1.12a - worked! But, the TIR didn`t. After deleting these 2 files problem was solved. Oh, little OT stuff: When I tried to install my WinXP, my new DVD drive would not come up to speed and I was getting errors. Hell, it was Sony! :( Something must`ve crapped out. So I used my HP drive from my other rig and it was flying! But, that`s way OT!

LOL, finally; I fit in too. :)

at the Nvidia site. Probably not any different from 84.20 other then WHQL part.

Even if they fixed the scan orientation thing, it would still be half ass. Unless couple of TWS submodes were included. Not sure if the early APG63 had any combined modes. That could really be usefull.

LOL, I guess not. Was he in a dive?

I didn`t notice this problem. If you "intuitively" follow the target(s) with elevation adjustments and the targets are not doing any radical manouvers, you shouldn`t have any problems tracking them. Yes, I know, in RL the radar scan is auto-centered on your primary target and it would be nice to have this feature implemented here, but...

Anytime you click on "Options" (not just graphics settings), you`ll have to delete these 2 files to be able to use TIR. If you edit the graphics.cfg - it does not effect TIR (once you have it working)

No, hammerhead = hammerhead

A thrust vector equipped jet probably could.

Yea, in Lockon`s F15 this generally works. But "when" ED implements a good AFM for the Eagle, the recovery might go like this: ... For recovery from a positive g spin, maintain neutral longitudinal stick and apply full lateral stick with the yaw, the same direction as the turn needle. Rudder is not needed, but if used, must be against the yaw, opposite to the direction of turn needle. Neutralize all controlls when the departure warning stops and allow large residual motions to damp. Neutral controls will recover the aircraft from all negative g conditions including spins and auto-rolls; however, rudder with the roll will provide a faster recovery from a negative g auto-roll. Do not move the throttles unless in afterburner. If in afterburner, reduce power to MIL. The checklist follows... Edit: oh, the compressor stall was not a factor in the above quote, of course.

How about inertial nav. Also, how different is the naval "nature"? Agreed on some military fields lacking ILS and that Lockon needs a major rework on nav part.

LOL, you`re quite a separatist yourself - talking about shaped charges and stuff...

I`m not sure if it`s a bug or something else. I`ve seen it only on dreyou`s server and before 1.12a. It appeared also under the missiles. Not sure if it still does that. Edit: Yea, I suspected it had something to do with the labels.

Seems like 84.15whql disappeared from Nvidia`s main d/l page but there`s 84.20 beta available (posted also on March 9)

Yep, I`ve been waiting for a long time for somebody to give Keiser Elecro- optics "SimEye" some serious competition and bring`em down from their high horse and I don`t think it`s gonna happen anytime soon :(

lethality of 20mm and 30mm rounds I`m just discovering 1.12a and for most of you this stuff is probably old news. The gunzo business changed quite a bit and there is no mention about it in the readme file. The lethality of 20 & 30 mm rounds. The planes will explode more readily now after being hit with a good tracking shot. The burning fuel does what it`s supposed to do now. Good job on that ED.

Yes, but in 1.11 for some reason I could follow an object with my TIR and the picture was clear (in RL I could do that too, when sober - without TIR:)) In 1.12a the blurry stuff happens also at medium speeds. Oh well, not a big problem.

My setup is exactly the same as in 1.1. Same values in graphics.cfg, etc. In 1.1 when flying through big cities and looking to the side, the graphics were sharp and fps was great. I could focus on any object flying at low altitude at high speed. Not in 1.12 - the objects appear blurred as if fps was real low. The fps is not really that much lower then in 1.11. It happens only when looking to the side at close distance, regardless whether I use TrackIr or not. My rig is AMD 4400+ with Asus7800GTX. Other than that everything works good. Well... I haven`t done any online flying yet with 1.12a.

I`m afraid to experiment with my own computer now. This f****** starfart stole another activation from me. I disabled some unused stuff on my rig: serial and parallel ports, midi, game, etc. (as advised by EvilScotsman) Obviously, the almighty sfart noticed it... I enabled all of these things again... sfart wasn`t satisfied. I tried registry backup I made earlier - no go! So, I activated again (12 left:)) Well, activation wasn`t quite smooth. I had to screw around with my firewall but, wasn`t so bad. I also upgraded to new BIOS, NV4 chipset drivers and some Guru3d stuff and I`m so happy and gratefull that sfart allowed me to do that... or, did it? I`ll find out soon :/

Thanks for the advice Evil, I`ll try that.

I didn`t have time to read the entire thread, perhaps you explained it already. After shutting off these ports, the blue screens stopped? When I overclocked my 4400+ (using AI in bios, initially) to the max. allowed by AI (10% :/) I would occasionally get a blue screen with a message "IRQL number not less or equal". When I backed down to 8% it stopped !!!? I have no idea if that was the reason why it stopped but I never got this BSOD again. I didn`t do anything else! BTW, what does "L" in IRQL stand for?