As I said everything worked fine untill I installed GSX, and then I had problems. I install the addon manger and the problem goes away.
I'm sorry but, I can only repeat and confirm this error doesn't have anything to do with GSX, because it's a .NET error.
NONE of our products is written in, requires, or affect .NET in any way. The smartassembly error can only be caused by a .NET application, and UT2 IS a .NET application.
Also, it's not possible that it would be a difference between GSX and our other product. None affects .NET in any way, just the same.
GSX install EXACTLY THE SAME Addon Manager (bglmanx.dll) and Couatl.exe programs as the other sceneries. It's not even possible that it would be any difference to what these installers installs because, as you might have noticed, they ALL download those two files.
The download location is only one (ok, we have to mirrors, but they host exactly the same files) so, whether you install a scenery or GSX, their installers install exactly the SAME files. This, assuming your internet connection is working, which should be plenty obvious if it isn't, since the installer downloading part would otherwise give a warning about it.
Which means, if either the Addon Manager OR the Couatl program were the cause of the problem, it should have happened EVEN WITH THE SCENERIES, not just with GSX, because they download and install exactly the same versions of those two files.
Since you said yourself it worked with the scenery, the only possible conclusion (that the download files are the same is 100% sure), is that the problem appearing with the GSX installation was just a coincidence.
And of course, I run UT2 with GSX without any problems, it's the one AI Traffic we use to our testings.
And of course, you already search other forums and, you would surely might have noticed that the smartassembly error message is very well known to be associated with UT2, and was known even BEFORE GSX was released.
It's more likely, instead, your UT2 installation might have been affected by a problem with your MS VC++ 2005 libraries installation or by an upgrade from Microsoft, because there IS some interaction between .NET and the VC++ libraries.
Yes, all our products launch the official MS installer for those runtimes but, on top of noticing the version being installed it's the same between GSX and all the sceneries (so, again, any difference between GSX and the scenery couldn't be explained by this), but the MS installer is made in a way that, if your VC++ libraries are already an newer version, they WON'T be touched. You can notice it, because that installation step is usually very fast, it indicates the MS installer we launch simply detected there was nothing to do, because you already had those libraries and they were a newer version.