bumfire

Yes it wont chose next WPT for you on the PVI, only for Abris, my post was merely a follow up to ZaltysZ post, where he mentioned the PVI way of doing things and I mentioned the Abris part of things.

In the Abris goto MENU/OPTION/MAIN using the FSK's In there you will find WPT SEQUENCE - AUTO Set to AUTO if it isnt already, automatically switches from one waypoint to next when the steerpoint has been reached. Page 7-24 -- 7-25 of the Bound manual.

I have landed 25t 25 and mig29s on road and grass in fc2, works no problem.

I can just imagine the performance hit if it was there and turned on :| But then again, maybe things have progressed and grass isnt that much of a perf hit ?

I really dont know, I am just saying what he said, at first he said it felt weird and then he said that it was just a very little jolt and that he hardly felt it and he didnt think it could of been felt as far as NYC. His words not mine.

My buddy was in his office speaking on msn to me when the quake hit canada yesterday, he said it felt weird as shit, his words :) I dunno about it being felt in NYC as he said that he could Barely feel it and that was way up in Canada, so I think its unlikely it was felt in NYC.

Agreed, ACE2 for Arma 2 is the ONLY way to play this game :)

try this, copy the entire contents on the disc to a new folder on your desktop and once its been copied there, try and install the game using the setup.exe or autorun icons, whatever you may have. You may have better luck doign it that way rather than installing it from the disc. If you do it that way and it works, then save that folder, copy it onto another disc ? but save it and install BS from there everytime, as it could be your disc thats messed up and you may or may not be able to clean it and be able to install from it again properly, but just cuz it wont install from the disc properly, chances are you can copy the files onto your harddrive and install that way no problem. But first off, uninstall blackshark, and delete the install folder before trying to reinstall.

Single trigger FTW ? I use single trigger for blackshark, just edit a file and the weapons all fire from 1 trigger instead of 2, dont know if gunpods and cannon can fire at the same time though, cant recall if I ever tried it.

Buffs dont have rear guns any more and havent had for years, so gunzo = easy kill :)

Well, if its been removed from the sim, their is no need for me to "try" and put them in. I havent played blackshark for about 6 months or so since I changed OS, and I never got around to installing it, and during that time the patch came out. But, in trying to add fix points, I select INU, then click on the map, but it wouldnt put a fix on the map nor show any co-ords in the INU box, they were just greyed out, but maybe the reason is because its been removed from the sim ? Hopefully it gets added back in again, but I would also like someone to test to see if they can still input inu points on the map/ME, just so I can rule out my game as being the problem. Even though it cant be used when flying like it could be before the patch.

In the mission editor, can people add INU fix points ? I ask because when I click on ADD, and then click on the map, nothing happens, it wont let me add any fix points at all, like it used to when I last had BS installed. I have tried adding them to the map, but nothing happens, everything remains greyed out in the INU section. is this a bug with the latest patch or is it just affecting my copy ???

"G'damn it wont keep a lock" gunzo ftw :D there is another video of a F15 from Oregan ANG or was it f15s from Washington ??? i cant exactly recall, long time since I seen the vid, they were training with phantom drones ( what a waste ) and the f15 fires a heater and the phantom releases like 100 flares and the heater does some crazy moves, like 90o angles and gets spoofed by the flares and the f15 pilots cant believe it. If I find it again I will post it if no one else beats me to it, it has the song radar love playing in the background. 4.05

