[Solved] Error on exiting game

[Quitch]

I see the following error every time I quit the game (Impulse, 1.004)



I am running Windows Vista Ultimate 64-bit SP2

Error file attached.

[T-Bone Biggins]

This might be an incompatibility with 64-bit OS's from what it looks like, but X4000 could tell you more if you find copy and send that UnhandledErrors.txt file here. That message has the directory, and it could help troubleshoot the problem.

[x4000]

I see the following error every time I quit the game (Impulse, 1.004)



I am running Windows Vista Ultimate 64-bit SP2

Error file attached.

Hi Quitch,

Thanks for stopping by these forums.  Looks like this is an internal error in SlimDX, the graphics library we use.  I haven't heard any other reports of this, on Vista 64bit or otherwise, although I don't know if anyone else has tested it on the latest service pack yet (that just came out last Tuesday).  It's some sort of security exception, so most likely it's something that Microsoft changed in that service pack.

I've opened an issue with the SlimDX team, and we'll see what they say, but for now don't worry about it too much -- I imagine it's annoying, but it's not adversely affecting anything except showing the popup and logging the file.  The SlimDX folks are usually pretty quick about resolving stuff, so we'll see what they say.

If you're interested in following the progress of that issue, here's a link to their issue tracker:  http://code.google.com/p/slimdx/issues/detail?id=494

[x4000]

This might be an incompatibility with 64-bit OS's from what it looks like, but X4000 could tell you more if you find copy and send that UnhandledErrors.txt file here. That message has the directory, and it could help troubleshoot the problem.

Thanks for filling in while I was afk.   But, just as an FYI, the game is fully compatible with 64bit version of both OSes.  One of our alpha testers was playing on Vista 64 the entire time (and we did have some issues with music playback and permissions during alpha, but those were all resolved by beta).  Looks like it's a service pack issue.

[x4000]

Hi Quitch,

Here's the preliminary response from the SlimDX team.  Looks like it might be another issue altogether.  If this does or doesn't fix it, can you let me know so that I can tell them and they can either close the issue or keep looking?  Thanks!


This appears to be some kind of machine configuration corruption. Take a look at:
http://forums.asp.net/t/1180694.aspx
http://weblogs.asp.net/bhouse/archive/2005/11/10/430270.aspx
http://msdn.microsoft.com/en-us/library/ms732012.aspx

Specifically, simply running this command:
%systemroot%\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation\ServiceModelReg.exe /i
Should do the trick. I hope.

[Quitch]

I don't have such a path, neither Framework nor Framework64 have a 3.0 path, they have 2.0.50727 and 3.5 but no 3.0. I ran a search in the Microsoft.Net folder for ServiceModelReg.exe but no such file exists.

I have Microsoft.NET 3.5 SP1 installed. I ran a repair which completed successfully but still no 3.0 folder and no file as named below.

EDIT: Downloaded the 3.5 package again and ran that, but it only offered me repair and upon running that and trying AI War I had the same issue.

Also uninstalled SlimDX, downloaded package from their site and reinstalled. Same issue.

[x4000]

Thanks for the update, Quitch, and taking the time to try all that!  I've passed your note along to the SlimDX folks, and we'll see what they say.

[x4000]

Okay, more info from the SlimDX folks.  Looks like the error is even below the level of their code; here's their suggestions:

-----------------

The fact that the user does not have the 3.0 runtime components is interesting.
Perhaps he could install the 3.0 redist? It's here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-
25634C3BF043&displaylang=en

I can guard the Debug.Write() calls with an #ifdef, which we should probably do in
the long run anyway, even though this does not appear to be a SlimDX bug
specifically. However I'd like to make sure we figure out if we can resolve it first.

----------------

Sure. He said he reinstalled the 3.5 redist, but still didn't have the 3.0
directory. I seem to recall having this issue at work as well... not this specific
issue, but one where the 3.0 redist needed to be reinstalled even though we had the
3.5 stuff on the machine and even though the 3.5 installer is supposed to include
the 2.0 and 3.0 framework components.

If he lacks that directory, he lacks some 3.0 runtime components, including the
stuff that would (ostensibly) let him fix the configuration issue. By getting him to
install the 3.0 redist, we can see if that creates the directory with the tool he
needs to run, and if running that tool fixes him.

As far as I can tell, this is not a SlimDX issue. SlimDX only requires 2.0, and the
actual failure here is deep into the runtime code, well beyond the API boundary
between SlimDX and the BCL. Although that call to Debug.Write() should not be in the
release bits of SlimDX, that itself turns out be the result of a compiler bug (the
C++/CLI compiler ignores ConditionalAttribute) but should nevertheless be perfectly
safe according the SDK documentation.

What I want to ultimately do is remove that Write() call from the release builds
manually. However, while this will appear to fix this bug, I am convinced it will
actually just be masking whatever the *real* problem is.

[Quitch]

It appears the entire thing was my fault.

.NET 3.0 ships with Vista so you can't install it as part of the packages but rather do it via Programs and Features in Control Panel. Well I'd tried to remove the XPS Viewer which forms part of .NET 3.0 but it appears that somehow I ended up removing .NET 3.0 from the system as well. I've now reinstalled it (minus XPS Viewer) and all is well.

Terribly sorry about that

[x4000]

No problem -- that's good to know!  I'll let the SlimDX folks know about that, so they can close the issue on their end, too.  This sort of thing happens, so really don't sweat it.