StrongHarm

Once I learned to liberate myself from "AP channels always on, no exceptions", I found that I was a much better helo pilot. For instance, instead of retrimming every channel to change heading, I just turn APheading off, yaw over a bit until I get the right track, then turn it back on.. voila. If I'm in a hover and I need to sideslip to get a view around an obstacle, I'll turn off APbank, slip over, then turn it back on.. bam. It's important to view trim in a helo differently than with a fixed wing aircraft. Don't overuse it.

I can confirm this bug still exists. I've tried a few work-arounds, but no joy. It's very frustrating as I'd love to do some AR, but ED does have a lot of irons in the fire. In return for a great product, I can offer only my money and my patience.

EA-6B?!? Oooooo!

Here's a simplified HOTAS reference card I put together in 2010. The source spreadsheet is in the OP if you need it.

Noprob Maverick. I'm sure you have everything covered, especially with the collective experience the 104th. I hate to point out problems without offering to contribute to a solution. If you ever need 'depot level' from an objective outside view, I'm at your disposal. Mustang, I had all the people who were in the 104th server when it was crashing repeatedly move over to mine for a test, with the same map/code/settings and the issue didn't replicate. My theory was a server issue such as a bad routing table somewhere in the local network, or NIC duplex or IPv6 conflicts. With that being said, it's entirely possible that one of the clients connecting to the 104th server had a better route to my server. My route to the 104th is only 5 external hops and 40ms.. but that doesn't mean the rogue client couldn't have an entirely different route to me than to the 104th I guess. If the 104th server is on a shared virtual server instance, I would consider looking into whether the NIC is virtualized. That can cause funkiness if the local node isn't on a dedicated static interface and there's a lot of traffic on the share. The other thing I'd look at is if someone else on a shared NAS is thrashing the disks. That's all irrelevant if it's not in a data center though. Regardless, periodic reboots might refresh route tables, etc. and mitigate having to find that needle in its haystack. Probably all things you guys have already thought about though I'm sure. Good luck to you.

Sunday 04/24 - Report on Crashes: Friday and Saturday I attempted to fly on your server and typically didn't get past TA Alpha before there were mass kicks or complete crashes of the map. After 14 attempts the furthest I got was TA Bravo. Saturday night the crash/massKick frequency increased to where we couldn't get past startup for TA Alpha. I was speaking with people in all the rooms of TS and the reports were consistent. As a test I extracted Armageddon from the temp files into a MIZ. I ran the map from my server with all the same people who were in your server. The result was that we had no issues with mass kicks or crashes. To be clear, I only ran the map from my server as a test. I've since deleted it from my system. Edit: I should add that the above is not at all a complaint, but rather an observation that I hope will help you in resolving the issue. I appreciate the 104th providing an open community server. If I can assist, please PM me and I'll come to your TS. I have over 20 years of hardware/software troubleshooting experience and an intimate knowledge of DCS as I was on the test team for a long time.

I think changing the LUA values may be an overcomplicated solution. I don't want to change the overall 'field of view' or 'angle', I just don't want to have to go to the middle position on the zoom slider and pull it back a bit each time. I've found that quickly adding a curvature to the slider in the control setup accomplishes this simply and quickly (since the root issue is my slider, and not my overall viewAngle values)

If you adjust your default zoom in the LUA, it still doesn't account for the detent on the HOTAS slider not being equal to the default setting of zoom. Of course, you could compensate further back in the LUA value, but you will still have a disparity. I'm not saying everyone has to use this method though, just contributing where I can.

If you're fishing for classified info you're probably not going to find it here. It's against forum rules + most people here who have it are well aware of ALICE. Here's some publicly available info on the Thales Top-Owl sighting system and the TSS that it feeds: https://www.thalesgroup.com/en/worldwide/defence/topowlr-helmet-mounted-sight-and-display-helicopters http://www.militaryaerospace.com/articles/2015/01/lockheed-electrooptics-cobra.html http://www.lockheedmartin.com/us/products/TSS.html [ame]http://www.globalsecurity.org/military/library/budget/fy2016/navy-peds/0604245n_5_pb_2016.pdf[/ame]

I've often been distracted by the fact that the center detent of the slider on the WH HOTAS zoom view is not equal to the default zoom of the cockpit (as with num5). I would have to find the center detent, then pull it back until the zoom was correct. In the heat of battle, any distraction is bad. I found a corrective action. - Control Setup - Axis Assign - Select JoySlider1 next to Zoom View - select Axis Tune - Check box 'Slider' - Set Curvature to -15 (or preference) Your center detent will now have you zoomed back a bit.

Newer Apaches have the Arrowhead system. This has vastly improved optics (both in the eye piece and in the pod). The eye piece isn't just input, it's also output by tracking the eye pupil for precise targeting and sensor queuing. One interesting thing to note about Apache pilots: They learn how to operate their eyes independently of one another. The left eye might be looking straight forward while the right eye is looking down and right! More info: http://www.defenseindustrydaily.com/arrowhead-mtads-pnvs-sensor-system-06461/

