Arbil

I'd be interested in knowing how I screwed it up. What trigger I missed, if you don't mind sharing/speculating.

After being cleared to refuel and then RTB I missed a trigger or something went wrong, not sure which. I may have missed something when reading the toast message, I don' think I did, but it told me to refuel up to 8000 and hit space to clear that message. I did this, refueled to 8000lbs, then disconnected and radioed the tanker and told him abort refueling. I formed up on his right wing and nothing happened after that. I decided to just go ahead and RTB and landed back at mother and the mission seems to have completed as I am on mission 4 now. But I feel like I should have got some more dialog and whatnot after that final refuel. Please advise. Absolutely loving the campaign so far. Superb job.

I literally just slewed the TGP around using the coords that are displayed in the upper left of the TGP screen until I got the numbers he gave me. Voila, the house I needed to bomb was right there. No technical know-how needed.

I think you are misunderstanding what people are saying here. At the end of the mission when returning to the boat for the case III landing. Is there a way to get Smoke to do his own case iii instead of him following you in the case iii pattern and all the way down to the boat?

Is this working with the comms as of now? As far as I can tell, but I haven't tested much, after you bolter and re-comm in to mother they will always send you back to the stack to start from scratch. Hopefully it's planned to have a more dynamic response from mother where you don't have to restart the comm procedure on a case-iii bolter and just do the procedure and then get a call to turn downwind then rejoin the final bearing instead of getting told to go back to the stack and do the whole thing over again.

I'd like an option added for the volume of the tires locking up and skidding to be boosted so it's really easy to hear in the cockpit, just like the afterburner volume boost option. As it is now it's really hard to tell when I'm locking up the tires and skidding during landings on airfields.

https://redd.it/kbyuuy Bump ...

What exactly do you mean by, "... behave as it should ..."? Should the realistic slew option be affecting the behavior of the EXP modes or shouldn't it? And if not, what is the reasoning behind it being implemented for the MAV and not the AG radar EXP trapezoid?

Not sure if I am doing something wrong or missing something but I cannot get my wingman to respond to anything(formation changes or anything) and help with the attacking of the targets. Makes this mission much harder than it should be. Could someone else please try and see if you can get your wingman to respond to anything?

There's some serious misinformation that will lead to negative training in some of these comments. Some people saying forget about trim and that navy pilots never flair. Both are incorrect. If you're having that much trouble landing you need to practice getting the jet dirty/configured for landing, which includes trimming the e-bracket with the velocity vector, which in the hornet should be easy because the fcs. Trim the vv to the center of the e-bracket and you really don't need to adjust it at all after that. Only as you fly around and burn fuel/lose weight will slight adjustments be needed. Get the jet like this then just practice keeping it level at the same altitude with nothing but the throttle. Do that for hours. And navy pilots absolutely will flair for land based landings if they are over weight, same weight restrictions as carrier landings, 33k and above you flair. On the boat they will dump fuel to get under they weight, so in a sense never flairing on the boat is correct, but on land, flairs sometimes do happen. This is in the natops.

+1 thank you. I kept wanting to bump the old thread but this is better. There definitely needs to be a better explanation from ED on this. Even if it's just, "hey, we can't figure out how to properly code it for the AG radar EXP modes". Some transparency and a real explanation will be greatly appreciated.

I am also using the gen 1 Virpil T50 and binding this up neatly is still a problem. This is would be much nicer if the realistic slew option applied here. Some sort of response from a dev besides the correct as is tag would still be greatly appreciated. What is the reasoning behind having the realistic slew option available for the MAV and not the EXP modes of the A/G radar?

Under the user files for the new A10 there are a few missions, the only one I have tried so far is the SMERCH hunt one. Like 75% of the time it seems like the GBU54s are just not grabbing the laser and are sailing off into the distance way past the target. The launch cue seems suspect to me as well, like my launch zone is the same, within 3 miles, no matter what my altitude or speed is. It doesn't behave this way in the small missions I have newly made to test things out. It seems the only way I can get the GBUs to grab the laser is if I nose down and kinda CCIP towards the target for release. I am doing something wrong? Like I said, it only behaves this way in this mission for me, not the missions I have created or even in the other instant action quick missions and whatnot that came with the module. If anyone gets the chance to play around some in this SMERCH hunt mission and see how it behaves for you I would really appreciate it. I have also had the Maverick just not grab the laser in this mission too and completely miss.

