One thing I noticed is that FTX_OLC and FTX_VECTOR are under a ORBX folder, so I also tried:
airportCacheExcludeArea=ORBX\FTX_OLC
airportCacheExcludeArea=Scenery\Global
airportCacheExcludeArea=Scenery\Props
airportCacheExcludeArea=ORBX\FTX_VECTOR
As indicated in the linked post, the FTX_VECTOR area is already excluded automatically by the program even with no Couatl.ini file and, the path is not a problem, since the area will always be found as long it contains that name in its path.
Whilst testing this ini file addition, I have noticed my start time has become worse. Its now starting randomly between 1min 40sec and 2mins? Is there a way to know if the file is being used/accessed?
I'm sorry, but it the worse possible case, you would see little or no improvement, it's not possible the startup would be slower if you add some exclusion areas!
Yes, it's possible to see where the loading is slowing down, with the Windows Performance analyzer in the Task Manager. Have you configured Windows Defender to exclude the FSX folder from scanning ?
We had reports that, if you don't do that, the startup time will be increased a lot, see here:
http://www.fsdreamteam.com/forum/index.php/topic,12051.msg92019.html#msg92019And yes, it doesn't happen with GSX installed because, what is happening, is that Windows Defender has seen that some executable is reading files, so it CHECKS for each one of them to verify if THOSE files might be threats themselves, which can take a lot, if you have thousands of .BGL.
So, try to disable the whole FSX folder from scanning and, if you have sceneries installed in other folders outside FSX, add those folder to the antivirus exclusion.