drhay53

I noticed on the early mission with the two mosques where the loadout contains flares, the wingman was dropping them as if they were ordnance. He exhausted all flares before he would bring out the GAU-8. This is certainly helping me learn the A10C, although with the mountainous terrain and some need to take out moving targets quick I'm occasionally struggling. I'm really hoping you'll finish the A10C training campaign once A10C II comes out...

Not to be too pessimistic but I hear that and think we are at least another two years out from that being a reality.

Somehow all of the player aircraft are always spawning in an air start, despite them all saying "runway". Has anyone had and solved this problem? Using RC9

I was just looking into this, and one thing the TACAN fix says is required is for the TCN beacon data to be saved in the MC. I was attempting to do the TCN alignment in the first mission of MBOT's dynamic campaign, and I went HSI->DATA->TCN and I noticed that there are no beacons there. I was not able to get it to work on the carrier TCN either; the map never comes up. I haven't been able to test yet on a TCN that's in the MC (the starting point in this mission is too far away from any beacons). But it seems like the big change here is that it used to work for a carrier TCN, and now it doesn't?

The curvature would have an effect depending on how the user was performing certain tests, because the user is likely pulling the stick initially with the same force in both versions, however if the curvature values are different, that could lead to different output values for the control surfaces. So there could be different energy loss scenarios even if ultimately the user is shooting for a specific G for a testing maneuver. Basically just thinking of all of the variables that need to be investigated to make sure that the tests are valid test of the FM only, with no external factors.

Another random thing worth mentioning; make sure your axis curves are set to the same value in your 2.5.5 and 2.5.6 installations for testing, otherwise you're not providing the same inputs to the sim.

Unfortunately it looks like the dcs.log file has been overwritten at this point.

Just had this happen on the debrief screen after hitting quit from ESC menu. The score screen was all funky, like it didn't know what the mission file was, or who the player was. The "End Mission" button did nothing, it depressed but performed no action. The only thing I was allowed to do was an action that lost the progress of having flown the mission. I saved Track and Debrief if that is useful to anyone.

Just to clarify something, as of a couple of days ago, stable and OB are the same build; you're still using the previous stable build, right, not the current one?

TACAN is non-directional. It's just a point in space (literally a signal coming usually from a point a few hundred feet off the middle of the runway). Depending on the plane you're in, you can navigate to the TACAN and set a course line through it that's aligned with whichever end of the runway you want to approach from. On the F10 Map you can see exactly where the TACAN is... it's a little symbol ILS on the other hand can be thought of as "pointing out the end of the runway". If your plane has an ILS in it, it will be using that to provide alignment, heading, and glideslope information. When you contact ATC to report inbound, they give you a bearing and range. That bearing and range effectively tells you which runway to approach. It's a point a few miles (maybe 10?) off the end of the runway they want you to use.

I have been struggling through refueling in the hornet for weeks as well. I posted a not-well-received advice in a thread to use the dampening qualities of the autopilot as an aid. Anyway I have been working towards AAR with no autopilot and for me the answer was that I needed to clean and lubricate my x52 pro. I was getting more sticktion than I thought at small inputs. I play with curvature at 15 btw. Last night after cleaning the stick I got contact during a turn for the first time ever. With no AP aid. And I kept contact for a full 75% fill up. And I managed to actually do that twice. My advice is... When you get pissed off, take a break. Evaluate other causes of your issues (old sticking joystick?) I prefer a 3-4 knot approach speed. Generally focusing something on the tanker that intersects the HUD at the +10 degree ladder is what works for me. Trim up very carefully before going in. Null stick input and monitor changes in roll and pitch (via altitude). This helped me immensely. Make sure you trim at the speed and altitude you'll be contacting. I just do it right before starting my approach. I'm sure you know these things but it's worth mentioning. I cant tell you how many times I've rage shot down the tanker in the practice mission. It gets better the more you get a feel for the plane and just know that you'll get it eventually. But practicing while angry won't get you there!

I swooped back in last minute to pick up Persian Gulf, A10C, and the Enemy Within campaign. Not really even planning on starting to learn the A10C yet, still getting a lot of mileage out of the hornet. But I know I'll want it suddenly sometime in the next few months so I decided to get it while it was on sale.

I think this is unnecessarily harsh and elitist. I find it very difficult to independently manage both the throttle and the stick in a way that avoids PIO without deadening the stick inputs. I have a saitek X52 pro and it could also be that the stick does not have very good control at small input values, due to the tension on the spring. It's easy to overcorrect simply due to the amount of force that's required to set the spring in motion. With all that said, I view this merely as a stepping stone until I have muscle memory on the throttle hand and can smoothly manage my speed without having to think too much about that hand. Once I have that hand down, I will transition the stick to normal input. I was offering this as a learning path to lessen the pain, not a long-term solution. I fully understand that it will take many (10's to 100's of) hours of practice to get better at this. To me it's acceptable to make one aspect just a little easier by using a real function of the aircraft. Try not to discourage people by telling them that their method of practicing and learning is "wrong".

