• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By Jiraya
      For a 2D game, does using a float2 for position increases performance in any way?
      I know that in the end the vertex shader will have to return a float4 anyway, but does using a float2 decreases the amount of data that will have to be sent from the CPU to the GPU?
       
    • By ucfchuck
      I am feeding in 16 bit unsigned integer data to process in a compute shader and i need to get a standard deviation.
      So I read in a series of samples and push them into float arrays
      float vals1[9], vals2[9], vals3[9], vals4[9]; int x = 0,y=0; for ( x = 0; x < 3; x++) { for (y = 0; y < 3; y++) { vals1[3 * x + y] = (float) (asuint(Input1[threadID.xy + int2(x - 1, y - 1)].x)); vals2[3 * x + y] = (float) (asuint(Input2[threadID.xy + int2(x - 1, y - 1)].x)); vals3[3 * x + y] = (float) (asuint(Input3[threadID.xy + int2(x - 1, y - 1)].x)); vals4[3 * x + y] = (float) (asuint(Input4[threadID.xy + int2(x - 1, y - 1)].x)); } } I can send these values out directly and the data is as expected

                             
      Output1[threadID.xy] = (uint) (vals1[4] ); Output2[threadID.xy] = (uint) (vals2[4] ); Output3[threadID.xy] = (uint) (vals3[4] ); Output4[threadID.xy] = (uint) (vals4[4] ); however if i do anything to that data it is destroyed.
      If i add a
      vals1[4] = vals1[4]/2; 
      or a
      vals1[4] = vals[1]-vals[4];
      the data is gone and everything comes back 0.
       
       
      How does one go about converting a uint to a float and performing operations on it and then converting back to a rounded uint?
    • By fs1
      I have been trying to see how the ID3DInclude, and how its methods Open and Close work.
      I would like to add a custom path for the D3DCompile function to search for some of my includes.
      I have not found any working example. Could someone point me on how to implement these functions? I would like D3DCompile to look at a custom C:\Folder path for some of the include files.
      Thanks
    • By stale
      I'm continuing to learn more about terrain rendering, and so far I've managed to load in a heightmap and render it as a tessellated wireframe (following Frank Luna's DX11 book). However, I'm getting some really weird behavior where a large section of the wireframe is being rendered with a yellow color, even though my pixel shader is hard coded to output white. 

      The parts of the mesh that are discolored changes as well, as pictured below (mesh is being clipped by far plane).

      Here is my pixel shader. As mentioned, I simply hard code it to output white:
      float PS(DOUT pin) : SV_Target { return float4(1.0f, 1.0f, 1.0f, 1.0f); } I'm completely lost on what could be causing this, so any help in the right direction would be greatly appreciated. If I can help by providing more information please let me know.
    • By evelyn4you
      Hello,
      i try to implement voxel cone tracing in my game engine.
      I have read many publications about this, but some crucial portions are still not clear to me.
      At first step i try to emplement the easiest "poor mans" method
      a.  my test scene "Sponza Atrium" is voxelized completetly in a static voxel grid 128^3 ( structured buffer contains albedo)
      b. i dont care about "conservative rasterization" and dont use any sparse voxel access structure
      c. every voxel does have the same color for every side ( top, bottom, front .. )
      d.  one directional light injects light to the voxels ( another stuctured buffer )
      I will try to say what i think is correct ( please correct me )
      GI lighting a given vertecie  in a ideal method
      A.  we would shoot many ( e.g. 1000 ) rays in the half hemisphere which is oriented according to the normal of that vertecie
      B.  we would take into account every occluder ( which is very much work load) and sample the color from the hit point.
      C. according to the angle between ray and the vertecie normal we would weigth ( cosin ) the color and sum up all samples and devide by the count of rays
      Voxel GI lighting
      In priciple we want to do the same thing with our voxel structure.
      Even if we would know where the correct hit points of the vertecie are we would have the task to calculate the weighted sum of many voxels.
      Saving time for weighted summing up of colors of each voxel
      To save the time for weighted summing up of colors of each voxel we build bricks or clusters.
      Every 8 neigbour voxels make a "cluster voxel" of level 1, ( this is done recursively for many levels ).
      The color of a side of a "cluster voxel" is the average of the colors of the four containing voxels sides with the same orientation.

      After having done this we can sample the far away parts just by sampling the coresponding "cluster voxel with the coresponding level" and get the summed up color.
      Actually this process is done be mip mapping a texture that contains the colors of the voxels which places the color of the neighbouring voxels also near by in the texture.
      Cone tracing, howto ??
      Here my understanding is confus ?? How is the voxel structure efficiently traced.
      I simply cannot understand how the occlusion problem is fastly solved so that we know which single voxel or "cluster voxel" of which level we have to sample.
      Supposed,  i am in a dark room that is filled with many boxes of different kind of sizes an i have a pocket lamp e.g. with a pyramid formed light cone
      - i would see some single voxels near or far
      - i would also see many different kind of boxes "clustered voxels" of different sizes which are partly occluded
      How do i make a weighted sum of this ligting area ??
      e.g. if i want to sample a "clustered voxel level 4" i have to take into account how much per cent of the area of this "clustered voxel" is occluded.
      Please be patient with me, i really try to understand but maybe i need some more explanation than others
      best regards evelyn
       
       
  • Advertisement
  • Advertisement
Sign in to follow this  

DX11 Loading images in DirectX 11 to use as textures and sprites

This topic is 818 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

So I'm working on an Indie project for my startup and I am working on the graphics system for the game.  I'm trying to get textures loaded and displayed on the screen but with the removal of the d3dx11.h header and all of the useful stuff that it brought with it I'm forced to figure out another way to load images into textures.  I have looked into DirectXTK as a possibility but I would really like to learn how to do this stuff on my own.  The problem I'm running into is figuring out how to load various image file formats into memory to place into a ID3D11Texture2D.  Does anybody know of any good resource material on the topic?  I've been reading a lot of different sites about the topic and half of them talk about the old d3dx11 header and everything in there, and the other half just talks about using DirectXTK.

 

In case the question comes up the reason why I'm trying to stick with DirectX 11 for this project is that we are hoping to get approved in the next few months to also develop this project on XBOXONE so I wanted to stick to an API that will work on both PC and console.

 

Any help on this topic would be greatly appreciated and if you need more info please let me know.

Share this post


Link to post
Share on other sites
Advertisement
You can use directxtex, a loader that can load dds and other graphics files or you can use WIC. WIC is windows own image loading library which is pluggable, so if windows can load that format so can you if you use WIC.

In one of my games I used WIC to load sprites and textures from png files.

This isn't the most efficient way to do it and you're better off converting to dds or a format that closely matches the memory format of the image as part of your build process as this means less parsing to load assets, but png is friendly to modding so that's why I chose it.

Have fun!

Share this post


Link to post
Share on other sites

You can use directxtex, a loader that can load dds and other graphics files or you can use WIC. WIC is windows own image loading library which is pluggable, so if windows can load that format so can you if you use WIC.

In one of my games I used WIC to load sprites and textures from png files.

This isn't the most efficient way to do it and you're better off converting to dds or a format that closely matches the memory format of the image as part of your build process as this means less parsing to load assets, but png is friendly to modding so that's why I chose it.

Have fun!


I've used WIC successfully as well. Its not 'optimal' but still a solid route, and very easy I might add.

Share this post


Link to post
Share on other sites

The link to ChuckW's blog post above is terribly out of date, I'm afraid. What you actually want is this:

http://blogs.msdn.com/b/chuckw/archive/2015/08/05/where-is-the-directx-sdk-2015-edition.aspx

Which leads to DirectXTex:

https://github.com/Microsoft/DirectXTex

Which is a wonderfully simple library to use. Copy WICTextureLoader and DDSTextureLoader into your codebase and enjoy single function call texture loading.

 

P.S. Call CoInitialize near the beginning of your main function, or WIC won't work.

Edited by Promit

Share this post


Link to post
Share on other sites

Wow I thank everybody for the responses and when I said various image formats I was simply unsure what I was going to use, I am probably going to use DDS for my textures but I wasn't 100% certain.  The more I research things the more unsure I am about what I want to do.  I have read more about DirectXTK and do see a major benefit to its use in a project with it being supported on PC and Console.

 

The part that I'm trying to wrap my head around is that from what I can tell you don't get any control over resource management and memory management with using it.  I'm just trying to figure out if it will be a problem or not.  I was using a system for resource management that uses a template class with a stack used to hold the actual resources.  I use a different resource manager for each type of Resource.

 

I'm not opposed to changing this system or other parts of my code to make it better and more robust I'm just trying to make sure I'm making the correct choice.  The game that my company is trying to release is going to be a platformer mainly side scrolling with some in and out of the screen movement if that makes sense.  It will be similar to Mega Man style in the sense that you will go to a "world" in the game world that it will load and the player can explore that section of the map.

Share this post


Link to post
Share on other sites

resource management and memory management

 

If you use the DirectXTex library you need to be cool with COM (you're already using dx right?) and WIC calls. If that's a deal breaker you can roll your own dds loader, WIC is only really useful for loading more complex formats like jpeg or png. The downside to dds files is simply that they're large and don't trivially compress that great but I doubt this is a pressing matter for you.

Edited by Dingleberry

Share this post


Link to post
Share on other sites

Thanks for the response again and I have decided to use the DirectXTK in my project and I'm learning how to make its various systems work in my engine.  I am very happy to say that I am making some great progress in making my game.  The more I looked into the resource management of DirectXTK I like it.

 

Thanks for everybody's help deciding what to do.

Share this post


Link to post
Share on other sites

resource management and memory management


If you use the DirectXTex library you need to be cool with COM (you're already using dx right?) and WIC calls. If that's a deal breaker you can roll your own dds loader, WIC is only really useful for loading more complex formats like jpeg or png. The downside to dds files is simply that they're large and don't trivially compress that great but I doubt this is a pressing matter for you.
DDS textures will compress quite nicely if you use the right compression format for the textures. What's more, most graphics cards these days support the compression formats natively and all are supported by directx , so you send the card compressed texture data and if decompresses it on the fly for you, saving graphics ram and processing time. There are many options for compressing dds textures, some lossy and some not, some supporting alpha channels of varied depths and some not, both affect the compression ratio.

Check it out, you'll be glad you did, I could use it to get a dds down from several megs to about the same size as a 24 bit compressed png for equal dimensions of image file (1024x1024)... It's well worth it...

Share this post


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

  • Advertisement