ESP Tutorial by sraeG
ESP Tutorial by sraeG
Introduction
Ok then. I’m taking it you’ve all seen ESP’s before? If not, here is an example of one coded by Deltron, using the method that will be described in the following article:
Image: CoD 4 ESP as coded by Deltron
The idea behind an ESP is to gain extra information about enemies, and the general way this is done within gamehacks is by overlaying a layer of text over them.
However, for people like me who can’t code in D3D or OpenGL and have no desire to waste their time learning, how can you determine where to write the text to on screen using only the in-game co-ordinates of the player/item/building that you want to tag? This is where the concept of 3d-to-2d comes in.
I will say now, those who are not very good with mathematical understandings (especially trig) or are not very proficient in their chosen language, this tutorial may not be suitable for you. Also, this tutorial requires an angle given from my Aimbot tutorial to get our angle to aim at the enemy. With that said, let’s get the basics out of the way..
Basic Understanding
The whole idea of this concept is to be able to convert in-game 3d co-ordinates into 2d screen pixel co-ordinates.
Now imagine this is you in your chosen FPS game, looking straight down at the player from above. Your player is viewing North, and there is an enemy ahead of you, and slightly to your right (North-East of you). The red partition is your field of view, i.e. if the enemy were to move further right and therefore out of this portion, he would not be visible on your screen.
The screen (the blue horizontal line) therefore contains all it’s pixels between the points where to red lines cross, and the screen moves up and down depending on the distance of the enemy. To make this easier to understand, here is a picture showing where the screen would be for 2 enemies at different distances. It is assumed that the playing resolution is 800×600, and therefore, the width of the screen is 800 pixels:
Now, let’s study this image briefly. As can be seen, the screen adjusts its position based on how far away the enemy is to us, and this in turn affects the distance of in-game co-ordinates that the 800 pixels is spread out to cover.
Both enemies are the same distance to our right in this picture. However, by estimate we can visually see that due to their distance away from us, they do not take up the same proportion of our 800 pixels. Enemy 1 takes up about 1/3 of the right hand portion of our field of view, whereas Enemy 2 takes up around 1/2. Therefore, seen as though we know that the central line is at 400 pixels (which would be directly infront of us), we can evaluate that to tag Enemy 1 we would need to write at approximately 400 + (0.33 * 400) pixels, and to tag Enemy 2 we would need to write to around 400 + (0.5 * 400) pixels in the X direction.
This can be simulated quite easy in real-life by putting two items infront of you, for example beer bottles. Put them directly infront of you, but one further away than the other. Now take a step to your left but keep looking straight forawrd. As can be predicted, you can see them both still though they are different angles.. the 1 further away is nearer to your viewing angle, and so would need less of a head-turn to look at.
Hopefully you have understood this concept so far, if not, leave me comments or something. If you have, carry on reading.
Expanding the Principle
Ok, so let’s take a look at that above picture again with the 2 enemies. We know that by looking at this diagram, we can roughly guess the pixels, but how does this help? Let’s alter the picture slightly :
Ok, so now with the inclusion of a grid (which will simulate our in-game co-ordinates on an exagerated scale), we can see things abit easier.
What we can gather from this grid is that, if our enemy was 4 Game Co-ordinate units away from us, our screen of 800 pixels would cover roughly 10 Game Co-ordinates. That said, we can see that half of our screen would be 5 Game Co-ordinate unites, equating to 400 pixels. Now looking at the enemy, we know he is roughly 2 co-ord units to our right, meaning to tag him we would have to write our text to an X pixel co-ord of 400 + ((2/5)*400). Remeber, this first 400 is added as he is past the half way point.
To make this more universally acceptible, we can say that if our enemy is to our right, he is:
(ScreenXResolution / 2) + ((EnemyCoordUnits / FOVCoordUnits) * ScreenXResolution / 2)
In our above example:
* ScreenXResolution = 800
* EnemyCoordUnits = 2
* FOVCorordUnits = 5
So, if we wrote our text to 400 + ((2/5)*400) which is 560 in the X direction, our text would be over our enemy (as far as horizontal is concerned, as vertical has not been accounted for).
Now, let’s apply this to our game.
Applying the Concept to a Game
From now on, so that more detail can be put in, we will assume that the enemy we are working on is located to our right and therefore I will only show this side of the central line in following diagrams. Now, check this diagram out.. explanations will follow..
Just as a pointer for people, lines are referred to by their points. For example, the line XZ is the line from us to our enemy, and the line DF is from the center point to where the FOV meets the screen. From now on, points will be referred to by their letter and lines by their point notation.
Ok then, so this diagram shows all the infromation required to get the distances we need (in this diagram, DZ and DF). So lets start off from scratch… what do we need to get from memory?
* Our players X and Z co-ordinates (not height, yet.. in this picture, Y would be either going into the screen or coming out at you)
* Enemy’s X and Z co-ordinates
* The angle that we are currently looking at
* The angle that we need to aim at to hit the enemy (gained from Aimbot tutorial)
* FOV Angle /2 - this can be done by trial and error, or some games specify it. Try 40 degrees, and work from there if in doubt
Ok then, firstly, let’s get each of the parts we need, starting with the easiest.
ANG
ANG is simply the difference between where we are looking, and where we need to look to hit the enemy. For example, say we are looking at 270 degrees and to aim at our enemy we’d need to be looking at 289, ANG = 19 degrees.
XZ
XZ is obtained using pythagoras.
A is the difference in ours and the enemy’s Z co-ords, and B is the difference in our and the enemy’s X co-ordinates. C is XZ.
For example, if we are at co-ordinate (3,4) on a map and the enemy is at (6,10) :
B = 6 - 3 = 3
A = 10 - 4 = 6
C² = 6² + 3² = 36 + 9 = 45
C =?45 = ~6.7 = XZ
Note: Remember that A and B in this diagram are NOT XD and DF on the previous diagram. This would only be true if we were facing directly north all the time.
DZ
Now that we have ANG and XZ, we can use triganometry to obtain DZ.
Sin(angle) = Opposite / Hypotenuse
Therefore, Opposite (which is DZ) = Sin(angle) * Hypotenuse
DZ = Sin(ANG) * XZ
DX
Using the above information, but a different trig will give us DX.
Cos(angle) = Adjacent / Hypotenuse
Therefore, Adjacent (which is DX) = Cos(angle) * Hypotenuse
DX = Cos(ANG) * XZ
DX is required as it is the only line that stays a constant length in both triangles XDF and XDZ. Therefore, with this side we can use trig to get DF.
DF
Again, triganometry comes into play.
Tan(angle) = Opposite / Adjacent
Therefore, Opposite = Tan(angle) * Adjacent
DF = Tan(FOV Angle/2) * DX
Using the Obtained Values
Now that we have the two essential values that we need (DZ and DF), we can apply this to the grid picture right back up top.
If the enemy is to our right, in a 800×600 resolution game, the X write value is:
400 + ((DZ/DF) * 400)
Just for example with a 640×480 resolution:
320 + ((DZ/DF) * 320)
Now, assuming that the enemy is on our left, and therefore everything is flip reversed, it should be fairly obvious to see that the X write value is:
400 - ((DZ/DF) * 400)
Final Thoughts
Now, that is the concept of converting 3d game co-ordinates into 2d pixels, applied for just the X value. The same concepts can be applied to Y value and then, by overlaying text at these co-ordinates you will have a fully working ESP
As this is just an article on the concept, no code was or will be included, and this is as far as will be explained. If you have understood the article, creating the pixel co-ord for the Y value should be no problem, but as always, leave comments if needed.
By the way, as a side note. If SetCursorPos is used on these co-ordinates, you have just successfully created an aimbot that doesn’t write any information to the game, and therefore gets past alot of anti-cheat applications.
End Note
An absolutely massive shout-out goes to Deltron who first proposed the challenge of doing this to me over MSN, which let to many hours of MSN conversations while we worked over the above method. Hopefully in the not too distanct future, we will collaborate on a full tutorial with better explanations, in-game pictures and such, and on that note could you please pass any suggestions or problems onto my by use of comments!!!
Overall, good luck, and if you plan to use this tutorial then please give credits where due, to both me (sraeG) and Deltron.
I(Hell_Demon) have nothing to do with this tutorial, all credits go to sraeG and Deltron!
If you plan on using anything from this tutorial make sure to give credit to both sraeG and Deltron!
P.S. Attached is a rar containing the page as it looked back when I took it, R.I.P. sraeG's blog.
Ok then. I’m taking it you’ve all seen ESP’s before? If not, here is an example of one coded by Deltron, using the method that will be described in the following article:
Image: CoD 4 ESP as coded by Deltron
The idea behind an ESP is to gain extra information about enemies, and the general way this is done within gamehacks is by overlaying a layer of text over them.
However, for people like me who can’t code in D3D or OpenGL and have no desire to waste their time learning, how can you determine where to write the text to on screen using only the in-game co-ordinates of the player/item/building that you want to tag? This is where the concept of 3d-to-2d comes in.
I will say now, those who are not very good with mathematical understandings (especially trig) or are not very proficient in their chosen language, this tutorial may not be suitable for you. Also, this tutorial requires an angle given from my Aimbot tutorial to get our angle to aim at the enemy. With that said, let’s get the basics out of the way..
Basic Understanding
The whole idea of this concept is to be able to convert in-game 3d co-ordinates into 2d screen pixel co-ordinates.
Now imagine this is you in your chosen FPS game, looking straight down at the player from above. Your player is viewing North, and there is an enemy ahead of you, and slightly to your right (North-East of you). The red partition is your field of view, i.e. if the enemy were to move further right and therefore out of this portion, he would not be visible on your screen.
The screen (the blue horizontal line) therefore contains all it’s pixels between the points where to red lines cross, and the screen moves up and down depending on the distance of the enemy. To make this easier to understand, here is a picture showing where the screen would be for 2 enemies at different distances. It is assumed that the playing resolution is 800×600, and therefore, the width of the screen is 800 pixels:
Now, let’s study this image briefly. As can be seen, the screen adjusts its position based on how far away the enemy is to us, and this in turn affects the distance of in-game co-ordinates that the 800 pixels is spread out to cover.
Both enemies are the same distance to our right in this picture. However, by estimate we can visually see that due to their distance away from us, they do not take up the same proportion of our 800 pixels. Enemy 1 takes up about 1/3 of the right hand portion of our field of view, whereas Enemy 2 takes up around 1/2. Therefore, seen as though we know that the central line is at 400 pixels (which would be directly infront of us), we can evaluate that to tag Enemy 1 we would need to write at approximately 400 + (0.33 * 400) pixels, and to tag Enemy 2 we would need to write to around 400 + (0.5 * 400) pixels in the X direction.
This can be simulated quite easy in real-life by putting two items infront of you, for example beer bottles. Put them directly infront of you, but one further away than the other. Now take a step to your left but keep looking straight forawrd. As can be predicted, you can see them both still though they are different angles.. the 1 further away is nearer to your viewing angle, and so would need less of a head-turn to look at.
Hopefully you have understood this concept so far, if not, leave me comments or something. If you have, carry on reading.
Expanding the Principle
Ok, so let’s take a look at that above picture again with the 2 enemies. We know that by looking at this diagram, we can roughly guess the pixels, but how does this help? Let’s alter the picture slightly :
Ok, so now with the inclusion of a grid (which will simulate our in-game co-ordinates on an exagerated scale), we can see things abit easier.
What we can gather from this grid is that, if our enemy was 4 Game Co-ordinate units away from us, our screen of 800 pixels would cover roughly 10 Game Co-ordinates. That said, we can see that half of our screen would be 5 Game Co-ordinate unites, equating to 400 pixels. Now looking at the enemy, we know he is roughly 2 co-ord units to our right, meaning to tag him we would have to write our text to an X pixel co-ord of 400 + ((2/5)*400). Remeber, this first 400 is added as he is past the half way point.
To make this more universally acceptible, we can say that if our enemy is to our right, he is:
(ScreenXResolution / 2) + ((EnemyCoordUnits / FOVCoordUnits) * ScreenXResolution / 2)
In our above example:
* ScreenXResolution = 800
* EnemyCoordUnits = 2
* FOVCorordUnits = 5
So, if we wrote our text to 400 + ((2/5)*400) which is 560 in the X direction, our text would be over our enemy (as far as horizontal is concerned, as vertical has not been accounted for).
Now, let’s apply this to our game.
Applying the Concept to a Game
From now on, so that more detail can be put in, we will assume that the enemy we are working on is located to our right and therefore I will only show this side of the central line in following diagrams. Now, check this diagram out.. explanations will follow..
Just as a pointer for people, lines are referred to by their points. For example, the line XZ is the line from us to our enemy, and the line DF is from the center point to where the FOV meets the screen. From now on, points will be referred to by their letter and lines by their point notation.
Ok then, so this diagram shows all the infromation required to get the distances we need (in this diagram, DZ and DF). So lets start off from scratch… what do we need to get from memory?
* Our players X and Z co-ordinates (not height, yet.. in this picture, Y would be either going into the screen or coming out at you)
* Enemy’s X and Z co-ordinates
* The angle that we are currently looking at
* The angle that we need to aim at to hit the enemy (gained from Aimbot tutorial)
* FOV Angle /2 - this can be done by trial and error, or some games specify it. Try 40 degrees, and work from there if in doubt
Ok then, firstly, let’s get each of the parts we need, starting with the easiest.
ANG
ANG is simply the difference between where we are looking, and where we need to look to hit the enemy. For example, say we are looking at 270 degrees and to aim at our enemy we’d need to be looking at 289, ANG = 19 degrees.
XZ
XZ is obtained using pythagoras.
A is the difference in ours and the enemy’s Z co-ords, and B is the difference in our and the enemy’s X co-ordinates. C is XZ.
For example, if we are at co-ordinate (3,4) on a map and the enemy is at (6,10) :
B = 6 - 3 = 3
A = 10 - 4 = 6
C² = 6² + 3² = 36 + 9 = 45
C =?45 = ~6.7 = XZ
Note: Remember that A and B in this diagram are NOT XD and DF on the previous diagram. This would only be true if we were facing directly north all the time.
DZ
Now that we have ANG and XZ, we can use triganometry to obtain DZ.
Sin(angle) = Opposite / Hypotenuse
Therefore, Opposite (which is DZ) = Sin(angle) * Hypotenuse
DZ = Sin(ANG) * XZ
DX
Using the above information, but a different trig will give us DX.
Cos(angle) = Adjacent / Hypotenuse
Therefore, Adjacent (which is DX) = Cos(angle) * Hypotenuse
DX = Cos(ANG) * XZ
DX is required as it is the only line that stays a constant length in both triangles XDF and XDZ. Therefore, with this side we can use trig to get DF.
DF
Again, triganometry comes into play.
Tan(angle) = Opposite / Adjacent
Therefore, Opposite = Tan(angle) * Adjacent
DF = Tan(FOV Angle/2) * DX
Using the Obtained Values
Now that we have the two essential values that we need (DZ and DF), we can apply this to the grid picture right back up top.
If the enemy is to our right, in a 800×600 resolution game, the X write value is:
400 + ((DZ/DF) * 400)
Just for example with a 640×480 resolution:
320 + ((DZ/DF) * 320)
Now, assuming that the enemy is on our left, and therefore everything is flip reversed, it should be fairly obvious to see that the X write value is:
400 - ((DZ/DF) * 400)
Final Thoughts
Now, that is the concept of converting 3d game co-ordinates into 2d pixels, applied for just the X value. The same concepts can be applied to Y value and then, by overlaying text at these co-ordinates you will have a fully working ESP
As this is just an article on the concept, no code was or will be included, and this is as far as will be explained. If you have understood the article, creating the pixel co-ord for the Y value should be no problem, but as always, leave comments if needed.By the way, as a side note. If SetCursorPos is used on these co-ordinates, you have just successfully created an aimbot that doesn’t write any information to the game, and therefore gets past alot of anti-cheat applications.
End Note
An absolutely massive shout-out goes to Deltron who first proposed the challenge of doing this to me over MSN, which let to many hours of MSN conversations while we worked over the above method. Hopefully in the not too distanct future, we will collaborate on a full tutorial with better explanations, in-game pictures and such, and on that note could you please pass any suggestions or problems onto my by use of comments!!!
Overall, good luck, and if you plan to use this tutorial then please give credits where due, to both me (sraeG) and Deltron.
I(Hell_Demon) have nothing to do with this tutorial, all credits go to sraeG and Deltron!
If you plan on using anything from this tutorial make sure to give credit to both sraeG and Deltron!
P.S. Attached is a rar containing the page as it looked back when I took it, R.I.P. sraeG's blog.
