Jump to content
  • Advertisement
Sign in to follow this  
jpetrie

SlimDX August 2009 Now Available

This topic is 3169 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

The SlimDX August 2009 official SDK release is now available! Get it now. This is a major release in terms of new functionality, mainly due to the long-awaited inclusion of (non-beta) Windows 7 support. The new Windows 7 features include Direct3D 11, Direct2D, and DirectWrite. What's New Full release notes can be found here. Major points to be aware of include:
  • Performance improvements to many calls due to improved stack allocation policies for local interop storage.
  • Quaternion multiplication is now being performed in the correct direction (that is, the direction that is consistent with Direct3D).
  • Quaternion subtraction is now being performed correctly (before the operation was actually multiplying).
  • Direct3D 10 now exposes predication support on the device.
  • Many missing methods related to shader compilation and manipulation were added to the Direct3D 10 APIs.
  • Support for Direct3D 10.1 was added.
  • Support for Direct2D is now official.
  • Support for Direct3D 11 is now official.
  • Support for DirectWrite is now official.
  • Lots and lots and lots of bug fixes.
Do note that we recommend considering using the latest SVN release for active development using Direct2D, Direct3D 11, or DirectWrite as these APIs are still very new and are most likely to receive the most updates. What's With the Name? You might be wondering why this is the "August" release, despite the fact that we're well into October. We chose to keep the same name as the official DirectX SDK that corresponds to this SlimDX release in order to reduce confusion and simplify discussion. Future Directions The August release of the official SDK marks the last release of the DirectX SDK for which Microsoft has provided a firm ship date. We are not currently aware of when the next release of the SDK will be. Our plans for the next iteration of SlimDX include some fairly major changes to the library, including support for interfaces, a redesigned sample framework and sample set, and some other surprises. You will most likely be able to hear about these changes via the developer blogs and/or Twitter feeds. This will help you keep abreast of the upcoming changes, especially if you're a user who does not track the head SVN revision of SlimDX. Finally... ...we'd like to thank all our users for enduring the wait for this release; the official DirectX SDK shipped later than expected and included a number of additions that required more changes than usual on our end to update SlimDX to target the latest SDK. These delays unfortunately pushed us into a timeframe where none of the SlimDX developers had as much time to dedicate to the project as we would have liked, which delayed our release even further, and we appreciate the patience shown by our users while we addressed the last lingering bugs and issues. As always, please report any bugs, problems or feature requests on our issues page and to stay up to date with the latest happenings regarding SlimDX, you can follow us on Twitter!

Share this post


Link to post
Share on other sites
Advertisement
About time. Yeesh, I tell you, we start letting promit slack off and this happens. [grin]

Share this post


Link to post
Share on other sites
Quote:
Quaternion multiplication is now being performed in the correct direction (that is, the direction that is consistent with Direct3D)


This confused me so much a few months ago. I need to redo some of my camera code, but at least it will be a bit clearer.

This looks like a great release!

Share this post


Link to post
Share on other sites
Quote:

This confused me so much a few months ago. I need to redo some of my camera code, but at least it will be a bit clearer.

Yes, it was a very unfortunate failure on our part, which is why -- even though its a minor change -- we're calling it out in the release notes. :)

Share this post


Link to post
Share on other sites
This is great news. A few quick questions:

1) Are there examples on using Direct2D and Compute Shaders?

2) Can I build/test/deploy SlimDX code that uses ONLY those two APIs on class 10.1 hardware?

3) Lastly...anyone tried any of this on WPF?

Thanks for the great work guys, can't wait to get started!

-L

Share this post


Link to post
Share on other sites
Quote:

1) Are there examples on using Direct2D and Compute Shaders?

No, since we are heavily re-engineering the sample framework and revising the sample set for the next release, we did not do any work on them for this release.

Quote:

2) Can I build/test/deploy SlimDX code that uses ONLY those two APIs on class 10.1 hardware?

I'm not sure exactly what you mean; we delay-load the DLLs we depend on, and as long as you are doing something that is supported by the native API, you should be fine. I'm not precisely sure how much of what you seem to be asking you'll get from the feature level support provided by D3D.

Quote:

Lastly...anyone tried any of this on WPF?

A WPF sample will be in the next release. I've been talking with some users who are using WPF and SlimDX, and what I've heard is that the previous D3DImage related approaches don't work as well, or something. But I don't have much in the way of details right now.

Share this post


Link to post
Share on other sites
Thanks alot for the release! I started to work on my new D3D11 Engine and noticed some things:

1) Is there no Mesh class in Direc3D11? The D3D11 Namespace doesn't contain such a class, while D3D9 and 10 got it. Is the Mesh support deprecated, meaning that we need to load and handle mesh data ourselves? I guess it wouldn't be that dramatic, but it would make getting into it alot harder.

2) Is it really necessary to construct a new InputLayout for every single Shader Pass? I'm just wondering because it wasn't in the DX9 VertexDeclaration.

3) Another very minor thing i noticed is that Direct3D11.EffectPassDescription returns an Direct3D10.ShaderSignature object. I guess it isn't relevant at all, but the D3D10 and D3D11 namespace mixup is a little bit irritating. Is it meant to be this way?

Thanks for your help!

Share this post


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

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!