Mission 02, some issues

[Redglyph]

DCS 2.5.3.24436 (OB)

 

I observed the following issues.

 

1) Time discrepancies

 

See 1st screenshot (maybe it's a problem with the Viggen module and not the mission).

 

The line-up card specifies checking at 15:00 and take-off at 15:06, the kneeboard shows the engine start-up at 14:55 and take-off at 15:00. But the clock shows that it's already 15:00 when the mission begins, so there's a little confusion between the scripted kneeboard and the mission starting time?

 

2) Speed inconsistency

 

The line-up card specifies .6 M during the flight. The leader's speed is all over the place, after B1 it's about .7 M, after B2 it's well over .8 M (the altitude is also erratic), after B5 it's a very slow .5 M. A bit before B1, on the way back, he's suddenly slowing down from .6 to .4. Then a short event of afterburner and immediately after he's deploying the airbrakes.

 

There is no warning from the leader when he's about to slow down or accelerate.

 

I'm not sure which part is due to the scripting and which part is due to the AI, but it's unrealistic.

 

3) Voice

 

Wag's transformed voice is simply not understandable, and with the manoeuvring it's not possible to read the text. I suppose the idea was to mimick the VHF distortion but (1) it doesn't sound similar, (2) the two planes are next to each other, and (3) perhaps it could be more user-friendly, many people are not used to listening to distorted radio reception.

 

4) Bearings

 

It seems we were not following the waypoints (see 2nd screenshot for an example on the way back). I was wondering if there was some problems with true North and magnetic North. I'm not able to see the declination settings of the Viggen, and changing them doesn't seem to have any effect.

 

If the leader was not taking the declination into account and following magnetic N instead of true N, that could explain the problem, or almost, the angle seems a little more than 12°.

 

Also, there is little or no warning from the leader when he's about to turn.

 

5) Crash

 

At the end of the mission, DCS crashed, that's the first time I get this with the Viggen though the other missions I flew were simpler. I can post the dump if that's useful but I doubt it. Just let me know.

 

I have seen that it was possible to skip missions so it's not blocking (I know how to edit the logbook anyway).

 

# -------------- 20181203-203257 --------------

S:\games\DCS_beta\bin\edCore.dll

# C0000005 ACCESS_VIOLATION at E50DF6D7 00:00000000

00000000 00000000 0000:00000000

E50DF6D7 0029F050 0000:00000000 S:\games\DCS_beta\bin\edCore.dll ?ResetLinks@LinkHost@@QEAAXXZ()+17

EA736462 0029F090 0000:00000000 S:\games\DCS_beta\bin\edObjects.dll ??1viMovingObject@@UEAA@XZ()+42

E4AE2AD2 0029F0C0 0000:00000000 S:\games\DCS_beta\bin\WorldGeneral.dll ??1woLABase@@UEAA@XZ()+12

4000B9C4 0029F0F0 0000:00000000 S:\games\DCS_beta\bin\DCS.exe

[Bunyap]

Hiya Redglyph, thanks for the report.

 

1) The mission starts at 1500 so that would be one for Heatblur to have a look at.

 

2) This was included in the briefing: "As wingman, I’ll taxi behind the flight lead. On departure, I’ll stay in a visual trail formation 1nm behind flight lead – that’ll let me maintain formation while still being able to look at the landmarks that the flight lead points out to us."

 

The speeds average out over time but there are always fluctuations as they pass a waypoint. This was never intended to be flown in close formation for that reason.

 

3) I agree, radio distortion is wildly overdone in every flightsim, game, movie, or tv show I have ever seen. I rely on the kindness of others for audio work but I will see what I can do. At the very least I can leave the text on the screen longer.

 

4) The lead aircraft has a few extra waypoints the player does not have. He is just offset from the player's course a little in a few places.

 

5) It couldn't hurt to let the developers know if you get the time. Of course, crashes are out of my hands.

 

Thanks!

Edited December 4, 2018 by Bunyap

[Redglyph]

Thanks for the quick reply, Bunyap!

 

The 1 NM distance was completely overlooked on my part, sorry for that! Anyway, even if that was not obvious in my first post, I did enjoy the close formation exercise :D

 

I wasn't sure whether to report 1) and 5) (and potentially 4) here or in their respective bug forums, the latter is probably the best to do.

 

The offset in 4) seemed quite constant in several long legs, but if the waypoints are different I'm reassured it's not a declination mixup in the AI or mission editor (as if those were not already confusing enough IRL navigation...)

 

Any cure for 3) would be much appreciated, fingers crossed!