AstonMartinDBS

@Ian: Do we have to download your fixed campaigns manually or are they delivered automatically via DCS updates?

AFAIK every new module, tech or map will be released first for OB only - for extended testing purposes.

This is the reason for your problem. Syria is only available for the OB at the moment. Switch to OB and you can use your new map.

The Download started immediately after purchase via Steam and the map has been available as soon as the download (~30 GB) was finished. Depending on your internet connection this could take several hours. I had no problems so far. Great map btw! :thumbup:

Correct. I just placed the beacon in an existing mission and was very happy, as I saw the advanced waypoint settings for the TACAN functions. Then I started the mission once and observed the described behaviour :)

pagefile.sys ist die Windows-Auslagerungsdatei. Sie befindet sich standardmäßig auf jenem Laufwerk, auf dem auch Windows installiert ist, das ist also üblicherweise Laufwerk C: Die Größe der Auslagerungsdatei sollte von Windows automatisch verwaltet werden, was bereits aus gutem Grund standardmäßig so voreingestellt ist. Eine manuelle Begrenzung der Größe kann nämlich in einem instabilen System resultieren. Idealenfalls befindet sich die Auslagerungsdatei auf einer SSD. Einen weiteren - wenn auch geringen - Performancezuwachs gibt es, wenn sich die pagefile.sys auf einem anderen physikalischen Datenträger (SSD) als dem Systemlaufwerk liegt. Bei mir schauen die Einstellungen für die Auslagerungsdatei wie auf dem beiliegenden Screenshot aus, wobei in meinem Rechner drei SSD und eine HDD verbaut sind: C: SSD #1 SATA (System & Programme) D: SSD #2 M.2 NVMe #1 (Spiele, u. a. DCS) E: und F: HDD SATA (Dokumente, Fotos, etc. - zusätzliches, lokales Backup für NAS) P: SSD #3 SATA (exklusiv für die Auslagerungsdatei)

I just asked myself the same questions. The steam price of EUR 36,99 (~USD 44,--) is quite between the standard (USD 49,99) and the discounted price (USD 39,99) in the ED shop.

Indeed, thank you for that hint! The TACAN Beacon works, but it is not very reliable. Just tested on the PG. I have set the frequency to 97X (AFAIK this one is not used by another station on PG) and placed the Beacon next to an airbase. Around 50 NM away from the TACAN Beacon the TACAN indication was totally wrong, only the distance was shown correctly. After getting closer (within 15 NM) the position was correctly indicated on the HSI. Maybe the transmission power of the mobile TACAN Bacon is too low to cover greater ranges. Or it's still WIP, what could be the reason, that the capability for transmitting a TACAN signal hasn't been announced so far.

Yeah!!! Thx for your persistent reporting @imacken! And, of course, thx to ED for fixing the issue! :thumbup:

:thumbup: Yeah! I hope, that we don't have to wait another month to get this sensor issue fixed.

Schau mal nach, wie viel Speicherplatz für den Windows-Papierkorb reserviert sind. In älteren Windows-Versionen hat sich der standardmäßig AFAIR bis zu 10 % vom Festplattenplatz unter den Nagel gerissen. Weiß grad nicht, wie viel er sich bei Windows 10 ab Werk gönnt, da ich ihn komplett deaktiviert habe. Außerdem lagert(e) Windows div. Update-Dateien (u. a. für Microsoft Office Updates) ungefragt auch auf anderen als dem Systemlaufwerk aus. Führe mal die Datenträgerbereinigung als Administrator aus, dann lassen sich auch ältere Windows-Versionen (dazu zählen auch die durch die zwei Mal jährlich erscheinenden großen Feature-Updates aktualisieren Versionen) und Systemwiederherstellungspunkte entfernen.

Thank you. Hopefully Steam will offer Syria within the next few days and we get benefit of the discount. :music_whistling:

Have the same issue. It's very sad that we have to edit the original mission files to make them useable...

Maybe your speed at the first missile launch was too low (~230 KIAS) so the SLAM may ran out of energy and didn't reach the target area. Second missile was fired at a much higher speed (~400 KIAS) and reached its area. I used the SLAM only with WPDSG so far, but using the TGP for target assignment shouldn't be the reason for your issue. That's a bug, which is already reported.

:thumbup:

Watch the flashing ALIGN in the HUD and/or flashing RDY in your DED before you turn the switch to NAV. You may re-check the alignment procedures: NORM or STORED

Push... :music_whistling: AFAIK with the improved Ka-50 Cockpit the OPER switch and the control light for the L-140 LWS changed their positions, while the labels kept their positions.

Thx for your feedback. I thought that repair has the same effect as a reinstallation.

Well, maybe it happened to me already, but I've never recogniced it :music_whistling: Under that aspect I think that it is a correct behaviour and not a bug, too. OT: Is that Steve Buscemi? :thumbup:

How did you manage this!? :megalol:

Thx! Enjoy your vacation!

Good to know, thx for your feedback! As I prefer cold starts I was little bit confused, that the campaign started with a hot Ka-50...

Coordinates, northing and range indication, AA mode and more: Thx ED/Wags!

Thx @Wags for the preview to the upcoming OB updates for the Hornet: (TGP coordinates and northing indicator, MFD brightness and contrast) :thumbup:

As I started the campaign first, the Ka-50 was cold and dark in the first mission. After restarting the Georgian Oil War campaign, the Black Shark is already hot and ready for take off in the first mission, but he should be cold and dark. Ka50 GOW M1.trk