Instead of using FD mode for funnels I prefer to turn the HeadingAP channel off. Holding trim or using FD mode is inefficient when the only axis you want to affect is heading. Having HeadingAP off does not make the aircraft unstable. If I haven't flown the Blackshark for a while, I warm up by taking off and performing a funnel around the tower, then practice high speed braking. More on funnels: - Trim out to hover (not autohover) - Turn HeadingAP off - Point nose toward tower about 100ft away - Slowly add on right stick while simultaneously pressing the left pedal to keep nose on tower - Start out a few hundred feet from the tower and concentrate on keeping your altitude and distance from the tower the same, while keeping your nose pointed at the tower - Slowly work your way in closer to the tower and get a feel for control coordination NOTE: When performing this maneuver; your collective, cyclic, and pedals should be in almost constant motion maintaining stable flight. Think of it like playing the drums. The biggest challenge is to get all three working symbiotically. The good news is that once you get it, muscle memory remembers it and you won't have to work so hard at it in the future. **When you get good at it, you should be able to trim yourself into a nice hands off funnel 2k out from targets and destroy them with disgusting efficiency, while making yourself a difficult target. Take note that if you're in a trimmed funnel you'll have to have Heading AP on... and Auto Turn To Target helps a lot too.

Reviving this thread to ask if there's been any work on a "unit detected by radar" or "unit locked by enemy" trigger. This would be great for training exercises in NTTR.

Great post and references Yurgon. Jfri, to reinforce your understanding, after going through Yurgon's material, take a look at this GoogleMap in MGRS. As you zoom into 37T, you'll see LP. As you zoom into LP you'll see the numbers on the bottom and left (eastings and northings) start to change. Viewing it from this perspective gives you a good practical example of how the grids are organized in MGRS.

I see what you mean Raptor9, but attend carefully and consider: it's silly to retrim, or interrupt configuration with FD, when all you want to do is change heading. For this you turn off APheading, change heading, then turn APheading back on and it holds that heading without retrimming all channels when all you're doing is changing heading. Please, consider what I'm saying while performing it in practice. When you try it, you may find that it's clearly a more efficient procedure.

I don't keep all AP channels enabled all the time. I'm a firm believer that making a heading change requires only disabling APheading, making the turn, then re-enabling it. It's foolish to trim while making a heading change (unless there's a big wind change). Although turning off pitch and bank AP compromise the airframe stability, turning off heading AP does not. This in my opinion is a huge inefficiency by most DCS KA-50 pilots.

A question was asked in the comments of my mission NTTR Tank Busting 101 on the user files page, concerning the MGRS reference to the tanker location. I think the answer puts it into perspective better than my past answers in the forums, so I thought I would share. Here's a link to the map that's referred to in the explanation (downloads comments won't allow URLs so it's not in the quote).

Few aircraft have true NOE terrain following capability. The A-10C does, but that's one of the subsystems that ED had to exclude from production. If you think about it, it's not surprising that it's so difficult to do and highly classified.. the civi world is still trying to get a car to drive itself through traffic (reliably). I believe that is small potatoes compared to a high speed aircraft automatically flying NOE without becoming a lawn dart. Where the Blackshark is concerned, the engineering goal was far from bells and whistles. It was to create a low cost, low maintenance, fully capable utilitarian beast of a war pig. I think they hit the hell out of the head of that particular nail.

I thought it was strange too. I've never flown the A-10 IRL, but I flew the C-2A which has even bigger vertical stabilizers, and even an extreme amount of yaw didn't cause that much residual roll. Could it be that abrupt or extreme rudder causes instability that is being compensated by SAS by adding roll in an attempt to stabilize? In the same line of inquiry; could it be that since SAS binds auto rudder to roll, that the code is erroneously causing this to happen in the inverse (roll is bound to yaw as yaw is bound to roll)?

Is this server dead?

Dusty, I'm not seeing that issue. I regularly see T80/90s go down with less than 100 rounds on an optimal run. In TankBusting101 it goes over some procedures. Try those and see how you fare. The important things are that you have PAC on so you'll get a concentrated hit pattern, you should be between .7 and .4nm when you fire, and don't try to breach the front armor (hit it in the rear, or at least in the flanks). Tell me how it goes.

For the Caucasus Version, see this post: http://forums.eagle.ru/showthread.php?t=72549&highlight=tankbusting

I've created a new version of Tankbusting101 specifically for NTTR/DCS2.0. You can find it in user files: https://www.digitalcombatsimulator.com/en/files/1839687/

I've created a new version of Tankbusting101 specifically for NTTR/DCS2.0. You can find it in user files: https://www.digitalcombatsimulator.com/en/files/1839687/

I've created a new version of Tankbusting101 specifically for NTTR/DCS2.0. You can find it in user files: https://www.digitalcombatsimulator.com/en/files/1839687/