EinsteinEP

Passwords work.

While it is true that the autopilot can only provide axis stabilization in F/D mode, this does not affect trim, which is independent of autopilot.

with BackspaceTouché Enflambé. Sorry, couldn't help myself.

I got all excited when I saw your link to Jesus, Nighthawk, but, it looks like I haven't found Him!

Great setup! Any chance we can see shots with the displays working? I'm curious to see how it all looks.

You can "use" 4:3 or 16:10 monitors, Szelma was answering your question which one was "better". I prefer widescreen (16:10 or 16:9) over the 4:3 boxes because you get a little more peripheral vision, and the debate between 16:10 and 16:9 is trivial, IMHO. The typical HD aspect ratio is 16:9, so when viewing HD on a 16:10, there'll be little black bars somewhere on the monitor, which upsets the HD purists to no end. I'd also add the bigger the monitor the better, as long as it still fits within your desk space. I recently went from a 19" 4:3 to a 24" 16:10 and am loving it.

I totally see where the confusion is coming from: there's a switch at the front of the cockpit that says "Inner", "Auto", and "Outer" and is labeled "NDB". When you flip these switches the ADF needle points to the different MARKERS. [edit: thanks for the PM, EvilBivol! Saved me from making even MORE of an a$$ of myself. Granted, I'm no commerical flyer, but as a private pilot in the US, I've never run into the practice of placing NDBs with both the Inner and Outer markers. They're rather sparse on the west coast of the West, at least. I humbly concede and owe Frederf an apology - apparently the correct terminology IS Inner NDB and Outer NDB when flying in Russia! Guess I better go relearn my radio navigation! Spasibo!]

I'm really not trying to argue about sematics, but while there are IMs, OMs, and NDBs there's no such thing as IM NDBs and OM NDBs: you use an ADF to navigate via NDBs while in flight and your plane (if equipped) sounds an alert when you fly over an IM, MM, or OM on final approach. You do not get bearings to markers and there are no alarms when you fly over NDBs. They are two separate things. In fact, there's a dead zone over the top of an NDB and markers only transmit straight up, NDBs each have unique frequencies and markers all transmit on the same freq, and NDBs are high powered while markers are very low powered, you use NDBs while navigating between airfields and only use markers when on final approach, so one could say they're exact opposites. Calling NDBs by marker terminology makes it more confusing! NDBs are identified by their frequency, not what marker they happen to be close to (e.g., "I'm headed towards the 373 NDB and 225 is 20 deg to my right."). NDBs can be associated with geographical features (e.g., "I'm picking up the Tuapse NDB, but the Kiorsky field NDB is still too far away..."). This thread really has my curiousity peaked - I'll have to check it out tonight.

I may be misreading your post, EvilBivol-1. If so, please accept my humble apologies in advance. NDBs transmit in all directions, hence the nomenclature "non-directional beacons", and are used in radio navigation. NDBs are very different beings than the inner, middle, and outer markers that are placed along runway approaches for use in making landing approaches using instruments instead of visual cues. Markers are radio beacons, to be sure, but they transmit directly up (a cone of only about 45deg from straight up, I think) and are very low powered (3 W). The lowest power NDBs are around 50W but can get up to 2,000+ W. I don't have statistics, but I'd assume 1,000W is pretty standard power for an NDB. An ILS system (including the OMI markers) may be brought down, due to maintenance or faults, but the marker beacons are not switched off and on depending on which way the wind is going. Every marker transmits at the same carrier freq (75 MHz), with the outer, middle, and inner markers modulated with a specific tone for their position (e.g., there's a characteristic tone for outer markers that's distinguishable from the inner and middle marker tones),but they can't conflict with each other since they only transmit straight up! Some confusion may arise from the fact that NDBs are SOMETIMES co-located with a marker, but they are still two separate transmitters with two separate purposes. The just happen to be roommates. Every marker beacons transmit on a carrier frequency of 75 MHz while each NDB has a unique frequency between 190 kHz to 535 kHz. NDBs are placed and freqs are assigned so that there are no conflicts between them - although mistakes CAN happen, this would be a big mistake, and I sincerely doubt that the FAA would tolerate overlapping NDBs for long. I've assumed NDBs and markers are modeled as separate thingies in Black Shark (haven't experimented with radio nav yet - still working on hovering without crashing!) but this post makes me wonder if there hasn't been some confusion between markers and NDBs... will have to check now.

Mig29movt, I did search for this bug before posting, but didn't find any relevant posts: probably wrong search terms, or something else user-related. Could you provide the link to the proper post? Thanks!

Bug description: While on ground, a long rectangular video "artifact" appears on the ground texture when looking out the window. The artifact is light colored, almost white, but is not solid or opaque (e.g., ground texture shows through). The artifact rotates slightly as I turn my view (with TrackIR). The artifact does not appear to affect any of the internal cockpit graphics and I haven't seen it from an external camera. Steps to reproduce / Conditions of occurrence Artifact is present right from the start, even before I flip a single switch. Artifact is also present when landing on the ground after a flight. I don't see it in the air. I haven't played many missions, but it's been in all the training missions, the Death Valley mission, etc. PC Configuration ASUS P-5e SLI motherboard, 2GB RAM, E6750 dual core processor, no changes to affinity via task manager, eVGA 8800GT graphics card, no overclock, all default settings. Artifact shows on Low and Med video settings in Black Shark (haven't tried High, but game probably won't run that great on High anyways). Monitor is 24" Widescreen Samsung 2443 BWX. Attachments 3 screenshots included (hopefully). Same mission, same time, I just rotated my view (via TrackIR) to show.

I haven't checked in Black Shark but in real life, pilots get wind bearing based on the direction the wind is coming FROM. For example, a pilot on runway 16 knows he's pointed at 160 deg magnetic from the runway number. If the wind is 160 at 5 kts, then he knows that he's got a 5kt headwind. Hopefully this is how Black Shark implements winds, although it doesn't sound like it based on your observations (ATC giving opposite approach headings, heli "windmilling" to opposite heading). I've never heard of the weather being called "meteo" - maybe this is a Russian thing, hence the different convention? Anyways, good luck!

Same comment as CyBerkut. Even though the word "left" doesn't appear, it's implied. If it helps, read "alt" as "left alt", "ctrl" as "left ctrl", and "shift" ans "left shift" and you're good. My x52 Pro profile with 6.2.2.4 works just fine with Black Shark, left and right modifiers included.

Is there a way to determine the status of the INU alignment in the Ka-50? e.g., in F-16s there's a display that gives the current "mode" of the INS and the word "ALIGN" blinks on the HUD once the INS has achieved a certain level of alignment. Any such indication on DCS Black Shark? If not, what about the real world Ka-50?

Not sure if this applies, but if I try to use a key that's ALSO being used by TrackIR, it doesn't get through to the game (BS, IL2, etc.).

WANT !!!