GameEx freezes

[night]

hi Tom i havent upgraded for quite awhile so i thought now it was time to do so

but GameEx freezes and when i press Esc. key this come up (picture below)

i havent upgraded any drivers or got any new hardware so it puzzles me alittle.

[Tom Speirs]

hi Tom i havent upgraded for quite awhile so i thought now it was time to do so

but GameEx freezes and when i press Esc. key this come up (picture below)

i havent upgraded any drivers or got any new hardware so it puzzles me alittle.

Hi Night, can you post the log please (after this happens). Glad to see your still around. Wondered where you got to:)

[headkaze]

This could be an issue with using the MDX 1.1 runtimes in .NET 2.0, but I'm not entirely sure. One thing I do recommend though Tom is to update your Visual Studio 2005 to SP1 if you havn't done already.

[Tom Speirs]

This could be an issue with using the MDX 1.1 runtimes in .NET 2.0, but I'm not entirely sure. One thing I do recommend though Tom is to update your Visual Studio 2005 to SP1 if you havn't done already.

Hey Ben, I've been using SP1 since day 1. What makes you think this though?

[Tom Speirs]

Hey Ben, I've been using SP1 since day 1. What makes you think this though?

Edit: Yeah i see the errors actually occuring in MDX - DirectDraw.

Night. Do you consitently get the error?

[headkaze]

There are issues with MDX 1.1 assemblies running in .NET 2.0, the first issue you would probably encounter is loader lock which you can turn off (but aparently this only solves the issue most of the time). The more I'm researching this the more I'm suprised you don't have more problems running GameEx in .NET 2.0. Let hope it's not this underlying problem, as what I have read about it has more specifically been about Direct3D 1.1 assemblies in .NET 2.0, I have no idea if it effects DirectDraw, but it probably does. The next thing is MDX 2.0 has expired (if you try to use it a messagebox pops up saying so) so there is no moving to MDX 2. I'm not even sure what the last version of MDX 1.1 is but you can't move to MDX 2.0 anymore, and forget XNA because you can't use the System.Drawing namespace and my guess is you are using it for some things. Microsoft has done a disappointing job with MDX and alot of people have been burnt trying to keep up with it.

[Tom Speirs]

Yeah its a bugger alright. I've obviously looked into all this stuff.

One of the things I looked at was using an umanaged wrapper for Direct3D or Direct2D. At the moment that looks like the best option, or perhaps the only viable option now. It would also give the option to use DirectX8 and user directdraw and direct3d together.

Nights is the only such report, so lets hope it something else. Maybe he can try a fresh install?

EDIT: According to MS MDX 1.1 is supposed to work fine in .net 2.0. (I read this on the XNA FAQ). I have not read up on thie issues your talking about. I know vs 2005 prompts about the loader lock issue when you try and launch GameEx with the visual studio hosting process enabled.

[night]

Edit: Yeah i see the errors actually occuring in MDX - DirectDraw.

Night. Do you consitently get the error?

yes everytime after i updated i get this error...

its a strange one GameEx starts up fine but when i uses the arrow keys to navigate it Freezes and i hit Esc. and the error the SS is of appears ...

ill try to do a full reinstall with .net and GameEx and ill let you know what happends....

[night]

Update :

i tryed to reinstalled .NET and it was still the same result then i noticed you had Done another update to GameEx i tryed to install that becouse i was completely out of ideas and now it seems to run fine again

i have No idea what caused the error but now after i updated i cant reproduce the error

so now im a happy bastard again cheers