Sign in to follow this  

DX11 About to enter the world of 2d animation under SlimDX...

This topic is 1945 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 next phase in my 2d game framework is animation. At the moment I have just one sprite texture for my moving sprites.

As I am using SlimDX, I don't have the handy sprite-related classes that XNA has. As such, I need to understand the principles of using sprite sheets instead of separate sprite images.

1. What defines a sprite sheet?

Is this just a large image with multiple animation frames organised into their own tiles in that image? Or does it also have some kind of header file which tells you the vectors of the rectangled which bound each image?

2. How are textures mapped from the sprite sheet?

Is this achieved via calls in the C# calling program, or via the HLSL fx file? I am using DX11 by the way.

I'm sure with a little guidance I can get cracking on this. Thanks in advance anyways.[img][/img]

Share this post

Link to post
Share on other sites
I think I know what to do now.

This will allow me to build a sprite sheet from separate images, which I can generate in GIMP easily enough. I would then need to map the texture using the texture coordinate attributes for each CustomVertex object (instance variable of a sprite) in my game.

I'll set the vectors as per the rectangle definitions in the spritesheet config file, and transform them through an orthogonal matrix.

I think this is the principle anyways.[img][/img]

Share this post

Link to post
Share on other sites
OMG No ! Not sprite sheets if you are using DX11. Use a texture array, they are so much better. [img][/img]. Tricky to setup and get to know but so much more powerful after that. Edited by Gavin Williams

Share this post

Link to post
Share on other sites
[quote name='Gavin Williams' timestamp='1347885008' post='4980854']
OMG No ! Not sprite sheets if you are using DX11. Use a texture array, they are so much better. [img][/img]. Tricky to setup and get to know but so much more powerful after that.

Texture arrays are definitely very useful, but I don't think they are a replacement for sprite sheets.
Why do you consider texture arrays so much better for sprite storage?
They definitely have some useful properties, such as texture clamping, which is problematic with sprite sheets,
but what happens when individual sprites have different resolutions or different amounts of animation frames?

Share this post

Link to post
Share on other sites
Of course they are a replacement for sprite sheets. For me it was a no-brainer, one minute i was using sprite sheets and the next minute, life was easier. Texture array's remove the problems inherent to sprite-sheets.

You can contrive any number of scenarios that might break a technique / technology. But that doesn't change the fact that by and large, Texture arrays make sprite sheets (in their regular usage scenario) redundant.

And just thinking about animation frames ... you can have any number of animation frames you like for any particular sprite with texture arrays. Using texture arrays doesn't change how you interpret your sprite collection at the higher level or how you are sampling your sprites to form animation.

And in regards to sprites with different resolutions, how many different resolutions are you talking about ? You could only look at sprite sheets as being more appropriate for particular situations. You can store sprites with different resolutions into a texture array, that's no problem, if you're happy with burning some empty memory (I think compression will mitigate that cost), and if there are only a few exceptionally small/large sprites then you can divide them up, and pass them in via another texture slot, maybe on their own or in another array, though i suppose you might want to stick with a single sprite pipeline. Anyway im not arguing that sprite sheets aren't useful in those scenarios, im just not familar with having to do that, and i stand by my point that texture arrays are better than sprite sheets (in most circumstances).

I would concede though that if the OP described how they were going to use the sprites, what sizes etc, then perhaps Hyunkel's points should be considered if appropriate. Edited by Gavin Williams

Share this post

Link to post
Share on other sites
I agree that texture arrays are ideal in a situation where you have many sprites of the same (or nearly the same) size.
However, as you said, it depends entirely on what the OP is doing.
The last project I worked on for example, had completely arbitrary sprite sizes.

I suppose we both agree that if you can use texture arrays instead of sprite sheets, you should definitely go for it.

Share this post

Link to post
Share on other sites
Thanks guys - but I am not familiar with using texture arrays.

In terms of what I am seeking to achieve, I can explain.

