Antiguedad

+1. Just finished the campaign, it's really good, but the 330 KHz NDB not directing to Naqoura completely breaks the inmersion. I used openkneeboard with moving map to navigation, but please, yes, could you change the Naquora frequency to solve the issue? Thanks, I enjoyed the campaign a lot, specially the last missions.

Same error here, at least I'm not the only one.

In mission 11 after getting the message "All flights RTB", returning to base and landing the mission only shows 50%. Is there any trigger I'm missing? I land in runway 24R, maybe I have to land in other runway? EDIT: I'll try 06R, that's where the steerpoint is. EDIT2: Solved, but it's a little confusing because there are 2 RTB messages: "All assets RTB", and "Uzi, all clear, RTB".

I've been creating various OA1, OA2, PUP and VIP and I think currently it modelled like this: A. If you put an elevation of 0, the created point has the same altitude as the steerpoint. For example, if steerpoint has an MSL elevation of 12000 ft, the created points have the same elevation, 12000 ft MSL. So, uses Delta=0 value. B. If you put an elevation different than 0, the created points have the absolute value AGL of the elevation. For example, if you put an elevation of 52 ft, the points are created at 52 ft AGL. If you put -1, the points are created at -1. So, uses absolute AGL elevation value. This maybe is a bug: Input Elevation = 0 -> uses a delta value of 0 -> OA1, OA2, VIP, PUP are at the same level than steerpoint. Input Elevation not 0 -> uses AGL elevation. Please, could you check if this is the expected behaviour? Edit. You can check effective point elevations with TGP and OSB10.

I'll keep it, I love the plane.

In my case I think It's related to the launcher enabled and the top right "radar icon" spinning for a very long time, the language icon one. When I wait to the top right icon stop spinning before launching the game, the game starts ok.

Maybe the problem is not with our plane (4), but with the other planes (1,2 and 3) turning their mids knob on before leaving the hangar. Is there a way to delay 1, 2 and 3 turning their datalink on until they leave the hangar and, therefore they have valid GPS signal? Or maybe just briefly cycle 1, 2 and 3 MIDS knob OFF and ON again when they get airborne. Just to try a suggestion if this solves the issue, cause this campaign feels very good.. EDIT. It's definitely something on 1, 2 and 3 datalinks. In my case after an hour or so suddenly 1 and 2 datalink started working and became blue with numbers. EDIT2. Mission 7, datalink for weasel 51 doesn't work. Weasel 52 datalink (player) works, because I can see Weasel 51 in green as a friendly but not as a donor, and sometimes it turns white. Mission 7 and another previous I don't remember TACAN 115X gives no signal. Enjoining this campaign A LOT.

This problem still persists in 2.3 campaign. In the "normal" campaign it works fine. Also skiping mission in 2.3 campaign leads to a practice mission, the "normal" campaign works fine. Sorry for the question but, are you sure the updates and corrections you send to ED are being applied to the 2.3 version and not to the "normal" one?

Sorry if you misunderstood my message, English is not my primary language. If you read it again, you can realize that I didn't talk neither about outside temperature nor about engine not being able to start in cold conditions, nor needing any special equipment. I'm not talking about engine wont starting in cold conditions, and I'm not talking about outside temperature but engine temperature stabilizing. I just try to help responding to the original post author who said that, with the throttle in idle and engine started the engine does a start cycle. And sorry, but I keep stating that this is not a bug, and this is the way the A-10C engines really work: If Throttle idle and core RPM below 56% then the Air Turbine Starter Valve opens, the Engine start cycle light turns on, ECS valve is closed, bleed air valves opens and ignition is provided. IMO, this is a feature, not a bug.

I think this maybe is not a bug. The real plane manual describes this related to temperature and 56% core RPM. Edit. REDACTED.

Check your antivirus, maybe some file has been blocked. Add DCS folders to your exclusion list and try doing a repair.

Thanks a lot for your help.

Just the same here, wingman doesn't join. Edit: there is already a bug report about this, and the creator replied is solved, maybe in the next patch.

Yes, but the RWR mod must be in the main DCS folder. The other mods can be placed in Saved Games folder.

@CHPL ok, it worked, thanks, I ran out of fuel just before landing but mission works ok.