Florence201

CAT III limits AOA, roll rate etc, but shouldn't affect the FM

Looking at the log it looks like whilst DCS is registering DEAD for the Ammo Dump statics, it's not registering DEAD for the Tents for some reason. I would post this on discord and ask if this is normal behaviour. Meanwhile, i'll amend the mission goal and remove the need for Tents as a progression and release an updated version. Appreciate teh feedback on this.

There is an overall AMRAAM issue, not just related to Viper

If you fire AMRAAM in TWS, you can support multiple missiles to pitbull. Just use TMS Right to ensure all are target tracks then cycle between them.

Use the Separate function to see what is on the RWR. The Big Bird isn't used for Fire Control irl or in DCS.

If you're landing on sped you should have adequate runway to stop the aircraft, unless you're landing on a very short runway. The "grip and drag" FM on landing is such that asymmetric loadout will seriously affect how the aircraft responds on the runway. As for why the asymmetric, I would you suggest that you did MSL Step inadvertently, hence why you ended up with the loadout you did.

Yes they do. Use them and grayscale manual AGC all help in the short term.

This is the correct procedure, but you MUST wait for ALIGN to flash in the HUD rather than the RDY in the INS page. This seems to be an ongoing misunderstanding with respect to Viper INS alignment. In both STORED or NORM, wait for flashing ALIGN in the HUD and you will be fine.

So not sure how you’ve ended up with both weapons on 1 side of the jet, but in that instance yes you’ll need to trim. once the gear is down, you’re now into a different DCS engineered drag scenario that means different trim is required. Same for on the runway, DCS drag will affect you harshly with an asymmetric loadout. Rudder during 13deg AOA aero braking helps and then independent wheel braking until below 60kts, then NWS

Panther is spot on with her diagnosis IMO

I’ll look into the log, but from your screenshots it appears you only hit the 4 Tents with ammo dumps still alive. All 8 need to be hit to progress.

As far as I’m aware, you can only program 1 missile at a time. Set it up, shoot, set up next, shoot

everything checks out mission scoring. 4 Ammo dumps and 4 HQ tents. Then land back at base

You'll find the OB version has updated FM incorporated that has not been released into Stable version yet. Hence differences.

Not 100% accurate. Big Bird is an EW radar for area search. Clam Shell is the TA radar that looks for low level targets. FlapLid is the fire control portions of the S300. This is the engagement radar

You need to set them to Hidden on map in the ME.

Yup that's right If you want to check the mission score calculator, open M1 in the ME and click the mission goals tab on the left hand side. You will see what is needed to complete the mission

OK thanks. In testing wingman hit targets and if you strike as outlined above, then you should be good. It's a wise move to strike from height due to the ISIL MANPAD threat!

The boom needs to be to the right side of the jet as you move into the contact position for the none A-10C aircraft, not staring you straight in the face at 3 feet away. Very unrealistic

Worked fine for me in MP last night

I’ll check the mission success score, but destroying 4xAmmo dumps and 4xHQ tents should give you mission score of 100 and ability to progress. Did your wingman not strike any targets?

Ah ok thanks. I’ll check out both replies. Much appreciated. Really enjoyed The Event 1.

Just a couple of issues I’ve noticed after flying event 1. the “change frequency” messages disappeared very quickly. They are basically unreadable. also, I can hear the jester wheel activate, but I can’t see it. Consequently, I can’t navigate very easily. Thankfully, I use Vaicom so I can tune freqs. many insight would be appreciated.

Snow Plow or area track and slew are the only ways to do this currently. You can create a new SP based on pod generated coordinates

Bug is fixed in OB. Not sure in Stable though. Ensure INS is correctly aligned.