astrospud

I just saw ruggbutt's video of FC A-10's in action. I can see the appeal (I don't have any LOMAC software). Does anyone think that, aside from myself, J, and maybe the possibility of Viper, anyone going to fly the Blackshark after this expansion is released? I hope so. :)

Heading hold (yaw) AP is on, by the sound. I find, also, that if flight ceiling is not that crucial (not often I grant) I grab collective, as it seems to help in putting torque into the turn.

You see, this is what I'm afraid of. All this talk of the A-10 making a huge comeback as an expansion of the DCS series, and everyman and his hog (get it? :)) will be spamming the A-10, and us poor helo pilots will be wearing it... 26-J39, when you're kind enough to host after this expansion comes out, please make sure there are plenty of missions where the Shark pilots have lots of Flanker cover...:D Last thing I want is to be repeatedly pwned by a flying pig...:joystick:

Video is not loading up for me, Cat..

Whatever it will be, it's only going to improve the Shark experience. All good in my book! I know there are a lot of Hog watchers out there, but I love my rotor ship. I'll probably get the A-10 exp, but I think I'll still fly the shark majorly... /me waits for the snickering...:)

right-click on the tray icon and right-click on the profile you want. Then click on "Set as startup Profile". If need be, restart your machine. your SST software should start on windows start up. I strongly suggest that you remove (move to a safe location) the file lua-direct_output.dll found in C:\Program Files\Eagle Dynamics\Ka-50\bin\stable. This file has initially been the cause of "Bad Pool" Blue Screen deaths on my Vista 32 machine. You should also use the latest drivers. Download them, unplug your FCS, uninstall the SST software, install the drivers, install the latest SST software then plug in FCS when asked. If need be, disable the Directinput process as well. This will shut down your MFD display, but it shouldn't impact your gameplay.

Just a little off topic, I think the FD and Hover Mode should have been two ends of a 3 way toggle switch and not independantly operated. Toggle up for FD, centre for off and down for HM. I mean, who flys with both on?

Cheers, Ram. I use a greatly slimmed down version of your profile, having had problems with Bad Pool error blue screens. Nothing to do with your profiles, just removing mapped inputs and using them in DCS alone, whilst leaving SST inputs for stuff for things you can't set up in DCS. These are TS PTT and a setup to have trigger to fire both gun and hardpoints using modes 1 and 2. 1 for guns and 2 for HP. I used to have the Shkval Slew function mapped to my mini stick, but that was giving me so much grief in terms on lagged input - after slewing around a bit, no other functions aside from cyclic axes would function until 5 to 10 seconds later, all in one hit. There must be a correllation between ministick, DirectInput.dll, flickering MFD and this input lag. I'm happy with the way things are ATM; Slew function in on cyclic POV hat. I have since killed the Directinput process and have had no issues. I use Vista 32bit.

Voted! 1st - DCS: Black Shark - 687 2nd - The Sims 3 - 360 Woohoo!

http://www.ausairpower.net/DT-Helo-Survivability-June-2009.pdf Probably details points well known to readers here, but gives a summary of past and current threats to helo's in modern theatre ops. Not that we BS simmers need reminding of that!:D EDIT: Further to that: http://www.ausairpower.net/TE-Helo-Mar-05-P.pdf

Much appreciated. Rep inbound. My situation is that I fly on a 17inch notebook (not impossible, given the right equipment:)) and have astigmatism as well - I have a pair of prescription flight goggles . this makes it hard at times to spot threats. Probably the core of my problem. I can honestly say that in one instance - co-op SvobodaV2p - two of us cleared the field of AA threats and most tanks. Only 3 Leopard II's remained. Could I spot the suckers in strafing range? No. :doh: Pass after pass after pass. I could not mark them successfully. I think I need to invest in a nice 24inch LCD and put into practice some of these ideas.:thumbup:

Just wanting to know if there is a way the more experienced pilots tackle new mission. It seems to me that IRL jumping in the shark and moving into hostile airspace blind as a bat (tactically speaking) seems suicidal. Almost every new mission I fly - MP or SP - 10 minutes or less into it I either wear AAA or missile between the eyes, not knowing where it came from. Do you enter the combat space: gingerly, 1 km at a time, bring the shark to a hover and doing Shkval sweep? If wingman is present, send him into Recce? (probably a smarter way to do things in SP miz or Campaign) charge in fast, NOE or treetop level, consequences be damned? read the mission map, plotting probable SAM sites/AA emplacements, or ambush sites, plotting new WP's (don't think this is feasable, since MANPAD can be anywhere...)? I know I'm a nub at this sim, but I need to pick the brains of the accomplished and skilled among us, if I'm to have any chance of doing the campaign... Cheers.

I tend to link the cyclic positioning after a bit of trimming, and the closeness of the StB side of the rotors. What I mean by this is, in the external view, the Starboard side of the 2 rotor disks are much closer together than they are on the port side. It has never seemed natural to me, as it just screams "imminent blade clash". I'm guessing this is real world as well...?

