• Advertisement
Sign in to follow this  

MDX 2.0 has been knifed

This topic is 4159 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Don't take my word for it. MDX 2.0 was deprecated, we knew that much, but apparently its deprecation is a little more violent than I and most other people believed.
Quote:
I have no doubt this will raise the ire of many users
I'm not going to say much more till I've had a chance to compose a more...calmed response, but let's just say that this quote is an extraordinary understatement. Combined with the crippled state of XNA at the moment, it means MDX 1.1 is the only viable solution to any kind of managed dev. For a group of people who are trying to push managed development into games so heavily, these people certainly have a interesting way of going about it.

Share this post


Link to post
Share on other sites
Advertisement


While I am quietly smug I stayed with MDX 1.1, I think this is a pretty silly move by the DX team.

Share this post


Link to post
Share on other sites
I can't say that I have done any work with the XNA framework (yet), but it really wouldn't surprise me if they added more functionality to it for the next release.

Share this post


Link to post
Share on other sites
Now I'll be the first to admit that I'm not really up to date with various managed DX stuff, but I thought MDX was a more general purpose library, whereas XNA is solely game-orientated. Isn't MS basically saying "if you're not writing a game, we don't care"?

Share this post


Link to post
Share on other sites
Sigh.

Is the equivalent functionality going to be restored in XNA? I haven't set up the beta yet and I'm in the process of wrapping my head around MDX 1.1 -- was hoping they wouldn't send 2.0 to its grave too soon.

Either way, here's what Mister MDX himself (tom miller) had to say about the 'MDX 1 or MDX 2?' -->Tom's blog

As he says, MDX 2.0 was never intended for anything beyond beta...I guess they were just warming up for XNA -- but not having played with XNA yet, I can't say.


~Shiny

Share this post


Link to post
Share on other sites
Quote:
Original post by OrangyTang
Now I'll be the first to admit that I'm not really up to date with various managed DX stuff, but I thought MDX was a more general purpose library, whereas XNA is solely game-orientated. Isn't MS basically saying "if you're not writing a game, we don't care"?

While the XNA framework beta is very game oriented, it is by no means solely for games. It is very possible to use the XNA framework with ordinary winform controls as shown here.

Regards,
ViLiO

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Quote:
Original post by Shiny
Is the equivalent functionality going to be restored in XNA? I haven't set up the beta yet and I'm in the process of wrapping my head around MDX 1.1 -- was hoping they wouldn't send 2.0 to its grave too soon.


MDX 1.1 to XNA Mifration Guide outlines the main differences.

Share this post


Link to post
Share on other sites
well, I'm glad I went back to MDX 1.1 when I heard 2.0 wasn't going to be continued. The only reason I started using it originally was because it had Font.MeasureString. But they added to MDX 1.1 at some point this year, so I went back. They probably do this timebomb thing in most of their betas... does anyone know? I wonder if they have the same thing in XNA... I would guess so...

Share this post


Link to post
Share on other sites
Just bumping this -- remember, Oct 5 is the deadline! All MDX 2 apps turn off on Friday.

Share this post


Link to post
Share on other sites
I haven't used MDX, but I don't understand why they would do this. Why don't they just let it languish into obscurity like DirectDraw?

Share this post


Link to post
Share on other sites
Anyone tried setting the system clock back to see if it "defeats" the timebomb?

I simply cannot understand the logic behind keeping this date a secret (I'm not aware of seeing this date explicitly written anywhere) given how it makes it difficult (if not impossible) to even run the existing/reference code. How are people supposed to port to MDX1.1 or XNA if they can't even run their existing code?!

Quote:
I don't understand why they would do this.
Quote:
They probably do this timebomb thing in most of their betas... does anyone know?
Yup, its fairly standard to timebomb beta's. I'm pretty sure my beta copies of Vista and Office expire early next year. The difference, as I see it, is that this timebomb was not disclosed (or, at least, not disclosed in an obvious manner) - someone finding out about it by accident a mere 2 weeks before the deadline is just wrong [flaming].

Whilst I doubt it'd happen, I think the only good thing that could happen is for a new build of MDX2 to appear in the October '06 SDK with an extended time-limit to cover migration to a final XNA Framework (or even just giving time to back-port to MDX1.1). Although, from what I currently see that aint likely to happen.


Guess there are still some definite advantages to sticking with native code - I'm not aware of any relevant timebombs in the D3D10 beta's (famous last words?)...

Cheers,
Jack

Share this post


Link to post
Share on other sites
Quote:
Original post by jollyjeffers
Anyone tried setting the system clock back to see if it "defeats" the timebomb?
The reversed code that was posted on the XNA forums was relatively crude, and I'm fairly certain that date munging will work.

The only bright side of all this is that porting to MDX 1.1 is relatively easy to do.

Share this post


Link to post
Share on other sites
Quote:
Original post by Simian Man
Why don't they just let it languish into obscurity like DirectDraw?
DDraw was slightly different - it was deprecated and was actually a full/final/retail component of DirectX. DirectDraw had an official lifetime and support period, whereas MDX2 didn't...

Jack

Share this post


Link to post
Share on other sites
David has extended an offer

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=742919

"If your company is affected by the timebomb of MDX 2.0, please send an email to xna@microsoft.com and indicate MDX 2.0 somewhere in the subject line. "

I assume that by 'company' he is looking for people who may have business issues rather than hobbiests but its there if you want to try.

Share this post


Link to post
Share on other sites
Quote:
Original post by ViLiO

:D

By the way, the first time I read about dropping the DX10 managed pool, MDX came to my mind. In some way, it didn't catch me as surprise.
I still don't get the point of MDX in the first place. Don't you like the inner obscurities of bits? (Ok, that's really a joke, I can see the benefits of faster development).

I wish you a good transition! Good Luck!

Share this post


Link to post
Share on other sites
Setting your system time back also works ok, it's obviously very tedious and you can't ship it that way, but at least it still works. You can set the system time on program start and set it back to normal on exit, of course if your program crashes...

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Quote:
Original post by Daggett
Setting your system time back also works ok, it's obviously very tedious and you can't ship it that way, but at least it still works. You can set the system time on program start and set it back to normal on exit, of course if your program crashes...


You could not ship it anyways without installing the full DirectX SDK on the end user machine. If you bundled the DirectX dll's with your application then you would be violating Microsofts License. Plus MS usually has riles against shipping products that use beta software.

Share this post


Link to post
Share on other sites
Quote:
Original post by Anonymous Poster
Quote:
Original post by Daggett
Setting your system time back also works ok, it's obviously very tedious and you can't ship it that way, but at least it still works. You can set the system time on program start and set it back to normal on exit, of course if your program crashes...


You could not ship it anyways without installing the full DirectX SDK on the end user machine. If you bundled the DirectX dll's with your application then you would be violating Microsofts License. Plus MS usually has riles against shipping products that use beta software.

True, but apparently some people did or they probably wouldn't have made the offer to extend the timebomb for your company.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement