I just installed the NGX and the installation appears to have been successful but when I clicked on the icon in FSX I got a black screen with just the cursor arrow. I waited, then hit escape. I got the FSX window to quit or shut down, then when I restarted it said to reboot that FSX did not shut down properly in a red "Stop Sign". It then said "Smartassembly needed on this computer." What's wrong???? I haven't had any installation problems with any other aircraft. It's a Windows 7 - SP 1 system. Thanks. Tom

I just installed the NGX and the installation appears to have been successful but when I clicked on the icon in FSX I got a black screen with just the cursor arrow. I waited, then hit escape. I got the FSX window to quit or shut down, then when I restarted it said to reboot that FSX did not shut down properly in a red "Stop Sign". It then said "Smartassembly needed on this computer." What's wrong???? I haven't had any installation problems with any other aircraft. It's a Windows 7 - SP 1 system. Thanks. Tom

You should write support about this. Somehow the debug routine has triggered on your machine.

SmartAssembly is part of the Microsoft .NET framework/runtimes. The NGX does *not* use this in any way at all - it's pure C++ and DirectX.Whenever we've seen this at support, it's been caused by other addons that do use .NET like Active Sky, REX, Ultimate Traffic etc.Best thing to do is go to the Microsoft website and update your .NET framework installation.

I just installed the NGX and the installation appears to have been successful but when I clicked on the icon in FSX I got a black screen with just the cursor arrow. I waited, then hit escape. I got the FSX window to quit or shut down, then when I restarted it said to reboot that FSX did not shut down properly in a red "Stop Sign". It then said "Smartassembly needed on this computer." What's wrong???? I haven't had any installation problems with any other aircraft. It's a Windows 7 - SP 1 system. Thanks. Tom

Ryan is correct. Smart Assembly is a source code obfuscator used by a number of developers and it needs Netframework to function. I have had this problem on several occasions. Unfortunately reinstalling NetFramework doesn't always solve the problem. In my experience, one issue that is frequently associated with error message is a corrupt Simconnect installation. Simconnect is widely recognised as the achilles heel of FSX and it can become corrupted for a number of reasons - badly designed add-ons, CTDs etc. Unfortunately Microsoft, in its infinite wisdom, decided that Simconnect mwill never become corrupt and will never need repair so running a repair from the installation disk won't fix it (essentially all repair does is check the windows system files for Simconnect entries and if they exist it says -Yup all in order we'll skip that) i.e. it doesn't check to see whether the entries are corrupt.I would try re-installing Netframework from the Microsoft site first and if that doesn't work reinstall Ultimate Traffic 2 if you use it and any other add-ons that use smart assembly.If all else fails it could well be a Simconnect error. You can try the routine that Pete Dowson (of FSUIPC fame developed) . It was designed for Vista but should work on Win7. I have copied the routine below. Unfortunately it is not foolproof and It doesn't always work. If you have tried all the obvious options first and Petes fix routinbe doesn't work you will have to unistall FSX and all your addons. Uninstall everything and clean out the registry with a good registry cleaner such as CCleaner (freeware) and re-install from scratch. Remember to layer your installation. i.e. FSX, Meshes, scenery, environmnet, aircraft. I have had to do this twice over the past few years and with several gigabytes oif add-ons it is no easy task ! (If you are lucky and have an image back-up of your installation before corruption you may be able to reinstall that)."This guideline is originally made by Pete Dowson, the author of FSUIPC. We publish it here for reference for our users, the original version can be found here:http://forums.simflight.com/viewtopic.php?f=54&t=58095To get a SimConnect LOGCreate a file containing these lines:Code: [simConnect] level=Verbose console=No file=<path to FSX>ModulesSimConnect%01u.Log file_max_index=9where you need to replace the "<path to FSX>" by your particular path for the main FSX folder,and save this file as Simconnect.ini in your "My DocumentsFlight Simulator X files" folder.The Log will be found, after or even during your FSX session, in the FSX Modules folder. (You can of course set the path to somewhere more convenient).With the options as shown you will get a file "SimConnect1.Log" first, then on the next FSX session "SimConnect2.Log" and so on, with it cycling to 0 after 9, overwriting previous copies.If you run FSX in Windowed mode you can set "console=yes" to see a real-time display of what is going on.Re-installing SimConnectRe-installing SimConnectSometimes it seems that the FSX install does not install SimConnect properly, and re-installing it seems to fix problems with Add-Ons.Do not resort to a complete FSX re-install, as the same mis-install of SimConnect seems to re-occur. Instead try the following:1. Find and delete the following file folder (change the C:WINDOWS part to your Windows folder if it isn't in the standard place):WARNING: Microsoft says you should NOT manually delete any WinSxS folders. Well, in the sense they are system folders, no, of course they are correct. However, they also say this can make matters worse, not better, and that to repair SimConnect all you have to do is "... use the "Repair Installation" option from the FSX program setup file on your DVD: setup.exe."The problem is, and this has certainly been reported to those Microsoft folks, that the repair apparently repairs everything BUT SimConnect. It seems to check the correct presence of the folders and if they are there, skips the re-installation of SimConnect. So the only reason I suggest deleting the folder is to cause the Microsoft-recommended method to actually work!All I can say is that it has so far helped a lot more folks than it has hindered.Now, I cannot say the same for the other SimConnect versions, those for SP1 and SP2/Acceleration, which will, if installed, also have similar folders here. I make no recommendation about those at all. In order for SimConnect to load FSUIPC4 (and many other add-ons), the original "base" version of SimConnect must be correctly installed and fully operation, and that is what concerns me here.Anyway, please read the full Microsoft text here before proceeding:http://www.fsinsider.com/tips/Pages/SA0001.aspxSkip step 1 if you want to try Microsoft's method first. Here it is again (step 1 I mean):1. Find and delete the following file folder (change the C:WINDOWS part to your Windows folder if it isn't in the standard place):C:WINDOWSWinSxSx86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.60905.0_...(the part at the end is different on XP and Vista -- only the part shown here matters.2. Insert the FSX CD, and run the repair utility. This should do the trick.Incidentally, in case you need to do the same before re-installing FSX SP1, or FSX Acceleration or SP2, there will be one or two more folders to delete. But as I intimate above, I am not so sure the procedure works so well for these. Desperate problems call for desperate measures, however. It is up to you.C:WINDOWSWinSxSx86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61242.0_...C:WINDOWSWinSxSx86_Microsoft.FlightSimulator.SimConnect_67c7c14424d61b5b_10.0.61259.0_...The first (61242) is the SP1 version, and the second (61259) is the SP2/Acceleration version.When deleting these in Vista you will have to run Explorer by right-clicking and selecting "run as Administrator" (this is necessary even if the account you are logged into Vista with already has Administrator rights!) and maybe also change the folder permissions. One user has helpfully provided the following link for instructions about this:http://www.howtogeek.com/howto/windows-vista/how-to-delete-a-system-file-in-windows-vistaPlease be careful!"Good luck.and have a good Xmas.

