PE_Tigar

@EtherealN - flight in this case might mean a downward part of the ballistic curve. There's nothing preventing a 4 engine airplane from flying (gliding) even with all engines out :). In no way should it be able to climb on one engine, at 96kts though...

LZSL doesn't have ILS for RWY 18 that this guy is using, nor is there any IFR procedure for that RWY. Therefore - eyeballin' it all the way to the ground. Also - landing speed guidance is too low, by about 50 km/h (known bug) - so fly approach on 280 km/h, not 230 - AoA will be lower, landing smoother.

@159th_Viper: how about this one: In "Over the Hump", after finishing the SEAD escort mission successfully debriefing screen crashes when 96% loaded. Ergo, the campaign cannot proceed.

Flew a couple of landings with F-15C last night and landing gear collapsed on one - I was doing maybe 160 kts on touchdown which should be pretty much by the book. The other landing was much slower, so a tailstrike ensued... of course - but landing gear was fine. I'll have to do some more testing to see what's changed and what not.

MiG-29S/MiG-29S Campaign, 1.2.3: Resolved: +flight director in MiG-29S works now Unresolved from 1.2.2: -annunciator panel, RWR and Bitchin' Betty still in English (even after Russian is chosen as a cockpit language in Options) -MiG-29S campaign still doesn't work (can't proceed after SEAD Escort mission, briefing screen crashes after loading 96%) -landing approach speed still too low (230 km/h, instead of 280 km/h)

I think that the airbases would be much more interesting if we had the following: - emergency traffic prioritization - ability to declare an emergency, and the ATC to clear the traffic to let the emergency traffic land first - emergency equipment at the airport - fire trucks in particular, as well as landing barriers, foam and wire traps

I presume you're following the speed guidance on HUD - and that's been reported as a bug already. That's why your AoA is too high. 260 is a good speed on final approach, as Kuky said.

One word - beta.

If you're using Chrome try another browser, DCS website has never worked properly with Chrome.

Your loss. Throwing the baby out with the water and all that...

I have managed to pass it once (somehow) and the campaign crashed (GUI crashed after the mission). I don't have a clue what I did :).

You have to change Shkval's gate size, and than it works without a hitch. For combat helicopters try and A-10/Su-25 type targets try 15-18 meters, larger airplanes - look up their wingspan and use that. I've shot down a few Mi-24s and AH-64s in Su-25T campaign with Vikhrs, they're especially vulnerable when hovering. When you spot a helicopter, try and move 10km away from it, turn back at the area you spotted him, and aim Shkval there and stabilize. When you spot him, move the Shkval gate (which you've previously changed to the target's size) over him, lock and let him have it... If you don't spot him before you're 5km away, turn 180, rinse and repeat.

Same issues exist with F-15C, MiG-29S and Su-25T campaign (at some point or another), check the main bug thread. Apparently, should be fixed in the latest internal build.

Here's to hoping we get the latest build soon then :). Thanks for the info!

MiG-29S campaign: -tried two missions so far, both crash the editor when I try to open them. -second mission has the same issue as reported with the first F-15C campaign mission and ATO C.P7.4 mission from Su-25T campaign. I assume it has something to do with the campaign design, as it always happens when I win the mission and should proceed with the campaign.

Affirmative. I'll try other imported campaigns and report findings.

Does this also concern the FC3 campaign missions? Because for the F-15C campaign at least me and another guy can't proceed further than the first mission (crashes GUI on exit, no record of the mission). More info here: http://forums.eagle.ru/showthread.php?t=97971 It also hapenned with one other mission in Su-25T campaign, common characteristics are: - mission finished, I land, hit quit - GUI starts loading, reaches 96% and crashes to desktop - no crash log is generated I assume, though I'm not sure, that this is connected with porting the campaigns over from FC2, so might affect all the newly imported campaigns at some point - I couldn't test them all as I am in general very short on time. BTW, I "fixed" the Su-25T mission by removing the tasking from my flight and re-tasking with a different task (which did approximately the same as the original).

Tried the first mission from F-15C campaign - same thing. Tried re-assigning tasks and commands to all aircraft/vehicles - same. The way I fixed the Su-25T mission I started this whole thing with (in the end) was that I assigned my AI wingman a different task. BTW, never had problems with the instant action F-15C mission.

WTG gentlemen - looks awesome!

So far, seems that clients get no lock or launch warning from any launch platform (SAM, airborne, ship). Seems to me it's not a particular, but a general problem.

Solved my issue by opening the mission in the editor and saving it again. It still exhibits one strange quirk (I'm supposed to take off from the field, but start 500 meters above the runway).

That's easy - it's defined separately for every airfield, and of course used only on visual approaches. Translated to FC3 it means you choose whatever you're comfortable with. For fast jets 2000ft AGL is about right for me.

Same goes for F-15C RWR, we've had a fairly intense session against multiple AI MiGs and Sukhois yesterday and I've had dozens of missiles launched against me, not once did I even get a locked signal from RWR, let alone a missile launch warning. Same for other clients, but host did get missile launch warnings. I can justify that for ET/T but approximately a half of the missiles were ER. RWR did display AMRAAM "mad dogs", though. Also a quick question - is AMRAAM capable of some rudimentary IFF in "mad dog" mode? Also, can anyone provide some details on how HOJ is actually not functioning? I know I can't get a hit in HOJ for the life of me, but I thought it was just me being incompetent :D.

- What were you doing just before - or trying to do when the problem happened? Exiting the mission ATO C.P7.4 in Su-25T campaign. - What happened? Land, finished the mission, close the DCSW, GUI starts loading, hits 96% and crashes to desktop - tried it about 5 times, always the same. I have been flying this campaign for some time now, never had this happen in any of the missions (and haven't had a CTD with DCSW in single player since .7286 otherwise). And there's no crash log generated.

Buks don't shoot down ARMs, but Tunguskas do, IIRC there are some Tunguskas at Buk sites in that mission.