kingpinda

All I heard was: New KA-50 Campaign!!!!! Whoohoo! That and the easy radio is fixed and released rudder from trim couple of months ago... I've been flying the heck out of the Shark these last months again, and I can't get enough of it! Especially so since my skill increased considerably after trying to "master" the Huey. Awsome!

I myself tried every setting to get the hat clip to work with my annoying reflecting glasses. Given up and using the pro clip instead.

Thanks! nice read!

Ah hell.. That gives me an excuse to buy the mig-21 when its on sale at discount.. Thanks :)

Sorry for going of topic here but I don't get the chance to speak with campaign creators much :) Have you done other campaigns as well? and will you make more campaigns in the future? I really dig this campaign. Hope to see more. Thanks!

I too have some troubles with this mission. Primarily because I can't seem to contact my wingman... I tune the radio to 127.5 and I've tried all vhf settings. And yes I use right-alt +/ for the radio. but he won't respond or attack targets.. edit: Ok for some reason you need to keep the radio tuned on the default frequency of 124.0 ...

If you start flying helos and WWII planes then Rudder Pedals truly shine. Flaming cliffs 3 not so much. I used to use hat on the back of the saitek throttle to control yaw. Different sims like il-2 sturmovik, rise of flight, helos in DCS I used saitek rudder, then logitech g940 rudder and now because I wanted more sensitivity and control I ended up buying the MFG Crosswind. pretty expensive but for my gaming needs perfect.

Also be sure if he wants a left or right turn!

Make sure there is NO waypoint selected in the waypoint selector pad. If you set the Desired Heading/ desired track in the middle position and you engage route mode on the collective then you will fly the heading/bank/pitch and altitude (if you activate this autopilot bank) in whatever you trim your helicopter. This is indeed great for mountains or even sideways flying. Edit: I'm sorry I thought you meant the position switch next to the baro/radio altimeter. switch. I never set the switch next to the weapon panel to manual. So i don't know if this works.

I don't use my G940 stick as a rumble pad... I use it in Helo's to trim. So I always KNOW where my stick is and I don't have to return to center. Also hands of flying with FFB in Helo's is just easier. In WWII crates I feel when I get in a stall. I must confess I havent flown many DCS WWII crates yet but in RoF, CoD and stuff this is very well simulated. I took the plunge however and Flying the A10-C with the warthog HOTAS is awsome. Flying Helo's I use the warthog throttle but will use the G940 stick. My desk is big enough for both sticks. So easy to swap :) I will however mod my Warthog stick to lengthen the stick. I might then try flying helo's again without FFB.

Have you tried the free planes in DCS World? With detail down your computer is still to slow?

sorry for my misinformation I wasnt aware you could upgrade from Lomac directly to flaming cliffs 2

You need to own Lock On modern air combat to update to Flaming Cliffs 1. You need Flaming Cliffs 1 to update to Flaming Cliffs 2 BUT!!!!!! Flaming Cliffs 3 is DRM free! (No Ubisoft meddling) as of a year now or so. So you can skip everything and just buy Flaming Cliffs 3 on DCS World. Maybe wait for a discount. I got it for 14 dollars I believe.

What planes are you flying? I hope surface stiffening will be present on the WWII Crates but asking this for modern planes is irrelevant. Most planes are fly-by-wire.

My first solution that came into my head would be. 90 - 26 to get to a heading of 360. so 90-26 = 74. Then 360 - 74 = 296. But above calculation is ofcourse also very valid.

Have you checked that you have the proper device ID? [FSF]Ian posted this: local count = 0 local function counter() count = count + 1 return coun end -------DEVICE ID------- devices = {} -- moved forward for correct initialization of another devices -- do not changed folowing sequence for sim devices["ELEC_INTERFACE"] = counter() -- 1 devices["FUELSYS_INTERFACE"] = counter() -- 2 devices["ENGINE_INTERFACE"] = counter() -- 3 devices["HYDRO_SYS_INTERFACE"] = counter() -- 4 devices["ADI_PILOT"] = counter() -- 6 devices["ADI_OPERATOR"] = counter() -- 7 devices["NAVLIGHT_SYSTEM"] = counter() -- 8 devices["SOUND_SYSTEM"] = counter() -- 9 devices["WEAPON_SYS"] = counter() -- 10 They left out ID 5 in the comments. so 6=5, 7=6, 8=7 etc.

From what I can tell modifiying the default or copied lua, there will be 2 identical functions. if they are named the same offcourse. 1 will be greyed out and the other will be clickable. Try the tip posted by Yurgon of putting a space infront of the name so it will appear on the top of the list. That one should work ie. be clickable.