I noticed this big time in this mission that Sedlo updated for the A10II. https://www.digitalcombatsimulator.com/en/files/3312554/ It was so bad that I couldn't use WHOT or BHOT and had to use the regular CCTV(? cant recall what it's actually called) to find the few BTRs that were the targets. update: Deleting fxo and metashaders seems to have helped the issue. I'll update again if anything changes.

I was doing this looking directly 90 degrees out to the side and the SPI point would be positioned fairly far behind where I intended it to go. I was setting it pretty close, about 10nm away, so I get that I was flying past it. But it still seemed like a pretty pronounced error compared to where I actually wanted to set the SPI. It seemed like maybe it was setting at the point where the initial button press was initiated and not when the threshold for long press was crossed to give it a more accurate position in relation to where it was intended to go. Not sure if this is how it's supposed to be or not.

Shouldn't this be labeled as a bug and not CNR? The bug being that having the historical feature active, no matter the year, results in "A-10C II is not available in the mission editor"?

I think you are getting the same thing I was getting. It is because of the historical list of units/era thing being enabled. No matter what year you set it to if that option is checked at the bottom of the editor, the little clock looking icon, the A10II will not show up in the list. Pretty sure this is a bug. Also, there is nothing for it for missions but it should have stuff under instant action and create fast mission. Just to help clear that up for you.

There was a thread about this where it was marked correct as-is even though it's very similar to the way the maverick behaves and the reason the realistic slew option was added to the game. Was the previous thread deleted or am I just missing it somewhere? What was the final verdict? Are we stuck having to make strange round about bindings by adding a separate TDC depress if we are unlucky enough to not have a real slew? Am I low class because I use a 4 way hat with depress that can't properly depress and directional press at the same time? It would be really nice to get this working like the MAV does without the realistic slew option checked. edit:L ok I found the other thread https://forums.eagle.ru/showthread.php?t=283533&highlight=radar+slew&page=3 It was moved to a different forum and still no dev response. A simple yes, no, we're looking into it response would be greatly appreciated and some communication would have prevented me having to accidentally make this new thread.

https://youtu.be/ZMmaFzbCqZE?t=1726 I was watching that and it mentions the F16 tracking and bombing moving targets with just the doppler radar, unless I misunderstand it. Is that something we will get eventually in the DCS Viper?

Take off roll and full burner acceleration out to 350kts seemed far more sluggish than before to me too. Also noticed that the toe brakes won't keep you in place when running up to 90% rpm after the most recent patch.

+1 to everyone else's sentiment. It should work like the mav. I don't think this should be marked correct as is unless the realistic tdc option is removed completely, which would suck.

Semi unrelated but is there a binding for the sweep handle? I have the cover and master reset switch bound on the throttle but I don't see anything for the handle. Shouldn't I be able to bind it to buttons or an axis? And bindings for popping it in and out? Should I make wishlist post if there isn't one already?

The fire warning lights are towards the end of the track and I tried to trigger them with the master test selector, so that might or might not give you the data you need. If needed I can try getting shot down and triggering the lights more naturally that way, let me know. Also, the collision light had to be triggered from the back seat so when the light came on I wasn't in the cockpit. So that might not give you what you need either. But I can get a friend to hit the switch from the back seat while I'm in the front if needed, again, let me know. f14ACMpanelTest.trk

It's a bit lengthy but for the most part I am cycling all 5 of the AOA indicator light states throughout the video. f14AOAindicatorTest.trk

Besides the stuff you have posted here and in the lua file to help with what's to do? What's the best way for me to help figure out new IDs? Is that something that perhaps heatblur has documentation on they would possibly give us so we don't have to stab in the dark to figure out the IDs? Forgive me if these are dumb/already answered questions I missed.