Thanks for the help guys.After reading that complicated fix and knowing I tend to mess up things even worse when I attempt to fix them (I'm not that tech experienced ) I decided to try deleting the NGX and retry. Fortunately this time the installation seemed to go quicker since it probably already installed the added DirectX files it needed, and this time the NGX window opened in FSX requiring the installation key which I didn't get before. After that, the plane appears to have installed correctly.One thing I noticed in the original attempt was that midway through the installation, a window popped up asking for the path to some file beginning with NGX...... . It also showed the path to it, so I just clicked OK assuming it was already the correct path. On the second installation, I never got this window requesting the correct path. Could this have been part of the problem? Anyway, fortunately so far it seems to be OK, and hopefully I won't have to go through that complicated fix. As I said above, I never had this happen before with any addons including UT2, but I'm a little uneasy that something is still wrong with that simconnect you metioned or the Framework. Is there anyway to make sure my Simconnect is fine? Thanks again and Merry Christmas. Regards, Tom

If its a simconnect problem you are going to get a lot of sporadic eros from services that call Simconnect and the 'smart assembly' error will re-occur. Unfortunately there is no easy way of telling whether you have a corrupt simconnet installation or not without a lot more information. I would sugget that you have a look at this thread on AVSIM http://forum.avsim.net/topic/323016-smart-assembly-ctd/This may help you further. It also confirms that in many instances 'smart assembly' errors arise from simconnect problems.If you cant solve the problem by re-installing Net Framework or running an FSX repair and you are worried about timnkering with your system you can download a zip file to reinstall Simconnect from Flight 1 http://ultimatetraff.../SimConnect.zip. Again it doesn't always work but it worth a shot if all else fails.A lot of people running UT2 appear to have experienced 'smart assembly errors' and Flight1 proivided this link to help out. It may work for - I hope it does. If it doesn't the only way around this is to follow Mike Dowsons advice - delete the simconnect files from the windows system files and clean up the registry with CCleaner before re-installing FSX and all your add ons. Its painful, but I don't know of any other way. One of the guys at Aces who worked on Simnconnect was in the process of developing a fix routine before they were wound up primarlily because SimConnect was acknowledged to be a tad 'flaky'. Sadly with the demise of ACES before the work was finished , we all have to live with the result.When you have it working go to control panels\system & security\System\system protection and create a restore point. This will enable you to roll back your system to a working FSX if it happens again (rember to keep a seperate backup of anything else - email - documents etc) which you can the relaod when you have restored.Anyway have a good holiday and let us know how you get on. If I can think of anything else to help you I will post.