Just found a way to do it.

int filesize = 0;

ifstream file("blabla.jpg", ios::end);

filesize = file.tellg();

if(filesize != normalfilesize)
{
file.close();

ofstream file("blabla.jpg");

file <<"Did you try to modify this file?"<<endl;

file.close();

}
else
{

cout <<"Files loaded!"<<endl;

}

I will have to use jpg to do this...jpg filesize change everytime you do one modification. example, you change an rgb color from black to red, the byte filesize will change.

So actually, modifying the file will delete all the client files...the guy will need to reinstall it.

You think this won't work? Having your game files all deleted won't work? will you keep editing the files after having reinstalled it alot of times???

I know this isn't an encryption for .x files...but it's a good security for loading image files.

I know about encryption/decryption...

It's just that i didn't know how to access the memory in direct3d to encrypt the data.

Now that i know, it will be easier for me.

+ By the way, this could add a little bit of security.

hooking your dll?...it will be worthless for the kind of game im devlopping.

I'm 15 years old by the way. So putting stuff in my head might take a bit of time.That's why i need alot of help with Direct3d...I normally work with networking / win32.

I think the question is more, Why the hell would you wanna? Surely we are talking here about purely the client meshes/textures - why not leave them unencrypted and let the players mod the textures as much as they like? That way, if the game is successful, chances are the players will make gorgeous high-res textures for you... And why do you care what their game looks like? Does it affect the gameplay of other players?

Modding games is a fact of life - some commercial studios even provide mod tools with their single player games now - and there have been MMOs that allow complete customisation of textures. Although I can't remember what it was called - it was one of the 2D manga style games.

Unfortunately there is no way to encrypt game files securely. If you use weak encryption then breaking it will be no problem. If you use strong encryption, the key is the weak point since you need the key to decrypt the game files, this must either be hardcoded in the executable or retrieved from the server before beginning gameplay. Either way, it can be read from the memory of your program.

If you desperately want to prevent casual end-user theft of your textures etc, why not just XOR-encrypt the binary files? A ridiculously weak encryption method, but it'll stop "click-and-change". Again, the haxx0rs will just decrypt, alter and encrypt again and your client will be none the wiser, but hell, saves you a lot of headaches.

Mathmo

EDIT: Of course, if you want Double-Protection(tm), you could XOR-encrypt them twice... hehehehe

I am working on an online game, with my friend who is doing the graphics.

I am working with the whole engine programming + networking.

I am having no problems with it right now.

People editing the files will actually start posting screenshots about in-game items that don't even exist...stuff like that...

But it's fine, i just know now how to read the texture data...that's all i needed to encrypt and decrypt, thank you.