Hi I have been getting the TCAS2V7.dll CTD lately on approach using MD-11 into EGSS (Stansted) and other Airports sometimes.I have also had it using the 747.I googled the crash and many post says make sure your TCAS2V7.dll file in the route FSX folder is up to date.I assume that both the PMDG 747 and MD-11 both share the same file: TCAS2V7.dll Well I found mine in the root folder and it says TCAS2V7.dll --- 28 April 2007Is this the most up to date? If it is not can anyone please tell me where I can download the latest one.Any help much appreciated

I also have both planes and my TCAS2V7.dll is 04-09-2007A shot in the dark, maybe you need to reinstall making sure the 744 is installed before the MD11?Also make sure you have all the service packs installed if you bought the planes before SP were released

I also have both planes and my TCAS2V7.dll is 04-09-2007A shot in the dark, maybe you need to reinstall making sure the 744 is installed before the MD11?Also make sure you have all the service packs installed if you bought the planes before SP were released

Hi Dazz cheers for looking at your file to see the date and your suggestion.I checked both my installations and they are bang up to date.Can anyone tell me where I can download the latest TCAS2V7.dll from?Cheers

Submit a support ticket and I'll send you the correct dll for the MD-11.

I had this problem yesterday with the MD-11 so I uninstalled the Level-D 767 (I had recently installed their new beta gauge) and that seems to have fixed it. PMDG has this problem in their knowledgebase but they only have a solution if (1) Your .DLL is missing or (2) Your .DLL is out of date.

I have the LDS 767 installed myself and do not have any TCAS dll problems... not sure what's going on for you, but that's not common.

I got the same CTD today but with the 747 I got version 1.1.6.0 04/29/2007 so is this the latest as well ?? I'm using FSX with win7 64bit/Thanks .Evan Banalian

Hi I thought to share with you my long lasting experience with the *DLL errors and based on my count they could reach up to 5-7 different errors, you can always check them at the event viewer, the first bright idea that would come up when error occurs is that it happened because of a corrupted file or older version / miss computability, I am afraid it's much more complicated than that, assuming your computer meets the minimum requirements for FXS comfortably J ( I would like to imagine that a 64bit system, Quad Core Processor, 4GB of Ram, large capacity Hard Disk, 1MB GPU, as a reasonable configurations for a FSX computer), any or some or combined of thefollowing could be the reason for the error: Note: Based on the kind of error? did it happen from day 1 so maybe it’s a hardware related problem or miss computability issue? I won’t be much help on that, or it just happened after regular operation lasted for some time?If so I hope this might help? - (Please consider the following procedures). Computer environment: 1. Make sure there is plenty of free space on the hard disk more than 50% of total capacity. 2. Do you perform disk clean up frequently? Highly recommended (especially with internet continuous download or on line gaming). 3. Your hard drive is optimized (defragmented) at least once a week (or as recommendedby OS). 4. The startup programs and memory resident utilities / programs are minimum. 5. You have to perform a registry cleaning every about a month, using a well-respectedpaid software co. 6. FSX folder with all components is in archive mode and not read only. 7. All*.exe files should have administrative rights (to run as administrator) (this includes add ons). 8. FSX.EXE should run in computability mode with windows Vista (only) and not XP. 9. When you run FSX is it in clean mode? (meaning you turned on PC then ran the least #of applications before starting it). If errors persist please try the following: FSX environment: 1. Minimize slider bars @ FSX settings for all 1/3or less. 2. Cancel shadows; minimize water effect or any other settings option that will cause FPSto be reduced. 3. Stop Add ons such as REX or FS passenger or any similar, try using areas with no special sceneries or land class or similar. 4. Start a clean flight using a default light aircraft departing from a low traffic/detailsairport to close by one, about an hour flight, clear whether and day light configuration. 5. When done hopefully with no errors! Close flight and FSX then restart and repeat flight again or similar one (you might use FSX weather and change time). 6. Later on try a more complex flight from KJFK to KBOS and see how it works. 7. If it’s OK (about 75% probability) starting running add ons one by one and increase slider bars not to exceed 50% at any variable. It was not designed tobe 100%. If problem still happening then you can try the following: 1. Go to control panel then Add/Remove programs and look at installed program history. 2. Try to determine to your best guess when the first time this error occurs and see which programs were installed later and simply uninstall one by one but youhave to try FSX at each time, start from newer to older. 3. Again if you uninstalled programs earlier then errors started reinstall it if you can. As you can see the solutionis not an easy or straight forward and it takes time to determine but it worked for me, installing a new program / add on could start the error, uninstalling some could cause it, running high CPU use programs would trigger *.dll in somecases (such as media player), using two keyboards, some internet connections,and sometimes FSUIPC older versions. The fun part is notall errors happens at all computers even if there are similar configurations,which is a puzzle to me, whenever you make an upgrade to OS or PC errors disappear and neweremerge, some add ones (specially the scenery ones) are badly programmed makesit a problem to install and bigger problem if you don’t, with all respect tofreeware stuff, it is high unrecompensed to use( well I can’t of course judgeevery one) but most of it worked negatively on my system, so when *.dll occursthe cause could be fare away from replacing the file and when you do replace itthe problem will keep on happening.Following link give more information regarding *.dll files http://www.easydesksoftware.com/dll.htm Good Luck Alaa Riad