DirectX timebombexception

King Harold · Post by **King Harold** » Tue 12 Dec, 2006 6:04 pm

Well, DirectX expired, so what do I do now? I tried reÃƒÂ¯nstalling (the newest redist version) but I still get that exception.

hop · Post by **hop** » Tue 12 Dec, 2006 7:11 pm

...?

Both the DirectX runtime and software development kit are available free of charge.

King Harold · Post by **King Harold** » Tue 12 Dec, 2006 8:44 pm

screeny 1
screeny 2

This is after installing the newest redist version of DirectX 9.0.

Post by **tr1p1ea** » Wed 13 Dec, 2006 12:27 am

You are certain it actually installed directx and didnt just skip over it because you arent running SP2?

hop · Post by **hop** » Wed 13 Dec, 2006 7:59 am

Well, maybe you should "upgrade to the latest version from http://www.microsoft.com/directx".

You should really know how to read dialog boxes before installing beta or pre-release versions of hardware acceleration software.

King Harold · Post by **King Harold** » Wed 13 Dec, 2006 2:39 pm

hop.. I told you that I DID upgrade it. Btw, you have a %22 in your link (a quote).
the problem is that it doesn't help

And I didn't skip anything, I downloaded DirectX and installed it.

Fact is that the DirectX version installed is NOT a pre-release version

hop · Post by **hop** » Wed 13 Dec, 2006 2:55 pm

Actually, there's a link in my quote in my link, not the other way around. And the board put it there.

http://support.microsoft.com/kb/311805

Also proof it with a pic, you may have mis-clicked when you where looking for the download.

Post by **benryves** » Wed 13 Dec, 2006 2:56 pm

I take it you are running a legal, up-to-date version of Windows XP SP2.

I'd download and install the full version of the latest SDK.

King Harold · Post by **King Harold** » Wed 13 Dec, 2006 3:07 pm

yes, look:

Stuart Laughlin wrote: Happy Time Bomb Day! You weren't planning on using that library anymore, were you?

The silence from Microsoft is deafening. Then again, so is the silence from the community.

Was anyone out there (besides me) actually and seriously using MDX2? If so, what are you doing now? Using MDX1.1, XNA, or 'other'?

alright, I give up, I'll just use XNA and try an' port the old code..

(I could allways take a hexeditor and change the timebomb date to somewhere in 2080 though

)

edit: XNA has those effect files, they're confusing (though I'd bet they're pretty powerfull if you know how to use them properly)

Post by **benryves** » Wed 13 Dec, 2006 3:34 pm

Oh, wait, you were using MDX 2? People have known that it's being killed off for a long time. Most of it ended up in XNA, so yes, use that.

hop · Post by **hop** » Wed 13 Dec, 2006 5:14 pm

Note that this error message may describe DirectX or a DirectX component such as Microsoft DirectDraw.

King Harold · Post by **King Harold** » Wed 13 Dec, 2006 5:27 pm

benryves wrote:Oh, wait, you were using MDX 2? People have known that it's being killed off for a long time. Most of it ended up in XNA, so yes, use that.

I think I've overlooked it..

Why is it 'discontinued' anyway?

Post by **benryves** » Wed 13 Dec, 2006 5:56 pm

King Harold wrote:Why is it 'discontinued' anyway?

Why does there need to be two wrappers around DirectX? It makes little sense for MS to have both MDX 2.0 and XNA, when it's better to focus on a single end-product.

What is the state of Managed DirectX 2.0 beta? (from September).

King Harold · Post by **King Harold** » Wed 13 Dec, 2006 6:28 pm

Well, what I mean is, they could have left it open anyway, without doing anything about it.. And focus on XNA

Post by **kv83** » Wed 13 Dec, 2006 8:02 pm

If they did that, they would have to support it, like answering mail and stuff. Closing it down for good, keeps everyone away from an unsupported and outdated library and lead everyone to the new library instead.