Release Background Sight Range

[SubZero**]

Today I am gonna release offset for the sight range

Offset :

0x00de34c0

if you gonna use lib

void PatchFloat(int addr, float value)
{
	DWORD dwProtect;

	if (!VirtualProtect((LPVOID)addr, sizeof(float), PAGE_EXECUTE_READWRITE, &dwProtect))
	{
		perror("Failed to unprotect memory\n");
		return;
	}

	//*((float*)addr) = value;
	*reinterpret_cast<float*>(addr) = value;

	DWORD otherProtect;
	if (!VirtualProtect((LPVOID)addr, sizeof(float), dwProtect, &otherProtect)) {
		perror("Failed to restore protection on memory");
	}
}

How to use?

PatchFloat(0x00de34c0, 10000);//org value is 3500

[jamaldoc88]

Lol nice release, I guess ryaneichner had enough of selling that xD
Question: this address patches the background sight range 2 value, how about background sight range 5, do you know the address for that ?

[SubZero**]

Originally Posted by jamaldoc88

Lol nice release, I guess ryaneichner had enough of selling that xD
Question: this address patches the background sight range 2 value, how about background sight range 5, do you know the address for that ?

You can check FUN_00a194a0 for the others cases.

[ƛssman]

Hey everyone,

sorry for reviving this old topic, but I feel like this can save you some hours of work if you run into the same problem. I've been using an increased sight range and found out that it can lead into visual bugs where objects are displayed at areas where they shouldn't be. At first I thought this was because of a ****** up Map.pk2/Data.pk2 but the error persisted even when using a clean Map and Data. However, the error disappeared when I used a client without patched background sight range.

Here's what this bug looks like, for a better understanding what I'm talking about.

 Spoiler

I did use a background sight range of 10000, not sure if there's any threshold at which this bug appears.