Ashilta

Thanks for the reply, L0op8ack. Am I to understand then, that there is no TTI for the actual bomb in the JF-17? Thanks, Ashilta

Hi folks, When performing LGB drops in the instant action mission for LGBs, I've noticed that the TTI on the targeting pod is something like 20 seconds out. Am I misconfiguring something or is this somehow defective? Happy to provide a track if required.

Hi folks, Very new JF-17 pilot here but loving it so far - Deka have done solid work and should be proud of the finesse they've brought to DCS with an 'EA' module. I've started doing some simple LGB runs in the jet and found that I have something of a problem with the targeting pod. Essentially, if I'm pointing 'at' the target, things are fine. If I turn off of the target line, and try to slew, down is no longer down - by trying to 'slew down' the TGP actually slews in some other direction, typically right. If I come out of point track mode then it seems to be better temporarily, but it's not guaranteed. Am I doing something wrong? Would a track help? Edit: Gah, sorry. Wrong forum and I can't move it!

Welcome guys! What a grand opening - really looking forward to seeing the Typhoon develop over the coming months/years.

In light of this being marked unreproducable: Here's a pair of screenshots showing the switch in the right place and the HUD readout as 0 whilst airborne: https://imgur.com/a/Hvf5Ksf Here's another track: https://1drv.ms/u/s!AlT38BKo2JnThNRQRHtWc6bcSO6VCg?e=KHmfpD This was created using the 'Takeoff' instant action mission.

Tried this just now and no joy, felpan, but thanks for trying!

I'll learn with you my love <3

I've taken the time to run through a video I recorded last night of a mission from within my wing. From it, I've taken some screenshots of the datalink behaviour I've identified. At no point in this mission did I, or anyone in the wing, change their Link16 settings. Whilst this isn't a track as such (and I can't produce the track of this mission because it relies on custom content), there's clearly an issue here that warrants further investigation. Images: https://imgur.com/a/7ML8gup Vidya: https://youtu.be/DwsuHSmo1r4

In 2.5.5, we had some intermittent datalink issues with the Viper but it seemed to work most of the time. Since the release of 2.5.6, the datalink seems to have degraded to such a state that it now doesn't work more often than it works. There are four categories of problem: Aircraft do not appear at all Aircraft appear but are incorrectly classed as hostile/friendly My own aircraft is reported as a separate contact, occasionally declared hostile The 'group' behaviour is defective, showing aircraft in other groups as in my group, or not showing my group as in my group I have a track confirming the first issue here: https://1drv.ms/u/s!AlT38BKo2JnThNRPPJgso6T4Ic7SFw?e=PzO8d6 - this track shows the 'aircraft do not appear at all' issue over any of the others. The server in question (the aerobatics server) was absolutely riddled with F-18s, many of which were airborne, but only three datalink returns were shown.

If I change the switch on the right console to display ground speed in the HUD, the value displayed is always 0. TAS and CAS seem to work fine and there's a seemingly reliably difference between the two values, but the groundspeed always reads 0, whether on the ground or in the air. Track here: https://1drv.ms/u/s!AlT38BKo2JnThNRPPJgso6T4Ic7SFw?e=PzO8d6

Since the release of 2.5.6, once the RWR is turned on, it cannot be turned off; the switch can be moved into the 'off' position but the display remains on. Track here: https://1drv.ms/u/s!AlT38BKo2JnThNRPPJgso6T4Ic7SFw?e=PzO8d6

Since the release of 2.5.6, the THREAT WARNING AUX power button now seems to function like a switch. I am convinced that in 2.5.5, I could press and hold the power button to turn the system off; now, a right click turns it off. Track here: https://1drv.ms/u/s!AlT38BKo2JnThNRPPJgso6T4Ic7SFw?e=PzO8d6

Right, I've done some further work on this. From what I've found, if you do ANYTHING on the ICP related to the DED then the stored heading align fails. The only way I can seem to make it work is by simply not touching anything whilst the alignment takes place. Here's a track showing the process if you touch nothing: https://1drv.ms/u/s!AlT38BKo2JnThNQ35dZHZ2EGAUl0GA?e=D224A1 Here's a track showing the process if I simply change menus: https://1drv.ms/u/s!AlT38BKo2JnThNQ4eMBj90QkisiJFw?e=B5ZWyY

Trying to fly in a training misisons this evening. Datalink is totally sour for all aircraft on RED.

If I follow the instructions in Wag's YT video, start the jet, set align to 'STOR HDG' and monitor the progress, I reach 1.5/10 and RDY does not start flashing. I have tried both 'entering' the LAT/LON and not and both have the same result. Subsequently, NORM align is the only mode available. Edit: Adding a note to say that I'm not 'changing' the jet during this process. I haven't moved any controls, I haven't added munitions or refuelled. Edit two: Track file here: https://1drv.ms/u/s!AlT38BKo2JnThNQpUb57w4ZegfzhXw?e=AcBX5J Edit three: The issue occurs in MP only. SP is fine...

Whilst flying this evening in an F16 allocated to RED, I noticed that my datalink was sour. Wondering whether or not my LINK16 settings were in conflict with another jet, I changed the numeric value in my ID from 41 to 49. DCS stopped responding. Can't produce a track because the track only gets saved with a clean exit from flight.

I feel that this is a pretty damaging bug, if I'm honest. As a wing that flies missions regularly containing both A-G and A-A flights, the fact that we can't have separate presets for each aircraft is very limiting indeed. Whilst I understand that legacy code exists, I'd like to think that newly created airframes with their own mechanism for storing presets (like in the mission file in the miz) wouldn't depend on the legacy methods for storing presets. Can this be addressed, please?

I confirm I can reproduce this as well. Every damned time I fly. It's actually quite limiting and, I would imagine, not tricky to fix...

Morning all, I have a couple of queries regarding the INS in the Mirage and I'm hoping you can help... I'm OK with configuring the INS - I can set my initial position, configure some waypoints, take off and navigate, I'm OK with that. Most of the time I fly with Auto-Navigation on, and this leads to question one: I like to fly with the INS mode set to Bearing/Distance, however when I cross a waypoint, only DEST increments - PREP stays in whatever waypoint I was configuring before. Is there a way I can synchronise the increment of PREP and DEST? Next, I managed to completely screw up the INS mid flight. I tried to perform an INS update, but when I looked at the Lat/Long difference (^L/^G), it read all 0's. I got over my waypoint again, hit the REC button and "N.DEG" appeared in the INS status window - my INS required alignment. There are actually two questions here: firstly, what did I do wrong to cause the INS to 'unalign' when trying to perform a position update, and secondly, is there a way I can conduct an in-flight alignment of the INS, or perhaps another position update to ditch the N.DEG notification? Cheers, Ash

Hello, Is there any chance that the correct presets for ATC, GCI West and GCI East can be added to the VHF radio in the Mirage for red? TIA, Ashilta

Thanks all, I'm glad it's not me missing something obvious!

Morning, I've noticed that if my loadout features a centre line tank, then provided you have weigh ton wheels, the FBW limiter switch is expected to be in the UP/A2A position. As soon as you take off, you get a config warning and are required to set the switch to the DOWN/A2G... Am I missing something?

What ****ing planet are you on son?

Our SAM network was disabled by a true gamesman. Think yourself lucky.

I think that the loss of target lock is because of the missing stabilisation, which Zeus has said he's fixed in the next update - targets shouldn't be lost quite so easily from Friday!