Habu_69

The TDC drifts down, as the aircraft flies, in RWS mode with no L&S track. Appears to be set onto whatever geographical coordinate the TDC is slewed to. Normal behavior? I expected the TDC to snowplow in such situations.

You can post a program issue on Github with the author. He is active and responsive. https://github.com/Santi871/DCSWaypointEditor/issues

Whenever power is disconnected from the Cougar it loses calibration. Does anyone know how to retrieve a saved calibration file? The CCP app has no calibration file search function and the calibration file window is always blank.

Well, my post above referred only to the function of entering WP and target coordinates in the cockpit. I have never tested the map capture functions.

I employ JSOWs quite frequently and find them very accurate in both PP and TOO modes.

Yes, this describes RL conditions, but does DCS model the effects of EMCON/radar silent? Are enemy aircraft and IADS less likely to detect and engage? Are detection/engagement ranges affected?

I use this app frequently with patch .55960 and it functions flawlessly. Make sure to use the most recent version.

Well, this is a 4.5 year old thread. Find current Moose info at the Moose Discord channel.

Well, TAz, your work-around failed. textures/terraincommon_Taz/voronka_ground.dds also fails IC on Hoggit servers. Booted me 20 min. into mission.

textures/terraincommon/voronka_ground.dds fails IC on Hoggit servers. Booted me 15 min. into mission.

Probably unrealistic, but hey, when you NEED gas..... I have found that engaging the F/A-18C autopilot is a great AAR assist. AP dampens the stick inputs.

IF you are trying to fly realistically, time in the groove should not exceed about 20 sec.

Voice Attack.

AAA 36 1 is simply the name of the "template" group in the ME. Recommend you check out the Moose User Guide from Moose Info channel of the Moose Discord as a very handy primer for scripting in general, and Moose in particular.

About as simple as it gets using a table of templates. Can also use a Moose set instead of table. AAA1 = SPAWN:New( "AAA 36 1" ) AAA2 = SPAWN:New( "AAA 36 2" ) AAA3 = SPAWN:New( "AAA 36 3" ) AAA4 = SPAWN:New( "AAA 36 4" ) Rand36 = math.random( 1, 4 ) TBL36 = { AAA1, AAA2, AAA3, AAA4 } AAA_1 = table.remove( TBL36, Rand36 ) AAA_1:Spawn()

If you check the Snapviews.lua F18 parameters for the Num5 view and the Default view, you will find they are different. A bit confusing because Num5 does act as the normal "default" view; however, there are functions that snap to the official Default view as defined in the Snapviews.lua.

True enough. That saved view, tho, becomes the "Initial" Num5 view, which is different from the "Default" view, which, AFAIK, must be tweaked by editing Snapviews, as I described earlier. Most counter-intuitive.

I tested ATC for CVN approach just prior to current patch. No go.

What is TM charging for the PCB?

Enable Snapview saving in Options. Save snapviews by pressing RAlt + Num0 while in cockpit. Now find Snapviews.lua in Saved Games\DCS World\Config\View.

OK, I think I found it. Parameter to modify is in snapviews.lua. For F/A-18C it is, oddly enough, [13] = {--default view about line 1708. I moved eyepoint back from HUD by increasing the viewAngle value.

To get sound files into a mission open the mission in ME. Make a trigger at, say, time More 5 with action to play the sound file to an obscure country not used in the mission. Save the mission. This loads the sound file into the mission making it available to play by a script action.

Ahhh. So, the grayscale is merely a visual reference for adjustments of brightness and contrast.

Does FLIR Grayscale adjustment work in DCS? How?

+1. Researched this a couple of months ago and found no fix. Tried all the default FOV settings I could find.