• 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
Suen

Writing out image data

2 posts in this topic

Hello. I'm not sure if this is really the right place to ask this but here goes. I'm trying to write an image to my hard drive. Basically I allocate space for an array big enough to hold my image and then simply insert my image data in it and write it to the hard drive. Since I'm fairly new when it comes to writing code that writes out an image to the hard drive I've decided to go with a very simple approach, I just write out a raw binary file which contains my image data and then use Adobe Photoshop CSS Extended (Ver 12.1) to open it to check that the result is correct. If I want to use some image format then it requires that I provide information for the image header and more which I want to avoid doing for the moment (although depending on my problem I might have to switch to another format).

Here's the relevant code for writing out the image to my hard drive:

[CODE]
typedef unsigned char byte;

int imageWidth = 400;
int imageHeight = 400;
int imageSize = imageWidth*imageHeight;

std::fstream imageStream;

imageStream.open("image.raw", std::ios::out|std::ios::binary);

if(!imageStream.is_open())
{
std::cout << "Could not open file" << std::endl;
exit(1);
}

for(int i=0; i<imageSize; i++)
{
imageStream.put((byte)imageData[i].r); //Red channel
imageStream.put((byte)imageData[i].g); //Green channel
imageStream.put((byte)imageData[i].b); //Blue channel
}

imageStream.close();
[/CODE]

Now this works perfectly fine IF my image width and height are of the same value. In other words I need to have the same amount of pixels horizontally as I have vertically. So if I have a 400x400 image as above I get the correct image. Photoshop will ask me, before opening the file, to describe the raw file options (dimensions of image, number of color channels etc.). Normally the default options provided by the application are already correct if I have the same value in my dimensions.

Here's the thing though, if I change my dimensions to be different from each other, say changing it to 600x150, then some problems arise. The image still gets written to the hard drive but when I open it the default raw options in Photoshop suggest that the image is a 300x300 image. If I choose this my image ends up being heavily distorted. If I choose to specify the original dimension (600x150) the image show correct results but this is only because 300*300 = 600*150 = 90000 (thus same image size) So it's a special case. If I went with something more random like 250x532 then the default Photoshop raw options consider my image to be 665x600. Changing this back to 250x532 in the Photoshop raw options will only produce a result with rubbish in it as 250*532 != 665*600 (the application will warn me that I'm decreasing the size of the image which it consider to be 665*600).

Now if I change my code to this instead (writing out a .ppm file instead of a .raw file):

[CODE]
imageStream.open("image.ppm", std::ios::out|std::ios::binary);

if(!imageStream.is_open())
{
std::cout << "Could not open file" << std::endl;
exit(1);
}

imageStream << "P6\n" << imageWidth << " " << imageHeight << "\n255\n";

for(int i=0; i<imageSize; i++)
{
imageStream.put((byte)imageData[i].r); //Red channel
imageStream.put((byte)imageData[i].g); //Green channel
imageStream.put((byte)imageData[i].b); //Blue channel
}

imageStream.close();
[/CODE]

then everything works regardless of my dimensions. Photoshop won't ask anything but just open the file with the correct dimensions and correct image result.

Now I most likely think that the problem here is not the code itself but just how Photoshop internally handle .raw file (although why it change the dimensions of an image with different values for the dimensions when I try to open it is beyond me). Especially if you compare it with the .ppm format where information about the dimension of the image is provided before writing out the data and the .raw file...provide no information at all.

In the case that this is related to Photoshop then this topic probably does not even belong in this forum [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] But I just want to make sure that it's not my code which is at fault here. If it is my code then what is exactly wrong and would I change this?

Best regards Edited by Suen
0

Share this post


Link to post
Share on other sites
The raw file doesn't contain any information about the dimensions of the image, so photoshop has to try to infer them from the number of pixels in the file. The ppm file [i]does [/i]contain the image's dimensions, so photoshop doesn't have to guess.

Look more closely at the code you posted and you'll see for yourself ... [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
0

Share this post


Link to post
Share on other sites
[quote name='mrbastard' timestamp='1349987385' post='4989243']
The raw file doesn't contain any information about the dimensions of the image, so photoshop has to try to infer them from the number of pixels in the file. The ppm file [i]does [/i]contain the image's dimensions, so photoshop doesn't have to guess.

Look more closely at the code you posted and you'll see for yourself ... [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
[/quote]

Yeah, basically this is what I suspected and said above, thanks. I guess the best thing to do is to switch to .ppm format instead as it seems easy to implement. Thanks again.
0

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