[FSF]Ian, thanks for the excellent walkthrough. It looks like i'm on the right track. I will get this to work quite easily it seems. But could you tell me what the difference is *if any* between your lines in the mods/aircrafts/ka-50/default.lua and my changes in a copied file from mods/aircrafts/ka-50/joystick/default.lua which I renamed to the throttle warthog as registered in the binding page? Throttle - HOTAS Warthog.lua I planted this next to the default.lua in mods/aircrafts/ka-50/joystick {down = iCommandPlane_WeaponMode_switch , up = iCommandPlane_WeaponMode_switch, value_down = 0.2, value_up = 0.1, name = _(' Weapon mode switch up/center'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = iCommandPlane_WeaponMode_switch , up = iCommandPlane_WeaponMode_switch, value_down = 0.0, value_up = 0.1, name = _(' Weapon mode switch down/center'), category = _('Ins Weapons Status and Control Panel PUI-800')}, 3004 = iCommandPlane_WeaponMode_switch so i gather. You have another ID however: cockpit_device_id = 12 Perhaps [3004 IN cockpit_device_id = 12] = iCommandPlane_WeaponMode_switch? I just trying to understand why there are more than 2 ways to make the game do what we want to do. And if any method is better or that it doesnt matter. edit: Ok I'm going with your method [FSF]Ian. My method doesn't work and yours does. The method I used doesn't register values it seems. it works ok for setting up a 2 way switch by sending the same command when released to mimick functionality but cannot register three way switches. No matter in what state i put the switch in, it only cycles one stage up even when I set the switch to down. Thanks for your explanation. I will modify all my binds now using the _device_id

Hmm thanks Yurgon, I'll rename mine as well. I noticed though with setting on/off toggles in KA-50 to the warthog switches that they don't always register. For example I've modded the HMS on/off to repeat the command when set to off in the lua file. Then I bind this to the up position of the EAC switch on my throttle. Sometimes when switching the switch down my helmet sight stays up. When switching up it then switches off my HMS and its now out of sync. Also I've read something about switch states. 0.1, 0.2 etc. Could someone give me an example to set the 3 stages of the missile volleys to the path/alt-hdg/alt switch? So i want to bind high-mid-low to Path/alt-hdg/alt. I am aware that the throttle switch is in fact 2 buttons. Button 28 up and 27 down if not mistaken. So should I take this one line in my Throttle - HOTAS Warthog.lua: {down = iCommandPlane_WeaponMode_switch , name = _('Weapon mode switch'), category = _('Ins Weapons Status and Control Panel PUI-800')}, and modify it into 2 lines? like so? {down = iCommandPlane_WeaponMode_switch , up = iCommandPlane_WeaponMode_switch, value_down = 0.1, value_up = 0.2, name = _('up and middle Weapon mode switch'), category = _('Ins Weapons Status and Control Panel PUI-800')}, Bind this to button 28 in keybinds upstate of autopilot switch {down = iCommandPlane_WeaponMode_switch , up = iCommandPlane_WeaponMode_switch, value_down = 0.3, value_up = 0.2, name = _('down and middle Weapon mode switch'), category = _('Ins Weapons Status and Control Panel PUI-800')}, and bind this to button 27. downstate of the autopilot switch? I know nothing about lua's... But I'm starting to see some logic in it and I remember something about variables from way back when, meddling a tiny bit in Pascal. So please tell me if i'm on the right track and where to find the states of the buttons. The values that is. And offcourse if above 2 lines are the correct way in doing it. Thanks

Hi there, I've copied the default.lua in the joystick map under KA-50. Renamed it to Throttle - HOTAS Warthog.lua editted it and copied it back next to the default.lua I've modified the line for engage/disengage route mode so it has now an up command as well. The same as the down command. The line beneath that already has that. The auto descent mode. Now I binded on the warthog throttle: Speedbrake forward = engage route mode and speedbrake aft = auto descent. all works as intended. namely speedbrake forward engages routemode. and when set back to neutral it disengages or toggles it off. Autodescent already functioned as intended because it used 2 commands. descent mode and descentmode off. But for some reason there are now 2 lines of engage/disengage route mode in the keybinding page in game. There is only one line i can double click and bind the throttle button_8 to. But when I click button 8 the line above that highlights as if choosen. This line is unchangeable in the keybinding page. What did I do? Did i screw something up? Its working as intended though but why are there 2 lines in there? is that the line from the default.lua? Also: is there a way to mod in LONG PRESSES? like the warthog does in A10-C? china hat long forward for example?

I think this is true for people with normal "game" sticks/cyclics. However people with FFB tend to hold in trimmer make their manuever and release it even in FD mode. This is because when you press the trimmer, the cyclic becomes limp compared to the spring force without trim. Making it very easy to swing the cyclic where you want. Also the stick REALLY stays in place when you release the trim button.

Yeah the campaign is awsome! Its very realistic in a sense. In a particular mission briefing the crew freaks out when they hear rebels are spotted with manpads! When flying with cruisespeed at around 80 knots with a max speed of 130 knots the dread is felt when flying through canyons and dropping infantry in contested areas. Its not an easy campaign. you will need to do some practicing with landing. So get familair with in ground effect. Also there is one mission where you are supposed to land on a carrier to take on a passenger. Be sure to have the groundcrew fill up your tank to the brim if you aren't sure of your landing skills. Or you could reserve your fuel by flying economic but I ussually try to fly at top speed because the missions are indeed quite long.

He started the procedure with RightSHIFT+L Thats electrics

Er don't know really.. But I suggest you do some more training in the trimming and AP channels department. Good usage of these features will let you fly steady and hands off even. The KA-50 is the easiest helicopter to fly if you utilize and understand its features. edit:https://www.youtube.com/watch?v=aH4tSiU7TCE This tutorial is assuming you are using a non forcefeedback controller. If you HAVE FFB then flying is even more easy and intuitive. Alas noone makes them anymore and logitech has the patent.

Is there fuel in the tank? :)