AstonMartinDBS

v0.5.0 available: adjustments to the latest DCS Open Beta update (2.7.12.23362): DOPPLER and RDR ALT are activated by default; minor pushbutton sequence optimizations;

Although I own SC, I'm happy about the availability of ACLS without SC!

Sorry for my misunderstanding. I first watched Wags' YT video and was wondering about the missing ACLS announcement in the "Hornet Mini-Updates". In my euphoria about the upcoming ACLS I didn't think about the fact, that it is (was) planned to be a feature exclusively for the SC (even tough the title of the YT video "DCS: Supercarrier and Hornet | Automatic Carrier Landing System" implies this). That's the simple reason why I overlooked the already existing announcement for the F/A-18C ACLS in the "Supercarrier Mini-Updates" and why I started this thread...

Tutorial for SC: Tutorial for the non-SC implementation: I'm looking forward to the next OB update. Thanks ED & @Wags!

Sure. You can do this via PB 08 on the HAD format page. The filter is set by default to "FR ON".

If you use the Steam edition of DCS you simply can change the language via Steam/DCS properties/language.

I watched your track and had the frame rate drop as well. My FPS rate went down to ~5 in the last minute of your replay. For HW specs see my signature. Edit #1: I flew your mission once with the AH-64D and once with the UH-1H Huey. The issue occured in both flights, so it's not AH-64D specific. As I observed, the frame rate drop started both times as soon as you get close to the SPH M109 Paladins. Edit #2: I flew once again using the Huey. This time I did an airstart near the Paladins. As I could pass the paladins without a frame rate drop the problem doesn't seem to be position or unit related. I continued my flight and after a flight time of > 6 minutes the problem appeared again. Track of this last flight: SY UH-1H FrameRateDrop.trk

I'm unable to watch the track because I don't have the UH-60L mod installed. You should remove all mods to exclude a mod as source of your issue and try again.

v0.4.0 available: [PLT]+[CPG] certain procedures re-arranged (IHADSS boresight procedure prioritized over weapons setup); [PLT]+[CPG] several pushbutton sequences optimized; [PLT]+[CPG] added some optional steps (MAP setup for instance); [CPG] added a few missing steps (WCA reset); Advice: to avoid unnecessary fuel consumption, the steps for the [CPG] should be processed pior to the engine startup procedure

3018 kB/1024 = 2,947265625 MB, so 2,95 MB is correct. I'm afraid that you've uploaded a wrong track: it shows the A-4E-C starting on CVN-72 @Caucasus). You find the last autosaved track in %USERPROFILE%\AppData\Local\Temp\DCS.openbeta\, the file is named LastMissionTrack.trk (without the initial underscore).

Thanks for this solution, @Rudel_chw!

Great catch. I assumed the identifiers were unique.

This works without problems (already tested before created this thread).

Well, thanks for clarification. Hopefully I'll find the base of my initial claim...

Had my first CTD with the AH-64D right now. I've been CPG and it happend after firing an AGM-114K Hellfire, TOF = 0, so on the eve of impact. I still saw the missile hitting the target. The CTD occured when the visual explosion effect was expected. Autosaved track: https://drive.google.com/file/d/1sHgn2DH-ee8gjQdmQSqWrM5O5qvv9ayy/view?usp=sharing DCS Log: dcs.log

According to a tutorial video (AFAIR it was a tutorial by Casmo, but I didn't find the resource right now) it shouldn't be absolutely necessary to select a point type on the TSD format by pressing T3/T4/T5/T6 for WP/HZ/CM/TG, when an identifier will be defined via KU. In that case the point type should be selected automatically, depending on the entered identifier. This worked 100 % for me so far - until I recogniced, that I cannot add a BP (battle point) to my route, because the BP was wrongly identified as a TG (target) instead of a CM (control measure). This behaviour only occurs, when the BP will be added while TSD is switched to ATK phase (BP will be incorrect identified as a TG) CA AH-64D PointTypeAssignmentIssue.trk When the exact same procedure is done during NAV phase, the automatic assignment of the point type works (BP will be identified as a CM) CA AH-64D PointTypeAssignmentCorrect.trk

This bug (reported in 10/2012 for version 1.2.1.6288) seems to be still present in the current OB (2.7.11.22211): I've setup a mission where a JTAC should mark some targets with laser. The JTAC has a valid LOS to the targets and the distance is < 5 nm. Mission: CA JTAC.miz When I set the mission time to nighttime (21.06.2016, 03:00), the JTAC responds in line 7 "no mark, 0" and won't mark the target. Track: CA JTAC NightTime LasingIssue.trk As soon as the mission time is set to daytime (21.06.2016, 09:00), the JTAC responds in line 7 correctly "marked by laser, 1688". Track: CA JTAC DayTime LasingWorks.trk

Yes, it works! And it works even with a group of four helicopters, if you place four invisible FARPS. Thanks again @toutenglisse for your analysis. As far as I observed, each invisible FARP has a single landing platform. The distance from the communication tower to the closest FARP center has to be at least ~1250 ft that an AI helicopter can land without difficulty. CA AH-64D FARP.miz

Thanks for the hints @toutenglisse! I've placed the tires based on the four platforms of a standard FARP because I expected that the invisible FARP has equal parking layout as the standard one. Does the invisible FARP provide only a single parking slot at its center (which is indicated by the FARP icon)?

I'm unable to download the track and misson.

How can I force an AI Helicopter to land on an invisible FARP? In the attached sample mission I've placed an AI Huey which should land on an invisible FARP. But instead of landing on the FARP the AI Huey is heading to the nearest Airport (= Tiblisi). CA AH-64D FARP.miz

That's correct - a solid circle indicates that RDR ALT has been activated. Sorry, but I have no idea. Did you do a cold start? If so, you can check the steps till activating RDR ALT (#36) of my Cold Start Checklist, maybe you've skipped a required step. If you manage to reproduce your problem you should provide a trackfile.

Exactly. You should select this category, if you wanna place helicopters in the ME:

First of all you should use the forum search to check out, if your problem has been already discussed here. This thread may be related to your problem - the problem was caused by the user, so it was not a bug. Then you should choose the correct forum for your problem. Due it seems to be a F-14-specific behaviour, the DCS: F-14A & B Bugs and Problems forum could be the first choice for your issue. Last but not least read this thread to learn, how you should report a (suspected) bug of the F-14 and this thread which is valid for other DCS bugs. Every report needs at least a track file of the described behaviour. The track file helps others to exactly reproduce your behaviour. It also shows, if it was an user error rather than a bug.

v0.3.9 available: [PLT] POINT management and SHOW settings moved further back (after alignment completion and prior to engine start); [CPG] radio SQL switches optional (the radios have been squelched already by the PLT at this point, the current switch behaviour is wrong implemented, the switches should be spring loaded); minor optical improvements