Partager via

.NET 3.5 SP1 Graphics @ Channel 9

  • Article

Sorry for the lack of updates, but we've been pretty busy. On what, you may ask? Our PM, David Teitlebaum, just did a video on Channel 9 showing off the new features. He starts by covering interactive 2D on 3D and improved layered window support, both of which were in 3.5, and he finishes with the customizable ImageEffects, the much improved WriteableBitmap, BitmapScalingMode.NearestNeighbor, and D3DImage.

-- Jordan

Comments

  • Anonymous
    May 13, 2008
    PingBack from http://windows.wawblog.info/?p=31157

  • Anonymous
    May 18, 2008
    Congrats on SP1. I am hoping that for your next release, the WPF 3D team is working on fixing the pipeline perf issue. I'd like to see something like this: <Pipeline>    <ModelVisual3D>        <GeometryModel3D>        <GeometryModel3D>    <ModelVisual3D>        <GeometryModel3D> The fact that efficient use of the pipeline can provide a 10x improvement should be a top priority at this point given the other features that are now available. Currently, folks are doing this on their own like this:    <GeometryModel3D>        <GeometryPart>        <GeometryPart>        etc... In managed code, they are updating the parts every frame during animations, rebuilding the main GeometryModel3D, and setting the new vertex points. Even though this is a 10x perf improvement, the perf could be even greater if things were being tweaked under the hood in unmanaged code on the WPF side. Also, WPF animations won't work as well as WPF hittesting - animations and hittesting have to be done in proprietary ways. If the WPF 3D team is never going to address this issue, they should tell the community, and we can open an open source project to address the issue as best we can. We all know that the proper architecture in this matter is on the Microsoft side. Again, congrats on SP1. rhogue

  • Anonymous
    May 18, 2008
    As a reminder, if Microsoft does the architecture to fix the pipeline issue, they can probably fix the zindex issue at the same time as there is some relationship between the two at the lower level. For those who don't know, objects are not sorted by zindex in the pipeline automatically, which causes another expensive managed per frame (hacked) solution by the community. An Aug 2009 with the pipeline and zindex fixes would be a great time table :) rhogue

  • Anonymous
    May 18, 2008
    We were considering WPF3D for our machine visualizations (that are embedded in WPF UIs). When scenes are animated and get a little bit more dynamic framerates drop like a rock from a cliff. The big advantages of WPF3D (timesaver because of ease of use and constinent APIs compared to the rest of WPF) gets eaten by the hughe amount of work that needs to be done to tweak performance in WPF3D. Our scenes are IMHO not so complex that WPF3D shouldn't be able to handle it. So let me chime in here: WPF3Ds performance really needs to improve otherwise it isn't very usefull. We should get beyond rotating some videocubes with WPF3D