• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0

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

6 posts in this topic

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]http://public.gamedev.net//public/style_emoticons/default/smile.png[/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]http://public.gamedev.net//public/style_emoticons/default/cool.png[/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]http://public.gamedev.net//public/style_emoticons/default/biggrin.png[/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]http://public.gamedev.net//public/style_emoticons/default/biggrin.png[/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]http://public.gamedev.net//public/style_emoticons/default/cool.png[/img]

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Similar Content

    • By bowerbirdcn
      hi, guys, how to understand the math used in CDXUTDirectionWidget ::UpdateLightDir 
      the  following code snippet is taken from MS DXTU source code
        D3DXMATRIX mInvView;
          D3DXMatrixInverse( &mInvView, NULL, &m_mView );
          mInvView._41 = mInvView._42 = mInvView._43 = 0;
          D3DXMATRIX mLastRotInv;
          D3DXMatrixInverse( &mLastRotInv, NULL, &m_mRotSnapshot );
          D3DXMATRIX mRot = *m_ArcBall.GetRotationMatrix();
          m_mRotSnapshot = mRot;
          // Accumulate the delta of the arcball's rotation in view space.
          // Note that per-frame delta rotations could be problematic over long periods of time.
          m_mRot *= m_mView * mLastRotInv * mRot * mInvView;
          // Since we're accumulating delta rotations, we need to orthonormalize 
          // the matrix to prevent eventual matrix skew
          D3DXVECTOR3* pXBasis = ( D3DXVECTOR3* )&m_mRot._11;
          D3DXVECTOR3* pYBasis = ( D3DXVECTOR3* )&m_mRot._21;
          D3DXVECTOR3* pZBasis = ( D3DXVECTOR3* )&m_mRot._31;
          D3DXVec3Normalize( pXBasis, pXBasis );
          D3DXVec3Cross( pYBasis, pZBasis, pXBasis );
          D3DXVec3Normalize( pYBasis, pYBasis );
          D3DXVec3Cross( pZBasis, pXBasis, pYBasis );
    • By YixunLiu
      I have a surface mesh and I want to use a cone to cut a hole on the surface mesh.
      Anybody know a fast method to calculate the intersected boundary of these two geometries?
    • By hiya83
      Hi, I tried searching for this but either I failed or couldn't find anything. I know there's D11/D12 interop and there are extensions for GL/D11 (though not very efficient). I was wondering if there's any Vulkan/D11 or Vulkan/D12 interop?
    • By lonewolff
      Hi Guys,
      I am just wondering if it is possible to acquire the address of the backbuffer if an API (based on DX11) only exposes the 'device' and 'context' pointers?
      Any advice would be greatly appreciated
    • By MarcusAseth
      bool InitDirect3D::Init() { if (!D3DApp::Init()) { return false; } //Additional Initialization //Disable Alt+Enter Fullscreen Toggle shortkey IDXGIFactory* factory; CreateDXGIFactory(__uuidof(IDXGIFactory), reinterpret_cast<void**>(&factory)); factory->MakeWindowAssociation(mhWindow, DXGI_MWA_NO_WINDOW_CHANGES); factory->Release(); return true; }  
      As stated on the title and displayed on the code above, regardless of it Alt+Enter still takes effect...
      I recall something from the book during the swapChain creation, where in order to create it one has to use the same factory used to create the ID3D11Device, therefore I tested and indeed using that same factory indeed it work.
      How is that one particular factory related to my window and how come the MakeWindowAssociation won't take effect with a newly created factory?
      Also what's even the point of being able to create this Factories if they won't work,?(except from that one associated with the ID3D11Device) 
  • Popular Now