In the hornet, if you activate autopilot then move the stick slightly, the FCS adds a pretty extensive dampening to your stick movements. The autopilot will show as being off, but you know FCS still has dampening because if you move the stick too far the aircraft jumps quickly when FCS releases control fully back. So, on approach to the tanker, turn AP on to BALT or something, then move the stick a bit to get into dampened mode. Now it will be much harder to get into PIO. For me the throttle is really hard to learn. Just remember to constantly rock the throttle. You can't just set it in one spot and forget it. If I focus too much on lining up the basket, I end up forgetting to rock the throttle, and then I over correct on the throttle, and then I have to just reset and start all over. Rocking the throttle with the left hand should be muscle memory. Practice it until you don't even have to think about it. It's the same motion you're looking for to stay on-speed for landing. Check out how much this hornet pilot is rocking the throttle for landing: And here's a link regarding use of AP for dampening control inputs: I'm not elite or anything. I'm still not very good at AAR. But these are the motions I plan to go through to practice it until it's muscle memory for me. YMMV of course.

That's exactly what I'm trying to do but the SA-6 keeps getting me before I can get all my bombs released. Will just keep at it I guess.

having trouble on mission5, OCA West. Spoiler alert. I can't seem to get my bombs away before the SA-6 gets me. Any tips for how you approached this?

My first attempt I got -3 points :D I tried it a dozen or so times and the improvement was obvious. Even managed to actually land once! One thing I constantly get docked for is being too close to the carrier after the break. I'm not even turning at 1% of airspeed anymore, I basically pull a steady 2-2.5G all the way through the break. So I'm not sure why I'm always ending up < 1 nm from the carrier on the downwind. Any suggestions? I am pretty terrible in the final turn and approach, and not so great at flying on speed and altitude on the downwind..... so like 3/4 of the procedure I'm not any good at. But, despite that, there is evidence that I can at least get on deck after really only a short amount of practice with this mission. It's way better than anything the game provides for training.

For me it’s not the wallet... a few years ago I had a really bad bout of migraines and ever since I get motion sickness incredibly easily. When I was younger I was roller coaster kind of person, when I went to the amusement park I’d ride them all day. Now I can feel every little oscillation in an airplane and I get nauseated fast. Even simple little phone VR apps disorient me fast. I know there is some hope of acclimating yourself to VR, but I’m not looking to drop a few hundred bucks on something I may never be able to use. So for now, head tracking is the most sensical next step. Although I’m also thinking of going less than trackir, because it’s not a huge step from there to VR in cost, really, and so it’s kind of tempting to just push on up and try it, and I’m just not sure it’s a good idea.

Came back to DCS after a few years. Picked up my first HiFi module (went with the hornet so I could have lots of options about what to do). Picked up NTTR and am guessing I will get Persian Gulf before the end of the sale. Also grabbed a couple of campaigns, the Hornet BFM and F-15C Georgian War and BFM campaigns. Although now that I have the hornet, my interest in the FC3 planes has greatly diminished. I really like having fewer bindings to remember. Trying to find something that will definitively keep me playing long-term. Only get an hour or two a night to play. The biggest missing piece in my setup is some type of head tracking and that is really starting to keep me from diving into A/A any further. Just finding it too hard to fly and manually move the camera around.

These are amazing, thanks so much for putting them out. In mission 2, the escort for Texaco, as soon as I got close to the tanker, I was told to RTB. The briefing makes it seem like I'm supposed to stay in formation for quite a while. I went ahead and RTB right away, and the result was 100%. But I was a little confused. Was I supposed to go ahead and stay for a bit even though I got the trigger telling me to RTB? In mission 3, as I was taxiing to the runway, I stopped before the threshold and sent out the comms to request takeoff. My wingman then crashed into me. I've noticed this in other missions too, is there any way to stop your wingman from taxiing into you?

I saw the same easterly target in a CAS mission, but I thought it looked to me like the target was at the ingress waypoint. edit: that seems to be what your screenshot shows as well? edit 2: Ah, in my next CAS mission I'm also seeing a target that's ~50 nm east of the actual battle. It looks like it also affects the CAP orbits, which are shifted quite east as well.

Another question, I was having bad issues with performance so I turned on the unit culling. Are those flights simulated in the background or is it as if they never existed? Also, what is the distance calculated from? I don't want to end up in a situation where I significantly hinder one side because of the culling range. First flight with it turned on was totally smooth in FPS, so I want to leave it on, but I want to make sure I know how it works. edit: and a third question. How many of the flight tasks actually work? I.e. if I set a flight to "intercept", the details aren't really filled in on the waypoints section. What will that flight do? There a few other tasks that I don't know if I should use them or not because nothing is filled in. Random note. My last flight I noticed a CAP flight went 70 nm off course in order to attack some planes that were on the ground at an airport. of course, both F18's in the wing were shot down by SAMs.

I started a new campaign with RC7, USA Vs RUS in Caucasus, and my airfield has some RUS units (SU-27, SU-25T, Ka-50, at least). Is that intended? Also what do each of the "frontline operations" settings do? I don't see them in your documentation. edit: my bad, yeah, I see those planes in the list.

Thanks alot, working fine now. Used the sync tool for the first time as well.

As suggested here: https://forums.eagle.ru/showthread.php?t=119849 Disabling force feedback was the only thing that made my trim work again. I suspect the warnings I am hearing are the RWR, not sure. First time in the A10A and not a ton of experience.