I am not sure, but I think I may have found a fix. goto Scripts\Aircrafts\Ka-50\Cockpit\mainpanel_init.lua then change -- Fuel tanks ForwardTankAmount = CreateGauge() ForwardTankAmount.arg_number = 137 ForwardTankAmount.input = {0.0, 1.0} ForwardTankAmount.output = {0.0, 1.0} ForwardTankAmount.controller = controllers.ForwardTankAmount RearTankAmount = CreateGauge() RearTankAmount.arg_number = 138 RearTankAmount.input = {0.0, 1.0} RearTankAmount.output = {0.0, 1.0} RearTankAmount.controller = controllers.RearTankAmount lamp_ForwardTankTest = CreateGauge() lamp_ForwardTankTest.arg_number = 139 lamp_ForwardTankTest.input = {0.0, 1.0} lamp_ForwardTankTest.output = {0.0, 1.0} lamp_ForwardTankTest.controller = controllers.lamp_ForwardTankTest lamp_RearTankTest = CreateGauge() lamp_RearTankTest.arg_number = 140 lamp_RearTankTest.input = {0.0, 1.0} lamp_RearTankTest.output = {0.0, 1.0} lamp_RearTankTest.controller = controllers.lamp_RearTankTest to -- Fuel tanks RearTankAmount = CreateGauge() RearTankAmount.arg_number = 137 RearTankAmount.input = {0.0, 1.0} RearTankAmount.output = {0.0, 1.0} RearTankAmount.controller = controllers.RearTankAmount ForwardTankAmount = CreateGauge() ForwardTankAmount.arg_number = 138 ForwardTankAmount.input = {0.0, 1.0} ForwardTankAmount.output = {0.0, 1.0} ForwardTankAmount.controller = controllers.ForwardTankAmount lamp_ForwardTankTest = CreateGauge() lamp_ForwardTankTest.arg_number = 139 lamp_ForwardTankTest.input = {0.0, 1.0} lamp_ForwardTankTest.output = {0.0, 1.0} lamp_ForwardTankTest.controller = controllers.lamp_ForwardTankTest lamp_RearTankTest = CreateGauge() lamp_RearTankTest.arg_number = 140 lamp_RearTankTest.input = {0.0, 1.0} lamp_RearTankTest.output = {0.0, 1.0} lamp_RearTankTest.controller = controllers.lamp_RearTankTest All works perfect, its been used for a while now by various people and there are 0 problems associated with it, basically just switch the red numbers about so that the forward tank is numbered 138 and the rear tank is numbered 137 and the tanks/guages will be correct ingame. I hope this helps, also its my first ever fix for any of the lockons/dcs sims, so I did get a raging boner when I found a solution :joystick: Just to add, I did more than just swapping the numbers about, I also swapped the paragraphs about so that the rear tank/137 is now above the forward tank/ 138 instead of being below it, purely because of the positioning of the numbers, I simply wanted 137 to be above 138 :music_whistling: have Phun.

I think in the video, they were playing lockon AND DCS A10C Because, in one frame you see him flying the A model and then the f15, now, we know the f15 wont be in DCS A10, so in my opinion, in the video they were flying Lockon 2 and DCS A10C, hence the reason you see 2 versions of the A10. I dont think the A version will be available as a Flyable plane in DCS A10C.

I have this video on my harddrive if anyone who cant view it needs it, I didnt think much of the programme, but others might like it. If you need it lemme know and I will host.

Good to hear that a jiggle/reseat fixed your problem, with your symptoms, I would of definetly put it down to bust hardware, but alas a bad connection or a dodgy 6/8 pin power connection may have caused your problem. Good to see that it wasnt needing RMA'd, cuz rma is a pita, I am in the middle of 2 atm and both companies are coming the cnut.

One of the Global Hawks was lost in December 1999, when an official incorrectly programmed the UAV to taxi at 155 nautical miles per hour. :megalol: http://www.barnardmicrosystems.com/L4E_accidents.htm#Hawk

Whats Testes got to do with Lomac ? apart from getting them shot off :)

I doubt very much that we will see a KA52 any time soon, the hardware inside it is probably classified. I would settle for the KA50 with samshite night attack system, gives us more scope for night flying, but alas, I wont get to see that ingame unless it goes into service.

I would put my money on video card being fubar'd, memory problems on the card or actual gpu. If this happens before windows boots, i.e if you get graphical glitches during post or in the bios then its definetly a hardware fault, I presume by your shots that its a hardware fault already, but if it happens during post or bios then that would confirm it. RMA time me thinks.

Try the beta ones instead

Dnnzed FC1 fully patched works perfectly on windows 7 64. When vista first came out if I recall, starforce caused problems then, but only because that version of starforce wasnt compatible with vista, but within days an update to fc1 was available that fixed the problem. Basically you will or should not have any problems running fc1 on win7 64.

So I wasnt just dreaming it ?

4 weeks of utter bullshit now commences :doh: