Rolds

Ah yes forgot to mention this is on the 2.5.1 and I do think its a DCS not a museum relic issue.

P51D relic 2 starts engine but does follow relic 1 as expected, relic 2 remains at spawn position. Edit - there is a failsafe in this mission, the P51D respawns in the air halfway through and from that point on behaves I believe as normal. One other odd thing is that Nalchik does not acknowledge my request to taxi, they do in all other missions. Also I think this bug also shows up two missions prior where you attack an airfield with a big group. An F16 and an F18 on either side of you start engines but do not move.

This all looks good, and I'm looking forward to flying the eagle. Have you had a chance to work on multi crew for it yet?

I would say that's a pretty good response time, thanks!

Are you sure? I've tried this mission 4 times and nothing happens after "take them out!". Its possible I can't find some of the infantry if you need to kill the whole group but I'm fairly certain I get them all. After running out of ammo on my first attempt I started bringing rockets, is it possible that's doing anything to mess up the triggers? Being played on version 2.5.1

Possibly a bugged trigger, the 3 F16's which are supposed to join you don't, but much later I got a seemingly random radio message from them telling me to lead the way to Sukhumi. I tried flying 6,500' at 300 knots to get them to form up with me around a point south of Gudata, and then tried a number of other air speeds and altitudes but couldn't get the trigger to fire. I could still beat the mission just without the part where the F16's follow you to Sukhumi.

Can't seem to contact ATC, appears to be a new problem.

I have 32 gb ram, i7 7700, gtx 1070, ssd install, and was not having any problems with 2.5 loading times. 2.5.1 has resulted in a performance hit and I'd like to go back. Thanks! Rolds

This isn't accurate in my experience. To test I created a mission (Nevada map this time however this is no different from Caucuses in my experience), put in an A10C set to "player", created a new trigger to fire on "time is more - 15 seconds" with the action set failure L-Engine, 100% probability within 1 mm. In flight I was monitoring the mission log periodically and I saw the failure event occur on the log within the first 30 seconds of flight, however engine RPM never decreased and there were no other noticeable signs of failure.

The failure will show up in the mission log but no actual effects (in the case of my tests, hydraulic failures or engine failures) actually occur to the plane.

Came here to report this, shame it doesn't work.

Just happened for me, version 2.5 in mission 2 of the museum relic campaign.

Just tried, test 1 release height 300m QFE, release speed M.73, first impact dead on target, which was destroyed, then the line proceeded from there. Test 2 release height 400m QFE, release speed M.70, all long.

https://www.youtube.com/watch?v=VQ9_1pWuU1g Made a quick video to show you, thanks for looking into this Zabuza! Also, I just posted this, it'll be available in 1080p shortly based on past experience.

I am finding that while I am piloting an aircraft I can click add target to issue orders through the F10 map with certain artillery units, the Akatsia, MLRS, and CG 60 Normandy, but not others, such as 2B11 mortar and M109 Paladin. All units have been placed on the same mission, see attached, does anyone know what might be inhibiting some from taking target orders? Does this happen when others open it?

English user here: - Spitfire produces no thrust, the engine makes noise and manifold and rpm gauges increase as expected in response to throttle but there is no sign of thrust in cold start, hot start, or air start - FW190 - gear starts in a "retract" position, can be worked around by setting the button before engaging battery, but then the engine will not start. air start results in windmilling propeller with no thrust - P51D, BF109K4 - no issues noted I also have crash to desktop on A10C battery switch Soft lock occurs on attempt to spawn Mig 21, Mi8, F5E The following spawn and appear to have no issues: -M2000C -Mig15 -F86 -Av8B -UH1H -Gazelle -Hawk -L39 -Ka50 No mods on my install, I7 7700, Gtx1070, 32gb ram, SSD install

Does anyone know if this has been enabled? EDIT: It does and it is glorious! The little gazelle can all in tomahawk strikes! Instructions are in a "new features" notepad in the same folder as the flight manual.

The radio volume knob isn't doing anything, also doesn't appear to be animated correctly, it turns in the "up" direction, but not down and for all I know that may be related.

Yeah I am following that procedure and hitting the target but not bracketing the waypoint as expected, there are two things that seem apparent from my attempts: 1. The guidance in nav mode has you fly 400m above target elevation, this causes all bombs to miss long. When I ignore the guidance and fly 200m or lower, I get hits but... 2. The first impact is fairly close to the waypoint, so to bracket an area target I need to remember that and move the mark point accordingly. Curious if this jives with the experience of others.

Follow up, is the waypoint supposed to be the middle of the grouping (this is what I was thinking) or the FIRST impact point?

yes

Could someone please try these and let me know if I'm crazy? I've tried against a number of targets and at various release heights and speeds. Thanks!

Update: Figured it out, I sheepishly withdraw my question about the ARUFOSH's, the white lights are still too dim but think that's just a 2.5 re balance issue.

Thanks this fixes the M818 but not the ships, any idea what texture file I might be missing there?

ARUFOSH ultraviolet lights don't appear to be working for me from a cold start, I've tried a number of variations in startup procedure but have not been able to activate them. In an airstart Mig15 they work just fine. KLS-39 white cockpit lights appear to work but too faintly to be useful, air start or cold start is the same. The KLS-39s I think just need to be rebalanced to DCS 2.5 lighting, but the ARUFOSH might be a bug, can someone else please check and maybe let me know if I'm doing something wrong? I do see the O p e r a t i o n p e c u l i a r i t y of A R U F O S h l a m p s section in the manual, however the lights aren't lighting in the first place, and I have tried several methods of moving the RUFO rheostats and simply haven't gotten any UV lighting in the cockpit. Thanks!