Profiler, on September 22, 2011 - 01:57 PM, said:
As I said, it's a mapping bug in Marakkesh and Oasis and can be fixed with 'mapping'. You believe or not it's not my concern at all. I am not going to argue on the same topic again and again with the guy who doesn't know basic in PC. You don't even know 1GB RAM = 512MB + 512MB and on top now you are comparing mapping bugs to wallhacking.
PB doesn't scan any 'files' aka opengl as you claim.
GPU drivers take over openGL support.
Oasis tunnel bug is mapping bug and can be fixed with mapping.
PB doesn't scan any 'files' aka opengl as you claim.
GPU drivers take over openGL support.
Oasis tunnel bug is mapping bug and can be fixed with mapping.
Its not just marakkesh or oasis...its every map. I have been blown up into walls in goldrush (other maps too) and I've been able to see through the back sides of walls/polygon faces i'm in because only one side is rendered. as i said before:
ibblecabibble, on September 21, 2011 - 12:42 PM, said:
Its not a bug, its called polygon face culling. In a polygon solid only the front side is visible. You can prevent opengl from rendering and processing the backside. Its called culling. To use it you must enable it by passing GL_CULL_FACE to glEnable(), then use void glCullFace(GLenum mode) to specify which face to cull. mode can be GL_FRONT, GL_BACK, or GL_FRONT_AND_BACK, culling both faces won't draw anything at all (heres your potential for WH). The default is GL_BACK.
I read this in my book Beginning OpenGL Game Progamming 2nd Edition, I have another book OpenGL Super Bible 5th edition (haven't read it all yet). This is used when you know only one side of a polygon solid (3d object) is going to be seen, this is not a bug...it saves memory and processing time from rendering textures that will not be seen. This is actually a good practice that doesn't need to be fixed, however, if you alter your opengl file you can take advantage of this to create a type of WH.
Here is a link to a forum that has several threads on how to create a wall hack by altering and compiling a opengl32.dll. Most seem to involve wrapping a opengl function with your altered function this intercepts function calls in the game and alters what you see injecting the code into your et.exe process. PB does scan for these hooks and injections to opengl32.dll file and et.exe process,so in a way you're right pb doesn't scan files unless its md5 scan. but you did say before that no hacks modify your opengl file but here there are many that do. All of these don't even use culling for wh but I'm sure that it can be done and if it can someone already has.
If your interested in how cheats work or are programmed I suggest you check around that site, it is very interesting and informative. I'm actually taking a look at the assembly code tutorials, its a low level programming language that gets you closer to the manipulation of the hardware in your computer, much more interesting then just lists and lists of functions and their parameters.
I'm learning opengl for fun to make graphics, vids, and maps. I'm also trying to learn geometric algebra so I can link it with opengl and create a graphics process that doesn't have to use matrix math/linear algebra to translate an objects position through the 3d environment. I'll have to find out more about ET, but if it doesn't use this or only limited use, then I might be able to make a mod that can help our fps and also that lag that occurs every time a bunch of air strikes are thrown, especially on open sky maps.
btw its actually a common misconception that 1 gb is 1000 mb, it really is its just that, but since a byte is 8 bits and not 10 that leads to the confusion down the line.
remaining relatively humble and unrelatively flawed (hay thats what gives us character) yours untruly,
ibble
p.s. nikola tesla I found out to my delighted surprise also wrote some of his calculations for "free energy" device construction in a paper that uses geometric algebra...and i just bought the book for graphics lol















