DirectCanvas

Source code checked in, #80132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:49:39 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #80131

Project Collection Service Accounts — Mon, 01 Oct 2012 21:43:10 GMT

Checked in by server upgrade

New Post: Load TGA Image without using WIC

rosenkostov — Tue, 24 Jan 2012 17:25:45 GMT

Hi, found DirectCanvas recently and it is amazing.

How can I load TGA image nativly supported by SlimDX.Direct3D10.Texture2D.FromFile(Device, String) and attach it to drawing layer?

I have one more question. I need to extract raw bytes from a DrawingLayer in BRGA or ARGB buffer after I render something on it.

Thanks.

New Post: Use Case?

oskarK — Thu, 12 May 2011 19:50:36 GMT

Charts with sensible performance comes to mind...

New Post: VC++ 2010 Runtimes

davehorner — Mon, 09 May 2011 13:38:25 GMT

Ok, so pulling the latest from codeplex on my Windows 7 64bit laptop (vs2010) I get working samples! :)
Though, this ultimately should work on my vista machine correct?

Thanks,
--dave

Source code checked in, #66341

JoshB — Fri, 29 Apr 2011 19:20:28 GMT

Fixed oversight for ShaderRenderer changes

Source code checked in, #66340

JoshB — Fri, 29 Apr 2011 19:14:43 GMT

Added Filter property to ShaderEffect and updated ShaderRenderer to allow ShaderEffects to specify Linear or Point filtering

New Post: VC++ 2010 Runtimes

davehorner — Wed, 27 Apr 2011 21:43:13 GMT

This machine has all sorts of stuff on it. It has Microsoft .Net Framework 4 client profile, 4 Extended, 4 Multi-targeting Pack, DirectX SDK Feb 07,DirectX SDK June 2007, VS2005 pro,VS2008 pro,2010 pro

New Post: VC++ 2010 Runtimes

jdsmith99 — Wed, 27 Apr 2011 01:43:27 GMT

@davehorner: do you have the .NET 4 runtimes or Visual Studio installed?

New Post: VC++ 2010 Runtimes

davehorner — Tue, 19 Apr 2011 00:17:58 GMT

Additional information that might be handy, I did notice that the handle coming back from IntPtr GetSharedHandle(SlimDX.Direct3D10.Texture2D Texture) was negative (-2147419200). All the other parameters looked OK to me.

New Post: VC++ 2010 Runtimes

davehorner — Mon, 18 Apr 2011 23:59:54 GMT

I installed the directx_Jun2010_redist.exe as linked on the home page. I also tried installing the VC++2010 runtimes found here:

Microsoft Visual C++ 2010 Redistributable Package (x86)
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84

When I tried to run WindowsFormsTest, I found that it referenced a Wildlife.wmv and failed, I placed a file there...
I now get this:
a TargetInvocationException when doing _touchHandler = Factory.CreateHandler<Windows7.Multitouch.TouchHandler>(panel1);

I am running on a Vista Ultimate 32bit OS, so that means I won't be playing with that sample on this machine....

So, I then went back to the next sample, WPFTestApp, when I run it, I get the following Direct3D9Exception (E_INVALIDARG) on
E_INVALIDARG: An invalid parameter was passed to the returning function (-2147024809)

> DirectCanvas.dll!DirectCanvas.D3DImageSlimDX.SetBackBufferSlimDX(SlimDX.Direct3D10.Texture2D Texture = {SlimDX.Direct3D10.Texture2D}) Line 77 C# DirectCanvas.dll!DirectCanvas.WPFPresenter.SetBackBuffer() Line 188 + 0x34 bytes C# DirectCanvas.dll!DirectCanvas.WPFPresenter.InitD3DImage(int width = 825, int height = 650) Line 183 + 0x8 bytes C# DirectCanvas.dll!DirectCanvas.WPFPresenter.WPFPresenter(DirectCanvas.DirectCanvasFactory directCanvas = {DirectCanvas.DirectCanvasFactory}, int width = 825, int height = 650) Line 93 + 0xe bytes C# DirectCanvas.dll!DirectCanvas.WPFPresenter.WPFPresenter(DirectCanvas.DirectCanvasFactory directCanvas = {DirectCanvas.DirectCanvasFactory}, int width = 825, int height = 650, System.Windows.Controls.Image image = {System.Windows.Controls.Image}) Line 103 + 0x11 bytes C# WPFTestApp.exe!WPFTestApp.MainWindow.InitDirectCanvas() Line 171 + 0x62 bytes C# WPFTestApp.exe!WPFTestApp.MainWindow.MainWindow_Loaded(object sender = {WPFTestApp.MainWindow}, System.Windows.RoutedEventArgs e = {System.Windows.RoutedEventArgs}) Line 65 + 0x8 bytes C#