I'm not sure where to post this, so I hope this is the right place. When I want to lift off vertically in BS (from FARP), I have to pitch the cyclic a smidge forward, so that the diamond (in the control schematic) is just north of the natural rest position. Is this because my X52 Pro is out of calibration or is this how the Kamov actually behaves? Also, I find that in the course of a flight,the diamond in the control schematic generally ends up in the top right quadrangle, after much trimming. Upon resetting trim, the ship pitches up wildly, thus I have to pitch forward whilst resetting trim. Is this normal?

Thx, Ramstein! Will give it a go tonight after work :)

Couldn't agree more! Incidently, I am a BS noob, only flown a handful of missions and mostly MP since August, so the game is still fresh for me. But i do mix it up with other games. Also FSX and 2142 as well. Sure they are not in the same vane as BS - FSX is simulation, but not in the same camp as BS, IMHO, and 2142 is just pure MP slugfest. Where ever your interest lies, you are only limited to your descision to take a break from that which has lost it's shine. I have been playing 2142 since it came out (2006). Took a break for about 8 months, came back and the people I play with (TOG -The Older Gamers) make it fresh and fun. Try MP BS, or join a squadron with casual easygoing players. It's fun, flying with real humans. They are just as competitive - or fallable - as you are.

I have just purchased TIR5 and find that if I bind a Left mouse click button to my HOTAS, I can keep mouse mode on and interface directly by moving my head to hilight the input I want to switch. I then press the bound LMB. I do this for Fence in/out sequence where I want ot stay hands on. The mouse crosshair is not obtrusive.

Nice name...:) No, I don't but it is an unusual bit of kit if you haven't had experience before. You have: Laser range finder - important to find range of targets to determine whether they are in effective range. Zoom: 7X or 23X. 2 options - I supposed Carl Zeiss don't do electro optical sights... Target tracking; ground moving, air to air or air to air head on (air burst prox. fuse). Turn to target: must have auto pilot heading hold switched on. Does it automagically. And finally, target lock: when you have the target window on a chosen enemy, press this to get a lock. These things all have a baring on how targets are acquired using Shkval. The key thing to using Shkval, is to have a steady hover. Master that, and you'll be well on your way. :) Stick with it, mate.

OK, It turns out that the ministick is the problem. I tried entering the ministick mapped to Shkval slew in SST exclusively and my throttle MFD flickers every time I input from ministick. This flickering coincides with my input lag issue as well. Bugger. It's a good aspect of the X52pro. I have tried using the Shkval slew on the Cyclic tophat, and while access is easy, it's more of a challenge locking moving targets, as my target lock button is on "Fire c" of the cyclic as well. I will now have to shuffle my config around. Double bugger. I was just getting used to that config... I'm thinking I will have more luck if I change OS - currently Vista 32.

Thnx mate. Will have a go at your first recommendation. Pending further issues, I may follow the rest of the points - or simply point 4 as it stands...

Counter to some views here, I prefer to use the ministick for Shkval slew.... But I have another problem. I have the X52 Pro kit and have had "input lag" issues lately - apart from cyclic pitch, roll and yaw, all other inputs from buttons and even throttle have been lagged, sometimes for 15 seconds. After which all inputs flood in all at once. It's kind of like a pipe being blocked up and suddenly getting unblocked - sorry, weird analogy, but that's as close as I can come to describing it.... I blame the SST programming software. So, now I am trying to program my (Blackshark) controls, purely through the game options, and bypassing Saitek's SST altogether. I'm hoping this will streamline my controls regime and get rid of this input lag once and for all. My problem, however, lies with the apparent lack of ministick in the axis assignments options. I am used to using the ministick for Shkval and would like to program it in game. Any ideas?

Just curious. How'd you score a medal? I've done that mission 2-3 times and made it back in one piece. I'm jealous!;) BTW, with regard to slewing the Shkval and getting all out of control; I have an X52Pro kit and sometimes I get input lag - delayed response from any of my control inputs, aside from cyclic, then they all manifest 10 seconds or so later, all at once. I've had my ship pitch back wildy whilst in a hover, searching for targets. Do you have a Saitek stick?

I share the sentiment with the others. Don't give up. If you love simming, with some time this will give you so much enjoyment. I am constantly learning how this ship flies as well. and I have only had the game since August. I learned so much from the guys at VAAF.net. Great bunch of simmers and really patient. Find out what groups are recruiting novices and I guarantee your skill level will go through the roof. Stick with it. :)

I think it has to be set to simulation mode - no padlocks, labels, ammo / fuel mods. Just a guess, since i have 3 medals from game mode - all in individual missions and instant action flights. Campaign might be different.

Hi guys. I'm new too, just been flying since August. I strongly suggest you dive straight into full real mode, as It's the only way you will pick up this terrific sim without leanring any bad habits. The biggest killer us newbies encounter in this (I proudly stand among the newbie! :)) is VRS - Vortex Ring State. If I remember rightly Game mode doesn't produce conditions for VRS. Check out the Wiki: http://en.wiki.eagle.ru/wiki/Resources_for_New_Pilots In a nutshell, VRS is when the ship is descending in it's own downwash and thus not getting new air to keep it stable. Even with full collective and power, you still keep heading for the dirt. Game mode won't teach you that. :) Anyhoo, welcome to the best sim around!