BBQ

It's a nasty bit of high altitude mountain flying -- but I didn't know that "repair" was an option. Does that automatically happen when you refuel/rearm as long as the engines are off? I refueled with engines on - throttles to idle, but did not turn engines completely off.

I'm testing a mission, and realized when I had landed, that I missed an objective, and need to refuel and head back out. However, before I landed, I noticed my pitch autopilot channel was disengaged. I thought I might have taken some small arms fire or something, and since I was about to end the mission and land, didn't bother to investigate codes presented on EKRAN. Then I realized I missed an objective -- but since I had landed, the EKRAN apparently reset/finished it's fourth cycle, and so now I'm trying to figure out what is wrong with that channel. Hydraulics are all good -- the gauges all read between the lines. I've tried emergency disengage autopilot channels, and then re-enabled them each -- but the Pitch channel refuses to activate. I'm trying to look at this problem as if I'm still in flight, when in fact I'm on the runway, ready to take-off again -- the mission does not allow external views, so I can't do a BDA on the aircraft externally. Any troubleshooting advice? All other systems appear solid. :helpsmilie:

+1 :)

To clarify, you mean keep it on your 3/9 when you say "beam", right?

I suggest posting a track, as for me, I haven't had such a problem.

Yup, that's the way it's done! That video inspires me every time I see it: pure, undiluted, 100% talent. What a show!

Here is another excellent resource -- a real gem that I only found a month or so ago, having no idea that it existed. Very well written -- a whole article on the topic -- but you'll regret not reading the entire "series" of articles that are linked at the bottom!

I was specifically responding to JG14_Smil, which one would think, was obvious, since I quoted him in my initial response. However, I didn't mean to high-jack the thread.

Ka-50 Spot Light

The analogies are endless ... someone sees you fly and asks "Wow, what HOTAS do you use?" much like as a photographer I invariably hear "Wow, what kind of camera is that?" after looking at nice photo I had just taken. So I'll borrow an age-old adage from photography, and slightly modify: IT'S NOT THE HOTAS, IT'S THE PILOT! (From "It's not the camera, it's the photographer!")

Then how is it that I can fly like a hot knife through butter with zero adjustments to curve, deadzones, etc.? :music_whistling:

After many years of frustrating (though fun) flights in the Ka-50, and many different "styles" of flying and using the trim, my advice is to first and foremost understand how the trim system works, and then master basic flight maneuvers like turning, hovering, cruise, etc. You said you've pretty much covered those already -- but I would guess that you really haven't (of course I believe you when you say you have -- but two years from now you'll look back and laugh most likely, on your statement). It's not the stick, nor a deadzone, nor a curve. Read all you can in the "trim" and "autopilot" threads. Aside from luck -- I don't see how it would be possible for a new pilot to consistently perform advanced maneuvers like the split - s immelman, etc.

"233, Naval, return to base." Where 233 is the callsign to whom the communication is directed, and Naval is the callsign from whom the communication was sent. (courtesy of vergeev group) AFAIK, this is how it works in most Airforces. Because lots of people are listening, first bit of information is to be the intended recipient of the call, followed by author of the call. From what I understand, in Russia there is a lot more communication between tactical controllers (not on the battlefield per se) and each flight -- unlike, for example, a US flight that mainly communicates within its own flight, or perhaps other flights in a package (or other "in the field" assets such as AWACS/JSTARS, JTAC).

I actually dont use Fish's method either - but still good video to learn trackIR software. i have smoothing maxed out and speed set to 0.8. make sure after setting smoothing and speed to close trackIR completely and then reopen to make sure changes stuck. Often i would changes and the later reboot and changes always reverted w/o me knowing, causing great frustration!

Dudester -- my advice -- spend some time tweaking your trackIR. It's one of those things that pays off in the way of not being frustrated by little things here and there -- just not enough to get you to tweak trackIR. Spend 15 minutes on it and get it perfect, once and for all -- and you'll save yourself a lot of fretful startups. Better yet, watch this great tutorial from Fish:

You might need some more coffee ;) Seriously though -- I'm no expert and could definately be wrong, but as I understand it, it seems Sochi does have an NDB with a callsign and a frequency. AFAIK, the ARK-22 homes in on NDB's. From Wikipedia: Here is the code from original file -- you can see the callsign is "CO" and the freq is 761000.0: [sochi] = { -- URSS Sochi - Adler (Russia) type =BEACON_TYPE_AIRPORT_HOMER_WITH_MARKER, [b][color="Red"]callsign = "СО",[/color][/b] [b][color="Red"]frequency = 761000.0,[/color][/b] position = { Z0 = -20.0, S0 = -1120 }, }, ILS:frequency(111.1, 'ISO', math.rad(3.0)) Here's a shot of the mission editor:

I'll keep my eyes peeled for an update -- again, thanks.

I loaded it up -- and it didn't fix Sochi -- compared the new file with the old, and the only difference between the two had to do with Kutaisi. No change in relation to Sochi. (beacons.lua)

JG14_Smil -- thank you! Much appreciated.

There's a man -- took his licks and can admit a mistake. Respect --> inbound

Bug description: The list of ADF presets on the right side wall of the cockpit will not display information for Sochi (URSS) airdrome. I've not tested every single airdrome, but I did spot check a few others that aren't displayed by default, and they all worked properly. Steps to reproduce: Open the following file and replace any of the existing entries with "Sochi" (see code snippet below): C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\ARK\ARK.lua mode = ADF_ADF receiver_mode = ADF_RECEIVER_TLF homer_selection_method = ADF_HOMER_SELECTION_AUTO channel = 1 volume = 0.5 channels = { [1] = runway_homer_pair(Airdrome[Krasnodar] ,nil,localizedAirdromeName(terrainAirdromes[Krasnodar])), [2] = runway_homer_pair(Airdrome[MinVody] ,nil,localizedAirdromeName(terrainAirdromes[MinVody])), [3] = runway_homer_pair(Airdrome[sochi] ,nil,localizedAirdromeName(terrainAirdromes[sochi])), [4] = runway_homer_pair(Airdrome[Anapa] ,nil,localizedAirdromeName(terrainAirdromes[Anapa])), [5] = runway_homer_pair(Airdrome[Mozdok] ,nil,localizedAirdromeName(terrainAirdromes[Mozdok])), [6] = runway_homer_pair(Airdrome[Nalchick] ,nil,localizedAirdromeName(terrainAirdromes[Nalchick])), [7] = runway_homer_pair(Airdrome[Maykop] ,nil,localizedAirdromeName(terrainAirdromes[Maykop])), [8] = { [ADF_HOMER_FAR] = NDB(beacons["Кисловодск"]), [ADF_HOMER_NEAR] = NDB(beacons["Передовая"]) } } PC Configuration N/A Attachments None NOTES: Although the screenshot shows I'm using a modded cockpit (RICARDO's), I tested with the default cockpit and have no other mods installed. Having searched for a solution, I came across a thread suggesting the ARK.lua file be added to the x.miz file as a workaround -- however, this did not solve the problem for me.

Ok then -- a compromise -- $10 per AFM for FC3 owners. I imagine the team in Moscow is trying to come up with a figure somewhere between $5 and $15 per AFM for FC3 owners. I hope so, at least. In any event, I'll purchase all of them no matter the price -- just wish I hadn't bought FC3 yesterday, as I won't ever use it/fly it -- buying it soley on the (false) premise that I would get the AFMs as a free update, at which point I would fly some of the FC3 aircraft.

i just purchased FC3 on sale thinking that that would be better than buying the forthcoming, Individual modules. My mistake was listening to the testers. Having been one myself, i assumed they posted info with extreme confidence, and would furthermore ask them to be careful when posting info in the future -- especially any info regarding pricing/licensing. In the end, no big deal as i'm happy to support this product any way that i can -- but if i had been a student or something, i would have sorely missed that $29.95. UPDATE: I just re-read thread and cannot find post that led me to believe that the FC3 owners would get individual module level updates for free - so either it was deleted or simply my mistake, and I misunderstood. At any rate (no pun intended) it's very clear now.

Refactoring -- make code more efficient = better performance = happy customer

New mustang in the garage :)