Any thoughts on how to get past this error?

Thanks,
--dave

PS> your dnn article linked on the DirectCanvas home page for the DXVA checker is full of bad links, you might want to remove that reference on the DirectCanvas homepage.

New Post: VC++ 2010 Runtimes

jdsmith99 — Tue, 05 Apr 2011 23:12:17 GMT

In addition to the DirectX runtime noted on the project's home page, apps built with DirectCanvas require the VC++ 2010 runtime. I built some sample apps and deployed them to a "clean" machine. No luck until I installed the VC++ 2010 runtime. I used v 10.0.30319.

New Post: Adding elements dynamically

jdsmith99 — Sun, 03 Apr 2011 02:13:09 GMT

Very cool project.

Any suggestions on adding visual elements at run time? I can think of several ways to do it, but any guidance as to what you think is the best way? For example, if I create a particle simulation, and I want to allow users to, click the mouse to add a new particle to the system...how should I do it (add an additional particle)? Something like a method on my Scene class? Wasn't sure if there was something in the library to handle a case like this or any big gotchas to watch for.

Patch Uploaded: #8760

Marcus417 — Wed, 16 Mar 2011 14:43:35 GMT

Marcus417 has uploaded a patch.

Description:
Simple Memory Leak fix, the D3DImageSlimDX.IsFrontBufferAvailableChanged event was never unregistered.

Now doing so in the Dispose() override, just before freeing the reference to the D3DImageSlimDX.

Source code checked in, #64523

JoshB — Sat, 12 Mar 2011 18:31:22 GMT

Added another RenderOption to ThreeDSample - using a DrawingLayer as a texture for a 3D object

Source code checked in, #64511

JoshB — Sat, 12 Mar 2011 06:31:59 GMT

Added new sample project (ThreeDSample) to show how to render Direct3D10 onto a DrawingLayer Modified DrawingLayer to expose Texture2D IntPtr and RenderTargetView IntPtr, allowing you to get reference using any Direct3D10 framework Added overload to DrawingLayer.DrawText to allow specification of font size

Source code checked in, #64510

JoshB — Sat, 12 Mar 2011 06:28:53 GMT

Fixed bug in WPFPresenter to ensure rendering happens on UI thread

Source code checked in, #64079

JoshB — Wed, 02 Mar 2011 22:57:15 GMT

Updated SlimDx to latest nightly build (rev 1976, http://code.google.com/p/slimdx/) Added D3DImageSlimDX.cs from SlimDx's WpfSample10. Moved old WPFPresenter (and some experimental changes) to WPFBlitPresenter Integrated D3DImageSlimDX into WPFPresenter WPFPresenter now subscribes to CompositionTarget.Rendering for render loop. Start and stop the rendering with WPFPresenter.StartRendering and .StopRendering. Check if rendering with WPFPresenter.IsRenderingActive property. Changed IScene interface into the abstract Scene class and moved it to DirectCanvas.Scenes Moved InputStatus enum to DirectCanvas.Scenes Added Scene.ActivateScene and .DeactivateScene and updated demos to start and stop the video playback WPFPresenter now calls Scene.Render on the CurrentScene property, so you should set CurrentScene to whichever Scene derivative you want it to render and can change it at any time. Added RotationParameters.Empty static property Renamed DirectCanvasM2 namespace, assembly, and window title to WindowsFormsTest Updated WindowsFormsTest and WPFTestApp to work with Scene and other changes Updated Demos scenes to work with new changes

New Post: DirectX9 Support?

LukasFellechner — Fri, 25 Feb 2011 23:23:11 GMT

Hi Jer,

thanks for contributing this project, pretty amazing stuff you got going there. I tried to get this running at home, but first I stumbled over the DX10 HW requirement. On my other machine I could get it running then. While Direct2D is DX10 based, MS put quite a lot of effort into making it still compatible with DX9 HW by using the D3D10Level9 layer. By lowering the FeatureLevel parameter in the device creation call, you can create a DX10 device even on DX9 hardware, and most of the stuff will be HW accelerated.

This however does not work with your solution, because you are using version 4.0 pixel and vertex shaders for your SpriteRenderer. While the SpriteRenderer seems to be highly optimized, offloading the transform calculations to the GPU, you are loosing big part of potential users. Lots of users have rather powerful DX9 cards, yet they cannot run your code at all. Are you considering to add a second rendering path using version 2.0 shaders at some point?

Luke

New Post: Use Case?

ftballguy45 — Thu, 17 Feb 2011 17:18:50 GMT

What are some potential uses for this?