Sylvan

I had the exact same thought! Decided not to post it in case it was wrong. But I'll gladly corroborate your post cause my muscle memory tells me the same thing! :thumbup:

GUARD frequency and GUARD switch behavior Hey Headspace! I know you're busy and that TARS is at the bottom of your list right now but I'm going to put this request/suggestion here for later reference! The question is in relation to the GUARD frequency in the Ka-50. The way GUARD is supposed to work is that it is an extra frequency that the radio always listens to for emergency/priority transmissions. For civilian traffic this frequency is 121.500 and for military it is 243.000. The A-10 is able to do both. In the Ka-50 however the GUARD switch causes the R-800 radio to tune to 121.500 in receive only mode, which is not really practical for any usage. The question then becomes: is this behaviour something you as the developer of TARS has any sort of control over? Can you make the GUARD behave as one would expect, with the R-800 always listening in on 121.500 in addition to whatever it is tuned to? Or is this behaviour dictated by DCS? We would really appreciate having the ability to do emergency transmission on GUARD. As always, thanks for your amazing work and I think I believe I speak for the entire community when I say that we're looking forward to when your threat picture clears and you can find the time to work on TARS again! :D

While we're on the topic -- what's a reliable way of estimating where to aim with S-8OM's? I've been using the default S-8 ballistics profile, placing myself at approximately 4,5 km out and then just aiming up "a bit", approximately 10-15 degrees. That seems to land the flares mostly in the general vicinity of the target, most of the times close enough to get a Shkval lock, although far from perfect and with great variance depending on terrain, my altitude etc. Is there a better, more proven way?

You are indeed correct, Sir, they're working just fine. I was firing them into the ground... :music_whistling:

Hey guys, I recently went to brush up on my skills with the illumination rocket, but... Is it just me or do they no longer actually illuminate? Edit: Never mind, they do, it was just me being stupid... I seem to remember employing them with success before, but now they just shoot off into the darkness without ever actually lighting up...? :wassat:

Anyone else getting an immediate crash to desktop with the message "DCS has stopped working" after applying the 1.2.7 update & repair procedure? Here's the error signature: Problem signature: Problem Event Name: APPCRASH Application Name: Launcher.exe_DCS Application Version: 1.2.7.23097 Application Timestamp: 52b97dcf Fault Module Name: DXRenderer.dll Fault Module Version: 1.2.7.23097 Fault Module Timestamp: 52b97863 Exception Code: c0000005 Exception Offset: 0000000000024c8b OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1044 Additional Information 1: 2df6 Additional Information 2: 2df67ce17c6b1fa82ac0fbe2816907f6 Additional Information 3: 492a Additional Information 4: 492a1ea299e8af88b2dc69f8ea62325e

I don't belive OP was refering to the RMI needles. Here's a screenshot of figure 7-8 from the relevant page in the manual: I believe what OP means is the orange triangle in the middle of the arc page, not the red and yellow arrowhead indicators on the compass line. To my knowledge this orange symbology is not explained anywhere in the manual. Neither have I seen anything like this in-game. Possibly some kind of representation of a geographical feature, but this is just guessing.

I think what is causing the behaviour you describe is the autopilot attitude hold. (ATTitude, not ALTitude.) You seem to understand the trimmer but not the autopilot. The trimmer button gives input to both systems at the same time. Here's how attitude hold works: With FD off, every time you release the trimmer you are setting your desired attitude, meaning a level of pitch, roll and a heading that you want the autopilot to hold for you. For instance, when you are trimmed for forward flight, you have pitched the nose down and told the attitude hold autopilot to maintain this attitude, and the autopilot will use its 20% authority to try and maintain the nose down. When you pull back and then re-trim, the releasing of the trimmer button supplies the attitude hold mode with new constraints and starts to apply it's authority to attain that attitude. Those extra 8-10° of pitch is probably the autopilot ceasing to try to push the nose down and starting to try and hold the attitude you just told it to hold. The solution, like Fishbreath mentioned above, is changing the way you trim. Either perform constant presses on the trim button through the entire manouver, like most russian pilots do, or press and hold the trimmer button when you manouver, like most western pilots do. I prefer the latter. The pressing and holding of the trimmer button will temporarily disable the attitude hold mode (effectively the same as enabling the FD) while the button is held and re-engage it when you release it.

Minutes and tenths of minutes -- on a bearing indication? :unsure: Not that I don't believe you, but when would a pilot ever need that much precision?

Hi guys! I have a question about the "heading/range to target point" readout on the PVI-800 panel. By this I mean the button on the bottom right of the PVI-800. I searched for it but couldn't find it had been asked before. In the manual (p. 6-65) it says that the readout should contain the heading in degrees in the left part of the upper row and the distance to target in kilomters on the bottom row. These work as described. However in the game there appears an extra set of three digits in the top row on the right which aren't described in the manual. Example: I spawned in the "Take off from Beslan" quickstart mission, designated a target point to the right of the runway, heading 124° and 3,6 km away. I select NAV/TGT 1 on the PVI and hit the HEAD/RA TGT PNT button. The display top row now reads 124'30'0 and the bottom row reads 003'6. At first I thought it might be the reciprocal heading, so to get some more data I designated another target point bearing 110° and 4,5 km away. The readout is now 110'22'2 and 004'5, which shows that this is clearly something else than the reciprocal. In the DTA/DH mode these top three digits are estimated flight time to the target in minutes, but that doesn't fit these values either. When out flying, these three numbers change wildly, although sometimes if you're flying directly at a target point it seems to be counting, sometimes up, sometimes down. So does anyone know what those three right most digits are supposed to mean?

