Hi guys :)
Currently, my so called "game" is using 2D sprites, and every image is outside the exe, not inside.
My question is, should I include the images into the exe or should I keep them as seperate files
I am mostly talking about performance if there would be a great loss of performance in this or what...
Sincerely:
Include images and sprite inside exe or not?
Hot Topic
- Maximum primitivecount
- Should I share one VertexBuffer for multiple objects of the same type?
- DirectX or Managed DirectX ?
- Device.VertexDeclaration returns always null (.Net 2.0)
- DirectSound FullDuplex
- one vertex and 2 textures: beginner question...
- directx as math library
- Can I use PixelShaders with Sprites
- Octrees question
- Directx 9.0C issues , cant play games anymore.......
Game Technologies
- Windows Game Testing standards
- VB.NET/Direct X 3D object selection using the mouse click.
- OcclusionQuery Microsoft.DirectX.dll version 2.0.900
- Direct X application using MFC. I need to get the position of the window.
- Problem while installing Direct X 9.0c
- .x Model and duplicated vertices issue
- [MDX 2.0.0.0] How to read pixel from back-buffer (or equiv.)?
- BUG: Managed DirectX and Math.Atan()
- October 2005 DirectX SDK is available!
- Can i use .x files to render spline shape models?
Include images and sprite inside exe or not?
Pavel Sich
I assume you mean the use of resource files to get them "inside" your exe
I have to admit that I haven't tried it, but I can't think of any particularly good reason why you'd get a performance increase from doing that. The fact that the resources exist in memory may well give a marginal load-time improvement over resources on disk, but I'd imagine that'll be countered by the fact that it has to upload the entire exe from disk to memory in the first place!
The really big thing to be careful of is that large executable can lead to very slow execution. I'd hope that Windows splits the data/executable sections when it's first loaded, but without further research I can't be sure. There have been a few cases where I've achieved better optimization by producing a smaller executable than I have by having a large executable with heavy-weight code optimization. YMMV.
From a maintenance point of view it's a bad plan - if you ever intend to distribute new graphics files (e.g. a patch/upgrade) then you'd have to rebuild and redistribute the executable rather than just a few images.
hth
Jack