Basic chams Tut (Any renderer)

[U]I take No credits in this

Credits go to s0Biot

Any way here it is I take credits for finding and posting.

Ok, in this tutorial i will be explaining the basic concept behind chams, how they work, why they work and how this can be done easily in other renderers, but i will be using D3D9 as an example.

The term "chams" is short for "chameleon colors", which basically (you guessed it) changes the color of the model being rendered, but not just simple changes it, that would be a skinhack, the trick to chams is that the model is rendered one way behind the wall, and one way in front of the wall.

This can be a change in colors, wireframe, or whatever effects you want behind/in front of the wall.

The factor that controls the visibility (or pseudo-visibility) is a value called the Z-Buffer

n computer graphics, z-buffering is the management of image depth coordinates in three-dimensional (3-D) graphics, usually done in hardware, sometimes in software. It is one solution to the visibility problem, which is the problem of deciding which elements of a rendered scene are visible, and which are hidden. The painter's algorithm is another common solution which, though less efficient, can also handle non-opaque scene elements. Z-buffering is also known as depth buffering.

or this concept to work at all, one model has to be rendered behind the wall, this can be achieved by bringing your model to the top of the Z-Order, the Z-Order traditionally used to describe 2-Dimensional elements in this case describes the dilemma quite well

Our model is not on the top of the Z-Order, therefore, is not visible
what you see instead is a wall, the engine you use depends on how you do it exactly, but usually you can control the "flow" of the z-buffer for your current model in the model rendering function, once the z-buffer value is edited it is usually re-cached each frame, so you only need not apply the "hack" that frame to "stop" the chams

Once your model is on top, what you have is a simple wallhack, easy but it is not chams that is for certain.

You want to have two colors for the model, one behind and one in front
this can not be achieved without redrawing the model

in OpenGL the function to draw models is "glDrawElements", in d3d8/d3d9 the function is "DrawIndexedPrimitive" and in Source engine, the function is "DrawModelEx/DrawModelExecute"

to disable the "depth test" or bring your model to the top of the "z-order",
in OpenGL the function is "glDisable(GL_DEPTH_TEST)", in DirectX it is "g_pGlobalDevice->SetRenderState( D3DRS_ZENABLE, FALSE )" or "g_pGlobalDevice->SetRenderState( D3DRS_ZFUNC, D3DCMP_NEVER )",
i won't go into detail much about the Source engine because it involves a lot of explanation.

whatever the renderer is, the same idea still applies to all of them

To complete the chams, you need one model being drawn without a Z-buffer, and one drawn with one enabled.

this serves two purposes, you can edit the color of the model behind the wall and in front, and because you rendered the model in front of the wall after you rendered the "wallhacked" model, the model rendered after gets rendered over the wallhack model, and since it has a depth-test you will have effectively drawn one model of one color behind the wall, and another in front of the wall with a (hopefully) separate color.

now that the explanation is out of the way, here is the basic concept.

[PHP]int __cdecl Hooked_DrawModel( ... )
{
if( IsPlayer( ... ) )
{
//disable z-buffer checking
//color model blue

Original_DrawModel( ... );

//enable the z-buffer
//color model red
}

return Original_DrawModel( ... );
} [/PHP]

i have made chams for many games, but the same method still applies.

here is some other examples, in other renderers (which are not imaginary) which may help you

[PHP]void new_glDrawElements( GLenum mode, GLsizei count, GLenum type, const GLvoid *indicies )
{
if( _ReturnAddress() == 0x123456 )
{
glDisable( GL_DEPTH_TEST );
glDisable( GL_TEXTURE_2D );
glColorPointer( 4, GL_UNSIGNED_BYTE, 0, &green );
Original_glDrawElements( mode, count, type, indicies );
glEnable( GL_DEPTH_TEST );
glColorPointer( 4, GL_UNSIGNED_BYTE, 0, &blue );
}

Original_glDrawElements( mode, count, type, indicies );[/PHP]

[PHP]int __stdcall new_DrawIndexedPrimitive( IDirect3DDevice9 *pDevice, D3DPRIMITIVETYPE Type, INT BaseVertexIndex, UINT MinVertexIndex, UINT NumVertices, UINT startIndex, UINT primCount )
{
if( UC_IS_MARINE || UC_IS_REDARMY )
{
g_pGlobalDevice->SetTexture( 0, NULL );
g_pGlobalDevice->SetPixelShader( g_pBackAllied );
g_pGlobalDevice->SetRenderState( D3DRS_ZENABLE, FALSE );
g_pGlobalDevice->SetRenderState( D3DRS_ZFUNC, D3DCMP_NEVER );

pDrawIndexedPrimitive( pDevice, Type, BaseVertexIndex, MinVertexIndex, NumVertices, startIndex, primCount );

g_pGlobalDevice->SetRenderState( D3DRS_ZENABLE, dwOldZEnable );
g_pGlobalDevice->SetRenderState( D3DRS_ZFUNC, dwOldZFunc );
g_pGlobalDevice->SetPixelShader( g_pFrontAllied );
}

return pDrawIndexedPrimitive( pDevice, Type, BaseVertexIndex, MinVertexIndex, NumVertices, startIndex, primCount );
}[/PHP]

Nice tut.
Not to easy for the average choob.
But very helpful for any D3D coder.
GJ.

nice man, but i found an easier way

Boxes are much more easier. Don't forget about nametags and other esp stuff. But thnx anyway, no boxes for A.V.A , this helped me with that. VERY GJ, +Rep.

Nice, even if im not very good in D3D code im still a choob making some basic injector

I must not be an average choob cause this is very confusing!! Someone help?
Omg you're the one who stole my pic thegreatn00b!!!

Originally Posted by Deadlocked007

I must not be an average choob cause this is very confusing!! Someone help?
Omg you're the one who stole my pic thegreatn00b!!!

You have to write a function telling you the model is more important than a building. Simple.

As in, it chooses to render the character instead of the building, letting you see the character...

And cant this be used to color the 'behind something' into..say red..while leaving the 'shootable, killable marine' the normal texture? green, red..it hurts my eyes XD

NICE! thanks

You guys do know, he didn't write this.. right?

Its ******'s thread on it. And theres more to chams then just that code.

EDIT: Lol, it got bleeped.

FML.
I'm such a choob, I don't understand it.
This'll take a while for me to understand it, so I'll try making hacks later.

What format will we save this.. and how will we make it a .dll?

Originally Posted by CAFlames

What format will we save this.. and how will we make it a .dll?

It's quite simple actually.

Open up Notepad or Notepad++, copy and paste the code. Next hit save and save as a .txt. Then you open up an injector and inject it with any other hack.dll and you have chams!

Originally Posted by Crash

It's quite simple actually.

Open up Notepad or Notepad++, copy and paste the code. Next hit save and save as a .txt. Then you open up an injector and inject it with any other hack.dll and you have chams!

If it was only that simple D:

Originally Posted by CAFlames

What format will we save this.. and how will we make it a .dll?

I thought it would be that simple once, but you have to understand this is a VERY generic overview of chams. It is not specific to CA or any game. It does not tell you how models are drawn and how to specify which models are drawn. I think a lot of that deals with getting structures out or memory, but I wouldn't know for sure. However the basic concept is there. So what he's saying is learn more about some of these functions on your own, and what you need to use them, then you can apply this technique. It looked like one of his examples were for OpenGL too, so you see it was very generic, but meant to convey a concept. C&P'in does not a hack make. ;l

Umm... what program am i supposed to use.. lmao im a super noob

Basic chams Tut (Any renderer)

Similar Threads

Tags for this Thread