No, the ABRIS and the PVI-800 maintain separate databases, meaning if you alter a waypoint in the PVI-800 it won't affect the currently loaded ABRIS flight plan at all, and vice versa.

Navigation in the Black Shark is mostly a matter of learning how to use the PVI-800 and the ABRIS. Both systems are (reasonably) well explained in the manual and there are also several good tutorials on the web if you search for it, for example the Producer's Notes that someone kindly gathered in HD on their YouTube channel: http://forums.eagle.ru/showthread.php?t=56884 It's going to take you hours of studying and practice if you want to completely understand how to utilize these systems properly so dig in! :)

I was looking around the map when I discovered something. Have a look at this imgur album: http://imgur.com/a/5xflg Makes you wonder how old the map data that DCS World is built on is. A dam that is modeled in the game is the Inguri dam, which began construction in 1961 and became operational in 1987 so I'm guessing the map data is from somewhere around the mid 1960 and 1980. Not saying that this is some big deal, I just found it interesting and thought my fellow pilots also might. :)

This is from the AUTOPILOT NOTES.docx that has been circulating around: What is meant by double strokes?

Good answer, Auger. Thanks! :thumbup:

I agree wholeheartedly! And our opponents seem pretty quick on the trigger as well. It seems the second they get eyes on even a single rotor blade they start acquiring and getting ready to fire. There should be some form of delay at least.

More like crazy multi-billionaire artillery! :megalol:

Good answers! The off-axis effect of the tail rotor had never occured to me. Thanks!

Hello fellow rotorheads! I've recently started trying to learn the Mi-8, the big old glorious beauty of a machine. I'm struggling quite a bit and I'm hoping you could help me out with a few newb questions. 1: Coming from the wonderful counter-rotating world of the Black Shark, having to do my own counter-torquing is quite new and it's taking me a while to master the pedals. I understand the mechanics of why I need to feed right rudder to counter torque while applying lift with the collective. What I don't understand, however, is why the Mi-8 seems to require left pedal to avoid yawing to the right while parked on the ground. Why is this? As I practice trying to hover-taxi along the taxilanes and runways of Georgia, two questions form: 2: I watched one of my own tracks and noticed I'm yawed quite a bit off-center while I'm trying to fly straight. I also notice I constantly have to correct my position in the chair as I'm leaning to the right in an attempt to aim down the center line of the aircraft. Any tips on how to maintain orientation along a straight line? Like in the Huey where I've been told to aim along an imaginary line through the HSI and ADI to fly straight. Where's that line in the Mi-8? I can't seem to find it. 3: The amount of right cyclic I have to apply to avoid rolling to the left while hover taxiing slowly is quite surprising. Why is this? Help a n00b out! :)

Is this the one you're thinking of? http://simhq.com/forum/ubbthreads.php/topics/2626185/ The post on simhq says it's been made DCS World compatible. I have no idea if that is the case but it's worth a shot.

Doh! Didn't know that! That information would have been really helpful to a friend of mine who recently bought it to make better missions for the shark... :doh:

Also note that the target point tab won't be available to you unless you actually have the Ka-50 module installed.

I'm surprised to see this. This means the DCS Manual lied to me! :noexpression: (DCS Black Shark manual P 11-13)

Hi, Where are the R828 preset frequencies defined? I've been searching quite a lot for the answer to this, but couldn't find it either on here or on Google. Most seem to point to the R_828.lua file. Here's what mine says: DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\R-828\R_828.lua: squelch = true volume = 0.5 channel = 0 presets = {} presets[1] = 35654000.0 presets[2] = 25675000.0 -- radio Mayak presets[3] = 48543500.0 presets[4] = 35657500.0 I have not manually modified this file in any way. Neither have I installed any mods. Previously there used to be ten different presets, but as of later versions of DCS there are only these four. However, when I go in-game with TARS enabled and try to tune the various presets on my R828, my TARS status panel readout shows the following frequencies: 35.650 25.675 48.550 35.650 58.400 46.400 42.700 37.725 46.325 22.975 As you can see, the first, third and fourth frequencies do not match the contents of R_828.lua. And where do presets 5 through 10 come from since they're not defined in the file? What's going on here? :huh:

I hope that registered with everyone. Free will always take a backseat to paid, this shouldn't come as a surprise to anyone. Headspace has put A LOT of work into TARS. A lot of us are using it, submitting bugs (mostly poorly documented), asking Headspace (directly!) for tech support, requesting features (many of them impossible) etc. yet most of us hasn't paid one bit for any of this. I suspect we must appear like a bunch of whining two-year-olds most of the time. I'm willing to bet that less than half of the commenters in this thread has donated anything to the TARS project. (I don't have any evidence for this claim but it would take Headspace actively denying it for me to believe otherwise). This is not okay, people. TARS is effing brilliant and that kind of quality does not come for free. Let's keep it alive. Programmer no money for coffee; programmer no make good program! In short (and sorry for the rant): Donate, people!