Zyll

Yep that fixed it! the cleanup/repair identified these files, one/all of them must have been the culprit:
Scripts/Speech/common.lua
Scripts/Speech/speech.lua
Scripts/UI/RadioCommandDialogPanel/RadioCommandDialogsPanel.lua
Scripts/UI/RadioCommandDialogPanel/TabSheetBar.lua
Scripts/UI/gameMessages.lua

I think its Vaicom / VoiceAttack which modified these files. @Livers do you run Vaicom Pro perchance?

Ahh yes I should have been smart enough to make this correlation, you guys are correct. Testing with a completely empty mission, you do indeed get accurate time acceleration up to and possibly even exceeding 20x (ie. 3 seconds for a minute to pass). Hopefully if/when ED revamps the mission replay functionality, it will improve upon the time acceleration with a more reasonable number of units in it. 

turns out I could have just made my life a whole lot easier with this simple line in a mission script (assuming sanitization is turned off):
 
lfs.writedir() I can determine the server with this since the path will be specific to the folder under Saved Games that it was installed.
alternatively this worked just fine too:
 
dofile(lfs.writedir() .. "Config\\serverSettings.lua") grab any server setting from this file

you could use a conditional trigger and use a flag counter that increments to 10 or a 'time since flag' condition to exits the loop. That's the easiest way I can see doing it in the ME without a lick of lua scripting

You can reference the DCS.lua that comes with Moose:
https://github.com/FlightControl-Master/MOOSE/blob/master/Moose Development/Moose/DCS.lua

Most likely (this has been my experience anyways) your sight is currently FCR because you as the pilot switched to it and so as Floyd states, you need to take the additional step before guns will follow your head.

Zyll @ TAW

Are you high (altitude) or hot? The Apache does have challenges starting under extreme conditions.

If so, I have a video on this:


Zyll @ TAW

You can reference the enums, so in this case in place of doing a comparison to 1, use coalition.side.RED. For more enums you can use, reference hoggitworld:
https://wiki.hoggitworld.com/index.php?title=Special%3ASearch&search=enum&go=Go

a1 will evaluate to nil if it doesn't exist, so you can simply wrap the lines that follow in an if clause:

if a1 != nil then
...
end



Zyll @ TAW

As I recall, that folder didn't even exist until you installed that cockpit texture mod (or possibly a different one). The default cockpit textures would have been in a zip file under program files/Eagle Dynamics folder.
C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Textures\AH-64D-CPT-TEXTURES.zip

Did you try deleting the Cockpit_AH_64D folder and clearing fxo and metashaders2 folders?

Zyll @ TAW

Set your acquisition source from the TSD page to the TADS and you will see a broken cross where the CP-G had his sensors pointed.

The charts on the TSD also appear once the alignment is complete, 4:20 to be exact.

Are your textures (not terrain textures, the other one) set to high in settings?