The Summer 2004 SDK Update For DirectX has been released..

-- Official announcement - DX Web site should be updated soon..

The DirectX(r) Team is pleased to announce the final release of DirectX 9.0 SDK Update (Summer 2004)!

The DirectX 9.0 SDK Update (Summer 2004) contains updated versions of the D3DX library, graphics samples, sample framework, tools and Managed DirectX documentation. Areas of concentration in the DirectX 9.0 SDK Update (Summer 2004) release are:

- HLSL support for Pixel Shader & Vertex Shader 3.0
- Effects Framework performance improvements
- Pre computed Radiance Transfer improvements
- New Sample framework
- New & Updated Samples
- Improved Documentation
- PIX tool for better debugging of Direct3D applications
- Introduction of the Preview Pipeline for easier content creation

For information on what is supported in shader model 3.0, refer to the updated reference documentation. You can install the final releases from the below locations.

Software Developer Kit (230Mb+)

Extras (40Mb+)

Symbols (20Mb+)

Release Notes

Please feel free to post any concerns and/or discuss any issues with this SDK release within this forum, the public newsgroups or mail us directly at


Comments (28)

  1. juju says:

    Well done

  2. Russ C. says:

    Thanks for the hard work Tom!

  3. Brian Brown says:

    At first glance it looks like you guys put a lot of work into the documentation. Great job Tom!! I started playing around with the samples and specifically the Custom UI controls. One thing I noticed on my box was that whenever I ran any of the samples with the new UI controls they were flashing when in windowed mode. When I went to full screen they were fine and looked rock solid. Any ideas on why that might be?

  4. Chris C. says:

    Documentation is much much better thanks 🙂 I still have the bug where Intellisense doesnt kick in on the CustomVertex Class, is this just me, or is it a known issue? I.e. CustomVertex.[Intellisense] all I got with 2003 Update and now 2004 is "Equals" and "ReferenceEquals", none of the Vertex types popup 🙁

  5. Russ C. says:

    Chris C.

    I’m glad it’s not just me!

    It comes back, if I do one of the following (randomly)

    Recompile Successfully

    Create a new Class

    and always seems to come back if I remove the reference to DirectX and re-add it or restart VS.

    Strange, eh ?

  6. John B. says:

    Can anyone comment on the Changes included for Managed DirectX?

  7. Chris C. says:

    Russ C,

    Totally strange, I’ve tried all the things you suggested and it still doesn’t come back, equally strange the object browser shows that CustomVertex is just an empty class. Of course, it still compiles, but it makes working with CustomVertex structs clumsy.

  8. juju says:

    1) Documentation is much better now

    2) Occlussion query bug is eliminated

    3) UI Controls rocks

    4) Texture/State manager is nice

    5) We can play now with vs/ps 3.0, including HLSL fxc.exe

    6) PIX is good to profile your DX programs

    7) New samples are good ( specially shadowmap, new radiance transfer , etc )

    8) Improved radiance transfer engine!!!

    Well done, well well done, continue doing the best job Tom & company!!!

  9. ShadowChaser says:

    Looks pretty good, but I still don’t like the documentation. Why does it not match the standard .net style?

    The little IE-documentation-ish tab-interface to view methods/fields/properties/events/etc frustrates the heck out of me – it sure would be nice to just have a "members" page like in .NET.

    The content looks good though, just gotta work on the formatting! 🙂

  10. Firefox says:

    I guess the delay in your next book’s release date is connected to this 2004 Summer Update… Are there any news regarding the contents of the book, Managed Code updates (due to 2004 Summer Update)?

  11. Mary C. says:

    I heard SP2 will contain DirectX 9.0c by default. Will it have Managed DX installed by default? I think it should be.

  12. Fredrik says:

    Does anyone have any suggestion on a forum or any other place where questions on DX9.0C are likely to be answered?

    I am having huge difficulties using the new sample framework and need help badly…

  13. Max says:

    You fixed CalculateRect! Chris C: I have that problem too. It goes away when I exit and restart VS.NET – it is sort of annoying, but I suspect it’s an issue with the way intellisense handles inner structs, and not with MDX.

  14. Andy says:

    CustomUI runs like a bag-o-nails.. Only getting 0.52 fps and this is with the pixel shader debug option. None of the others run. Think I’ll be going back to previous good work

  15. Andy says:

    I think this is because I am running Windows 2003 server and Reference Rasteriser is not installed, WHY did you remove this??????

  16. Lonnie McCullough says:

    One of my biggest complaints about MDX has been that it will bring System.Windows.Forms into the process even when I don’t want it there. It adds an extra ~3MBs to my process of absolutely wasted space. I’m not sure if the entire 3MBs is attributable to WinForms, but it certainly contributes in a big way. I was wondering if there is anyway to force WinForms not to load? Modify code paths so that it is brought in only when the constructor that takes a Control for the device window is used… This would be awesome because I really want nothing to do with WinForms. Other than that MDX is the bomb. Maybe this has been addressed in the most recent update?

  17. Ralf says:

    I like MDX but redistribution of it is still a mess.

    The webupdate did not install it. The only way to get it is download the full redist (33MB) and run it with a special commandline parameter. DX9.0c make it even more worse. The redist only contains the newest version MDX. If somebody have never install MDX with a full DX9.0b runtime redist my old apps will not run.

    Because of the .net framework my apps are small but than I have to force my customers to download Megabytes of data to get the apps running.

    I still hope that the MDX-Team will give us developer for each MDX version a small installer for redistribution. Or even better make each MDX Version available over windows update.

  18. xian says:

    Strangely, it works from home, but on my work computer none of the examples will run without an exception.

  19. xian says:

    Manager.Adapters.Default.Adapter – Always throws the exception, fwiw. Worked perfectly in 1.0.1901.0.

  20. Jeff Johnson says:

    Sprite.Draw2D has a problem when attempting to rotate for the summer 2004 sdk … it will always rotate around the top left of the screen instead of where the sprite is located. This feature worked fine in the 2003 sdk …

  21. Max says:


    Why the DirectPlay has been deprecated? And when would it be finaly removed?

  22. John Mabbott says:

    Hi Tom,

    I think I’ve spotted a minor bug in the MDX GUI code, dxmut.cs (line 2622). Shouldn’t the contents of the if/else statement’s be reversed below? I’m not sure where the right place to make bug reports are…

    if (State.WindowTitle != null && State.WindowTitle.Length > 0)


    System.Windows.Forms.MessageBox.Show(errorText, "DirectX Application",

    System.Windows.Forms.MessageBoxButtons.OK, System.Windows.Forms.MessageBoxIcon.Error);




    System.Windows.Forms.MessageBox.Show(errorText, State.WindowTitle,

    System.Windows.Forms.MessageBoxButtons.OK, System.Windows.Forms.MessageBoxIcon.Error);


  23. Jice says:


    I ported my project from 9.0b to summer 2004. I use DrawIndexedPrimitive with effects. Since I recompiled it, nothing renders anymore!! I changed the effects API call as stated in the doc and everything compile without warning.

    Has some1 this problem ?

  24. As I said in my blog : I’m VERY VERY VERY ANGRY about DX 9.0c SDK.

    For all explanation, take a look at :

  25. Henk Bosman says:

    Any know why I my little game uses 50% CPU speed (2.4Ghz P4).

    I only use:

    using (Sprite s = new Sprite(device))



    // render code



    This is done in a Direct3D window.


Skip to main content