BBQ

You nailed it seikdel -- I had indeed, forgot to switch on the INU at startup!

K -- let me put this question another way: I was about to land, and verified the three green lights indicating my gear was down and locked. I now know that those lights have no relationship to your gear actually being operable, as when I landed, I didn't have any nose gear. But hey, the green nose gear light said I was good to go, so I went. BTW -- I was not asking the dev team to put it at the top of the list so that it was the first thing done when the office opened up in the morning. I was attempting to make the simulation better (if indeed it is a bug), but either way, when and if the bug gets fixed, and the order in which it is fixed in relation to other bugs is so off-topic that the mention of it borders on thread high-jacking. I could really give a **it which bugs someone else would prefer to have addressed first, nor do I care whether or not someone thinks my point was "moot" or not, though I do appreciate the opportunity to use the word "moot" in a sentence.

The entire strut.

So why not then, just have one light? Red up, green down and locked? I figured since there are three lights, that they can individually show status -- and if nose gear is inoperable, then if not red, then unlit, but certainly not green -- just my two cents.

I pledged yesterday, I hope there's one heck-of-a push for the last two days! I wonder if that's common for kick starter projects -- kinda makes sense I guess. With the announcement of Maddox games joining up (if that indeed is true -- I didn't read the whole thread), it seems the disparate parts of the flight simulation industry are in lead pursuit, and forming up behind the lead, our very own Eagle Dynamics/The Fighter Collection team!

Bug description: During my take-off it appears my nose gear was blown off/destroyed -- but I continued with the mission, eventually arriving back at Sochi to land. However, I noticed that I still had three green lights indicating all of my landing gear checked out OK. Should not the light representing the nose gear (of the three landing gear status lights) turn red because of the damage? I took off around 17:10 -- just start track and fast forward until I'm rolling down the runway -- Note: I am using a cockpit mod -- Ricardo's HD Russian variety. I didn't have time to test it with default cockpit -- but will do so this evening (EST). Steps to reproduce: Start mission and be sure to taxi to runway, and then do a rolling take-off. PC Configuration: * See attached XML file (Speccy) Attachments: noseGearLight.zip comprised of the following files: Track Logs PC Specs

Thanks! Back to Sochi ...

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).

Just wanted to say I'm extremely grateful for this perfect little application -- finally I think force feedback is working as designed for my Ka-50. Rep inbound!

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.