1,146 reputation
311
bio website code4k.blogspot.com
location Japan
age 40
visits member for 2 years, 5 months
seen 23 hours ago

Game Engine R&D Developer at SiliconStudio, Author of SharpDX and NShader, passionate by 3D Real-Time Graphics, Demomaking, Sound synthesis, C#/.Net, DirectX, XNA.


2d
comment Serious Memory leak using SlimDX Texture.FromMemory()
Yes you can avoid it as I said in my previous comment by updloading directly a decoded image buffer to a texture buffer using dynamic textures, without creating a texture at each frame, this is the recommended way to do it. Creating a texture on each frame will lead to the kind of memory leak you have, no matter it is managed wrapper or native C++. Also animating an image can be done directly on the GPU, but it requires you to dig into D3D9
Apr
16
comment Serious Memory leak using SlimDX Texture.FromMemory()
You should avoid allocating the texture inside the rendering loop but only at init time as the device will often not garbage collect it immediately. In case of updating the texture repeatdly at each frame, consider performing the update from a bitmap pointer to an existting texture youself
Apr
15
answered SharpDX.Toolkit setting constant buffer
Apr
14
comment SharpDX.Toolkit setting constant buffer
As the effect is handling all the constant buffers, why don't you update the variable slideX...etc. directly on the effect?
Mar
3
revised Difference between texture arrays and multiple single textures?
Remove trilinear as this was wrong
Mar
3
comment Difference between texture arrays and multiple single textures?
@NathanReed Oops, just checked this and you are absolutely right. I have updated my answer to reflect this. Sorry for giving false direction.
Mar
3
comment Difference between texture arrays and multiple single textures?
@NPS I did verify and arrays of texture cannot be indexed dynamically (which make sense and the reason why Texture2DArray were introduced). I have updated my answer.
Mar
3
revised Difference between texture arrays and multiple single textures?
Add array of texture cannot be indexed dynamically
Mar
2
revised Difference between texture arrays and multiple single textures?
Use term trilinear instead of bilinear
Mar
2
answered Difference between texture arrays and multiple single textures?
Feb
17
comment Read part of texture using SharpDX
This could be a bug. Could you provide a reproducible simple VS project on github issues github.com/sharpdx/SharpDX/issues so that we can have a look at this?
Feb
11
comment Instancing with the SharpDX toolkit
SharpDX is using Assimp.net for loading/converting 3d models to toolkit model. The code is specific to the toolkit conventions/layout/object model, so your code will be. You can always have a look at the model converter in SharpDX.Toolkit to learn how it is done (github.com/sharpdx/SharpDX/blob/master/Source/Toolkit/…)
Feb
2
comment Instancing with the SharpDX toolkit
The toolkit model is not supporting instancing. You should not have to modify Effect. It is a couple of lines to modify in Model/ModelMesh/MeshPart files (only signature in Model and ModelMesh to pass the instancing buffer and MeshPart to pass the instancing buffer along the vertices buffer to d3d11) and you have to recreat the layout of the MeshPart. Instancing is something that is a bit more difficult to standardize, as you can put whatever you want in the instancing bufffer, hence the layout would change...etc. But again, a couple of line to modify in the toolkit to match your needs
Feb
2
awarded  Commentator
Feb
2
comment Instancing with the SharpDX toolkit
There is a sample with a custom effect in the SDK that is working. Simply put the build action "ToolkitFxc" on the effect and it should be compiled at compile time. The main problem is not the effect but to override the default behavior of MeshPart.Draw to pass a layout with instancing, as long as vertices and instancing buffer.
Feb
1
answered Instancing with the SharpDX toolkit
Nov
14
awarded  Yearling
Oct
6
answered Memory Leak in SharpDX
Jun
11
awarded  Caucus
May
29
awarded  Nice Answer