csgoGlow
csgoGlow copied to clipboard
iseekwonderful
New Glowindex?
Hi, guys. With the new operation update (today), the glow doesn't work anymore. We need an update of the glowindex (I guess), as usual. Can someone do it?
Haven't had a chance to test it out though but here are the latest offsets -
m_iGlowIndex = 0xA438;
m_iHealth = 0x100;
m_iTeamNum = 0xF4;
@Fmostkill @inderpartap
uint64_t m_iGlowIndex =0xAD68; uint64_t m_iHealth =0x138; uint64_t m_iTeam =0x12C;
I've updated my fork of this project: https://github.com/Fricker95/csgoGlow
@inderpartap I didn't use a dumper this time, I used an iterative process I described in #291. I normally use https://github.com/mxwll1/GO-SX-Internal-Lite as a "dumper".
The hazedumper provides the windows offsets if I'm not mistaken
@inderpartap I didn't use a dumper this time, I used an iterative process I described in #291. I normally use https://github.com/mxwll1/GO-SX-Internal-Lite
Got it. Thanks for the help! I'll be trying out your fork of the project today. 😁
the hazedumper provides the windows offsets if I'm not mistaken
Oh I did not know that 😅
@Fricker95 I realize you are trying to make it possible to programatically get the offsets but how exactly does it work and will I get banned if I run it with that code in the cheat?
@jakobe15 By default if you compile Wall as is, you should be fine since the getglowindexoffset function is turned off by default. I recommend only using that function when you need to find the new offset, since you will need to launch the game with the flag -insecure, because you potentially could get banned if you run that function in a vac server. Follow the comments at the top of the function. The function only outputs the new offset then terminates. Then update the code with the new offset and then comment out the function call line.
As for how it works, i am attempting to identify a valid glowindex (*int) with a valid value in range. And if you read the code, its a basic implementation of the process i described in #291.
So to be clear this is not a valid way to find a new offsets, i found that it worked for this offset but it might not work for the next. I will test it out when a new offset comes out.
Ps. Never run code you do not understand on a vac server
Also i have implemented an anti flash in my fork, any flash value above 100 with be set to 100 so you can see that you got flashed but it doesn't blind you. Failing to acknowledge the fact that your are fully blind might get you overwatch banned. You can always disable it by commenting out the proper lines after the // Anti-flash comment.
@Fricker95 i see the instructions but it isn’t very clear to me how exactly the function is supposed to be enabled once you launch csgo with the -insecure and get into a bot game unless it is automatically enabled if i do launch csgo with -insecure. When I tried running the program in the menu it comes back with segmentation fault: 11
@jakobe15 I updated my fork btw. With the updated fork compiled...
You need to:
- launch the game with -insecure flag
- start a game with bots
- open terminal
- run
sudo -s - run
./Wall -o
the Wall program will terminate when it has found the new offset & display it in the console.
once done:
- copy the new offset from the console into the Offsets.hpp file
- recompile Wall
- quit csgo
- delete -insecure flag
- open csgo
- open terminal
- run
sudo -s - run
./Wall
Note that you should only use the -o flag when you need the new offset. To test try to put m_iGlowIndex to 0xAD48 (previous offset) in Offsets.hpp and see if in the console it returns 0xAD68 using ./Wall -o
ps: just fixed a the seg fault bug just updated the fork
@Fricker95 Thank you! I understand it now and I tested it out and it came out with the right offset. I realized the antiflash isn’t working properly though but everything else works flawlessly.
@jakobe15 the offsets were not adjusted. I've updated the fork.
I also added a variable maxFlash = 100.0f to simplify adjusting the value.
I manually set the cap to 100 so when you get flashed it limits the flash saturation, so you still get flashed just a lot less. Feel free to play around with that value, I've seen value upwards of 2700. If you don't want to be flashed at all, set maxFlash to 0.0f.
Hello there, I have been trying to make sense of what you guys are saying but I am clueless! Is there any chance any of you guys can add me on discord and give me a hand? There is also another thing I wanted to try with Xcode but I’m not sure how. My discord is: ~Diego~#5869 . I would really really appreciate any help! Hope to hear from you soon!
@DeChosenWan i added you on discord (arsenic). what exactly did you need clarity on?
Hey again mate, I’ve not received your friend request. It’s “ ~Diego~#5869 “ or send me yours and I’ll add :) see you soon!
Regards,
Diego Carreno
On 15 Jun 2020, at 01:03, jakobe15 [email protected] wrote:
@DeChosenWanhttps://github.com/DeChosenWan i added you on discord (arsenic). what exactly did you need clarity on?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/iseekwonderful/csgoGlow/issues/299#issuecomment-643834223, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP6IXIFRJMQZLBJUBTSONQDRWVJNBANCNFSM4N27FSVQ.
@Fricker95 hello i'm using your fork but I am getting a lot of additional lag compared to the original glow. Is there any stuff that I/you could do to fix this and minimise the amount of stuff thats running so I can get a smoother gameplay? For example, I wouldn't need the blue team glow - so I only want the green glow of the enemies.
I have basically no experience with this coding so I wouldn't know what to delete from the code to get what I want
@Fricker95 i changed the functions and it came up with a bunch of errors then when i fixed the errors the glow wasnt working altogether
@useking @jakobe15
updated the fork you can use:
sudo -s
./Wall [-f <max flash alpha>] [-r <refresh rate>] [-t] [-o] [-h]
-f <flash alpha> : Antiflash alpha max amount (default: 100.0, disable: -1, range: [0-2700])
-r <refresh rate> : Refresh rate in microseconds (default: 1000.0)
-t : Disables teammate glow
-o : Get new offsets (only use with -insecure launch option flag in CSGO)
-h : Display this message
@useking you could use ./Wall -f -1 -r 3000 -t
if the lag persists lmk
@Acew0t
assuming your on macOS 64 bit, you probably changed a compiler flag. Try redownloading it
@Fricker95 i just updated to your most recent fork and it seems to be crashing alot whenever i get ingame
@jakobe15 thanks for letting me know! I totally forgot to create a branch when I was testing out some stuff and it messed up everything. I just updated it again, lmk if it still has issues
@Fricker95 No problem! Glad to be of help and I’ll check if the problem persists the next time I try.
Added weapons / utility / bomb / chicken glow. lmk if you there are issues..
sudo ./Wall [-f <max flash alpha>] [-r <refresh rate>] [-t] [-u] [-o] [-h]
-f <flash alpha> : Antiflash alpha max amount (default: 100.0, disable: -1, range: [0-2700])
-r <refresh rate> : Refresh rate in microseconds (default: 1000.0)
-t : Disables teammate glow
-u : Disables weapons/utility/bomb/chicken glow
-o : Get new offsets (only use with -insecure launch option flag in CSGO)
-h : Display this message
I will implement at some point getting class ids to change colors independently.
Is anyone having issues running CSGO on Big Sur? For me, it's stuttering a lot if I go into a public server. And if I turn on the walls, it just gets unplayable. Not sure if it's just me.
@inderpartap Yes Big Sur is known to have lowered fps, there has been a patch since the first release of Big Sur but its still not as good as Catalina. Anyways, I updated my fork where it should take less cpu usage.