TogaMario
First Post
I'm having to implement an odd system for custom tile pics. All images that get loaded need to have a size suffix added to the file name. DirectX won't load textures properly unless they're 128x128/256x256/512x512 etc etc, unless you tell it what size you want to load. The only way to automate this is having each file you want to load have the pixel size in a predetermined format. It's really kinda easy, but something that'll be required, otherwise your pics are gonna look horrible, not offset correctly, or worse (cause a crash).
For example, I have a 72x72 pixel PNG file that I've appropriately called "Cobble1", so it's full filename would be "Cobble1.png" ... to work with the system, it'll have to be renamed "Cobble1_072072.png" - The first 072 tells the system that the width is 72 pixels, the second tell it that it's 72 pixels tall. So it we have a 72x144 (or a 1 inch by 2 inch tile) we'd name the file "TilesName_072144.png" That should work well enough for everyone's purposes, unless you're making one large tile that's 14 inches (or more) in either direction.
Does anyone think that's a bit much? Or is that agreeable?
For example, I have a 72x72 pixel PNG file that I've appropriately called "Cobble1", so it's full filename would be "Cobble1.png" ... to work with the system, it'll have to be renamed "Cobble1_072072.png" - The first 072 tells the system that the width is 72 pixels, the second tell it that it's 72 pixels tall. So it we have a 72x144 (or a 1 inch by 2 inch tile) we'd name the file "TilesName_072144.png" That should work well enough for everyone's purposes, unless you're making one large tile that's 14 inches (or more) in either direction.
Does anyone think that's a bit much? Or is that agreeable?