For my simple Pacman game, upon detecting a valid keypress in the game look I initiate movement to the next tile on the game board. I want to change the texture for Pacman every pixel of movement. This means changing the texture of the sprite every iteration of the game loop.

The method of retrieving said texture is the issue here. Should this be via sprite sheet, whereby I just change the texture mapping, or should the texture itself be swapped out for another? If the latter, I take it that I can either a) load a new individual texture, or b) retrieve it from a pre-loaded array of textures. Option b) would certainly seem to be less expensive, since the overheads of the load method will be negated in favour of in-memory data retrieval.

That said, if a spritesheet is in memory, I am not clear on how computationally expensive this is compared against using a texture array.

Do I have the right idea here? [img][/img]

Share this post

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

  • Similar Content

    • By mister345
      Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
      I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
      double clicked on the frame to open it, but no idea where to go from there.
      I've been searching for hours and there's no information on this, not even on the Microsoft Website!
      They say "open the  Graphics Pixel History window" but there is no such window!
      Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
      Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?
      All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated
      and Microsoft's instructions are horrible! Somebody please, please help.

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
    • By xhcao
      Is Direct3D 11 an api function like glMemoryBarrier in OpenGL? For example, if binds a texture to compute shader, compute shader writes some values to texture, then dispatchCompute, after that, read texture content to CPU side. I know, In OpenGL, we could call glMemoryBarrier before reading to assure that texture all content has been updated by compute shader.
      How to handle incoherent memory access in Direct3D 11? Thank you.
    • By _Engine_
      Atum engine is a newcomer in a row of game engines. Most game engines focus on render
      techniques in features list. The main task of Atum is to deliver the best toolset; that’s why,
      as I hope, Atum will be a good light weighted alternative to Unity for indie games. Atum already
      has fully workable editor that has an ability to play test edited scene. All system code has
      simple ideas behind them and focuses on easy to use functionality. That’s why code is minimized
      as much as possible.
      Currently the engine consists from:
      - Scene Editor with ability to play test edited scene;
      - Powerful system for binding properties into the editor;
      - Render system based on DX11 but created as multi API; so, adding support of another GAPI
        is planned;
      - Controls system based on aliases;
      - Font system based on stb_truetype.h;
      - Support of PhysX 3.0, there are samples in repo that use physics;
      - Network code which allows to create server/clinet; there is some code in repo which allows
        to create a simple network game
      I plan to use this engine in multiplayer game - so, I definitely will evolve the engine. Also
      I plan to add support for mobile devices. And of course, the main focus is to create a toolset
      that will ease games creation.
      Link to repo on source code is -
      Video of work process in track based editor can be at follow link: 

    • By mister345
      I made a spotlight that
      1. Projects 3d models onto a render target from each light POV to simulate shadows
      2. Cuts a circle out of the square of light that has been projected onto the render target
      as a result of the light frustum, then only lights up the pixels inside that circle 
      (except the shadowed parts of course), so you dont see the square edges of the projected frustum.
      After doing an if check to see if the dot product of light direction and light to vertex vector is greater than .95
      to get my initial cutoff, I then multiply the light intensity value inside the resulting circle by the same dot product value,
      which should range between .95 and 1.0.
      This should give the light inside that circle a falloff from 100% lit to 0% lit toward the edge of the circle. However,
      there is no falloff. It's just all equally lit inside the circle. Why on earth, I have no idea. If someone could take a gander
      and let me know, please help, thank you so much.
      float CalculateSpotLightIntensity(     float3 LightPos_VertexSpace,      float3 LightDirection_WS,      float3 SurfaceNormal_WS) {     //float3 lightToVertex = normalize(SurfacePosition - LightPos_VertexSpace);     float3 lightToVertex_WS = -LightPos_VertexSpace;          float dotProduct = saturate(dot(normalize(lightToVertex_WS), normalize(LightDirection_WS)));     // METALLIC EFFECT (deactivate for now)     float metalEffect = saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));     if(dotProduct > .95 /*&& metalEffect > .55*/)     {         return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));         //return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace))) * dotProduct;         //return dotProduct;     }     else     {         return 0;     } } float4 LightPixelShader(PixelInputType input) : SV_TARGET {     float2 projectTexCoord;     float depthValue;     float lightDepthValue;     float4 textureColor;     // Set the bias value for fixing the floating point precision issues.     float bias = 0.001f;     // Set the default output color to the ambient light value for all pixels.     float4 lightColor = cb_ambientColor;     /////////////////// NORMAL MAPPING //////////////////     float4 bumpMap = shaderTextures[4].Sample(SampleType, input.tex);     // Expand the range of the normal value from (0, +1) to (-1, +1).     bumpMap = (bumpMap * 2.0f) - 1.0f;     // Change the COORDINATE BASIS of the normal into the space represented by basis vectors tangent, binormal, and normal!     float3 bumpNormal = normalize((bumpMap.x * input.tangent) + (bumpMap.y * input.binormal) + (bumpMap.z * input.normal));     //////////////// LIGHT LOOP ////////////////     for(int i = 0; i < NUM_LIGHTS; ++i)     {     // Calculate the projected texture coordinates.     projectTexCoord.x =  input.vertex_ProjLightSpace[i].x / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     projectTexCoord.y = -input.vertex_ProjLightSpace[i].y / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     if((saturate(projectTexCoord.x) == projectTexCoord.x) && (saturate(projectTexCoord.y) == projectTexCoord.y))     {         // Sample the shadow map depth value from the depth texture using the sampler at the projected texture coordinate location.         depthValue = shaderTextures[6 + i].Sample(SampleTypeClamp, projectTexCoord).r;         // Calculate the depth of the light.         lightDepthValue = input.vertex_ProjLightSpace[i].z / input.vertex_ProjLightSpace[i].w;         // Subtract the bias from the lightDepthValue.         lightDepthValue = lightDepthValue - bias;         float lightVisibility = shaderTextures[6 + i].SampleCmp(SampleTypeComp, projectTexCoord, lightDepthValue );         // Compare the depth of the shadow map value and the depth of the light to determine whether to shadow or to light this pixel.         // If the light is in front of the object then light the pixel, if not then shadow this pixel since an object (occluder) is casting a shadow on it.             if(lightDepthValue < depthValue)             {                 // Calculate the amount of light on this pixel.                 float lightIntensity = saturate(dot(bumpNormal, normalize(input.lightPos_LS[i])));                 if(lightIntensity > 0.0f)                 {                     // Determine the final diffuse color based on the diffuse color and the amount of light intensity.                     float spotLightIntensity = CalculateSpotLightIntensity(                         input.lightPos_LS[i], // NOTE - this is NOT NORMALIZED!!!                         cb_lights[i].lightDirection,                          bumpNormal/*input.normal*/);                     lightColor += cb_lights[i].diffuseColor*spotLightIntensity* .18f; // spotlight                     //lightColor += cb_lights[i].diffuseColor*lightIntensity* .2f; // square light                 }             }         }     }     // Saturate the final light color.     lightColor = saturate(lightColor);    // lightColor = saturate( CalculateNormalMapIntensity(input, lightColor, cb_lights[0].lightDirection));     // TEXTURE ANIMATION -  Sample pixel color from texture at this texture coordinate location.     input.tex.x += textureTranslation;     // BLENDING     float4 color1 = shaderTextures[0].Sample(SampleTypeWrap, input.tex);     float4 color2 = shaderTextures[1].Sample(SampleTypeWrap, input.tex);     float4 alphaValue = shaderTextures[3].Sample(SampleTypeWrap, input.tex);     textureColor = saturate((alphaValue * color1) + ((1.0f - alphaValue) * color2));     // Combine the light and texture color.     float4 finalColor = lightColor * textureColor;     /////// TRANSPARENCY /////////     //finalColor.a = 0.2f;     return finalColor; }  
  • Popular Now