Ok, i work on that. Sorry, i hoped that when i'm working whith the newest VisualStudio and Directx SDK the program will run on most Windows computer
This should only be a small techdemo, not a big program!
To handle all the errorcodes will double the code (or more). The "Windows is checking for a solution to the problem..." Dos'nt help this way. I had that popup manytimes,
but windows never find a solution!

I wasn't suggesting you handle each error code, but rather just catch whatever error is produced and display it in a window before the program closes. That way I can at least tell you what the error was.

Would they? People post textures in JPEG form often on this forum, and they seem sharp enough depending on the compression settings used.

Some games, like Second Life, use Jpeg2000 compression, which squeezes even more quality out of the same file size (or gives a smaller file for the same quality). The downside is that it's not widely adopted, and you may need to include a library that can read it.

Sorry, don't noticed this post until now. I tried out what is possible.When I use the maximum quality the result is that: ( 3 megs big)

I used the colorkey 255, 000, 255 (Magenta). As result you see colorkeying 255, 000, 254!?!. What you see in magente is 255, 000, 255 ! the rest is gone by the jpg format.It is no problem for mee to turn the magenta color into black ->no one will see the wrong pixelcolor anymore, but the collisiondetection is gone. You see the the littleplayership riding on a magenta pixel.

Again, hope you know what i mean. Its not easy for me to explain it all in english.

Ok, I see how you're doing things a bit better now. One thing to consider is if you save the magenta color key alone in a PNG, separate from the texture, you'll get much better compression. PNG is good at compressing images with large flat areas of solid color. I did a quick test and your color key saved separately as a 3000 x 3000 PNG will be in the range of about 250K (using only red channel of image). That will leave you free to use whatever compression you want on the texture part. But it's just an idea--the file size may not be a significant issue for you.

Ok, I see how you're doing things a bit better now. One thing to consider is if you save the magenta color key alone in a PNG, separate from the texture, you'll get much better compression. PNG is good at compressing images with large flat areas of solid color. I did a quick test and your color key saved separately as a 3000 x 3000 PNG will be in the range of about 250K (using only red channel of image). That will leave you free to use whatever compression you want on the texture part. But it's just an idea--the file size may not be a significant issue for you.

Either way, great work!

Thanks.Using a colorkeymask is on my list. I thought about that using it in a smaller format, maybe 1024*1024, for the collisiondetection ( The objects , or their mask ,must be scaled down the same amount too ). That should be precise anough an is not that time consuming. For now the framerate on my computer goes down from 2400 to 700 by setting the collisiondetection on. Using the power of two in the texturesize will also have benefit in this context.Furthermore i'm rewriting my directx code again and have now installed the new SDK( March 2009 ). There are two more API's wich are interesting for me ( Direct2D and DirectWrite ). A new small demo.exe ( wich will run on every computer i hope ) will come in the next week or so.

Attached Files

Thank you for sharing. I love the idea that this is procedural. It's almost like it can be made to generate game level variations entirely automatically. Not only that, but the textures look really good!.