Forums WoW Modding Resources Tools [Archive] Vanilla 1.12.1 / TBC 2.4.3 / WotLK 3.3.5a - View distance unlock (patched WoW.exe)

[Archive] Vanilla 1.12.1 / TBC 2.4.3 / WotLK 3.3.5a - View distance unlock (patched WoW.exe)

[Archive] Vanilla 1.12.1 / TBC 2.4.3 / WotLK 3.3.5a - View distance unlock (patched WoW.exe)

Pages (2): 1 2 Next
rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#1
Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: This patch unlocks the "/console farclip value" command available in all WoW clients. The farclip value is capped at 777 in Vanilla 1.12.1, at 783.333313 in TBC 2.4.3 and at 1583.333374 + 791.666687 in WotLK 3.3.5a (for WotLK/TBC and Vanilla zones respectively). Yes, the values listed here are wrong.

Let's start with some eye candy, here are a few screenshots.

TBC 2.4.3:

Farclip @783.333313 (default cap)

Farclip @1500 (patched exe)

Farclip @2000 (patched exe)

Farclip @3000 (patched exe)

Farclip @3500 (patched exe)

WotLK 3.3.5a:

Farclip @1583.333374 (default cap)

Farclip @2000 (patched exe)

Farclip @2500 (patched exe)

Farclip @3000 (patched exe)

Farclip @4000 (patched exe)

Farclip @6000 (patched exe)

Vanilla 1.12.1:

Farclip @777 (default cap)

Farclip @1500 (patched exe)

Farclip @2000 (patched exe)

Here's some info about the whole thing:
  • All executables have been patched with the LAA (Large Address Aware) flag, which I believe will help avoid some crashes at high farclip values. More info here and here.
  • Both executables from TBC and Vanilla have my FoV patch included. See this (Vanilla 1.12 & TBC 2.4.3 - Permanent FoV fix (patched WoW.exe)).
  • The higher the farclip value, the more it will affect performance (obviously).
  • If the value is set high enough WoW's graphical engine will at some point reach its limit, even with powerful hardware.
  • If the value is set too high WoW will crash.
  • The value will reach diminishing returns at some point (see Vanilla @1500 vs @2000 and TBC @3000 vs @3500).
  • How good the game will look will depend on the zone (some zones have more fog than others).
  • Vanilla seems to reach diminishing returns way faster than TBC and WotLK, I'm not sure if that's because of the older engine or if I just chose a bad zone.
  • The value is actually capped at 10000 with this patch.
Here are the downloads:

WoW.exe - Vanilla 1.12.1

WoW.exe - TBC 2.4.3

Edit: apparently WotLK had two farclip value limits in place, one for WotLK and TBC zones, and a second one for Vanilla zones. Downloads for both versions:

WoW.exe - WotLK 3.3.5a - WotLK/TBC zones

WoW.exe - WotLK 3.3.5a - WotLK/TBC + Vanilla zones

Usage: when ingame type in the chat "/console farclip 1-10000" without the quotation marks.

Virustotal scans:

WoW.exe - Vanilla 1.12.1

WoW.exe - TBC 2.4.3

WoW.exe - WotLK 3.3.5a - WotLK/TBC zones - It seems like the WotLK executable gets picked up as "malicious_confidence_65% (D)" by an antivirus on the virustotal list, this is a false positive, however you can follow the instructions on how to patch the executables yourself below if you wish.

WoW.exe - WotLK 3.3.5a - WotLK/TBC + Vanilla zones - Same as above (although this one is because the signature doesn't match since the file has been edited).

Here's some more technical info for those interested:

Code:
Vanilla 1.12 (WoW.exe+8E9B94)
Default farclip limit float value: 777
Default farclip limit hex value: 00 40 42 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

TBC 2.4.3 (WoW.exe+9A45F4)
Default farclip limit float value: 783.333313
Default farclip limit hex value: 55 D5 43 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

WotLK 3.3.5a (WoW.exe+8D7748) - farclip limit for WotLK/TBC zones
Default farclip limit float value: 1583.333374
Default farclip limit hex value: AB EA C5 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

WotLK 3.3.5a (WoW.exe+8D7748) - farclip limit for Vanilla zones
Default farclip limit float value: 791.666687
Default farclip limit hex value: AB EA 45 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

Refer to this thread for more in depth info on how I patched the executables with the new hex values.
To wrap all of this up, it would be nice to have a way to lower or remove the fog which can hide a lot of detail in some zones, but I haven't found any info on this for these expansions/patch versions yet.
rektbyfaith
11-04-2025, 12:44 PM #1

Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: This patch unlocks the "/console farclip value" command available in all WoW clients. The farclip value is capped at 777 in Vanilla 1.12.1, at 783.333313 in TBC 2.4.3 and at 1583.333374 + 791.666687 in WotLK 3.3.5a (for WotLK/TBC and Vanilla zones respectively). Yes, the values listed here are wrong.

Let's start with some eye candy, here are a few screenshots.

TBC 2.4.3:

Farclip @783.333313 (default cap)

Farclip @1500 (patched exe)

Farclip @2000 (patched exe)

Farclip @3000 (patched exe)

Farclip @3500 (patched exe)

WotLK 3.3.5a:

Farclip @1583.333374 (default cap)

Farclip @2000 (patched exe)

Farclip @2500 (patched exe)

Farclip @3000 (patched exe)

Farclip @4000 (patched exe)

Farclip @6000 (patched exe)

Vanilla 1.12.1:

Farclip @777 (default cap)

Farclip @1500 (patched exe)

Farclip @2000 (patched exe)

Here's some info about the whole thing:
  • All executables have been patched with the LAA (Large Address Aware) flag, which I believe will help avoid some crashes at high farclip values. More info here and here.
  • Both executables from TBC and Vanilla have my FoV patch included. See this (Vanilla 1.12 & TBC 2.4.3 - Permanent FoV fix (patched WoW.exe)).
  • The higher the farclip value, the more it will affect performance (obviously).
  • If the value is set high enough WoW's graphical engine will at some point reach its limit, even with powerful hardware.
  • If the value is set too high WoW will crash.
  • The value will reach diminishing returns at some point (see Vanilla @1500 vs @2000 and TBC @3000 vs @3500).
  • How good the game will look will depend on the zone (some zones have more fog than others).
  • Vanilla seems to reach diminishing returns way faster than TBC and WotLK, I'm not sure if that's because of the older engine or if I just chose a bad zone.
  • The value is actually capped at 10000 with this patch.
Here are the downloads:

WoW.exe - Vanilla 1.12.1

WoW.exe - TBC 2.4.3

Edit: apparently WotLK had two farclip value limits in place, one for WotLK and TBC zones, and a second one for Vanilla zones. Downloads for both versions:

WoW.exe - WotLK 3.3.5a - WotLK/TBC zones

WoW.exe - WotLK 3.3.5a - WotLK/TBC + Vanilla zones

Usage: when ingame type in the chat "/console farclip 1-10000" without the quotation marks.

Virustotal scans:

WoW.exe - Vanilla 1.12.1

WoW.exe - TBC 2.4.3

WoW.exe - WotLK 3.3.5a - WotLK/TBC zones - It seems like the WotLK executable gets picked up as "malicious_confidence_65% (D)" by an antivirus on the virustotal list, this is a false positive, however you can follow the instructions on how to patch the executables yourself below if you wish.

WoW.exe - WotLK 3.3.5a - WotLK/TBC + Vanilla zones - Same as above (although this one is because the signature doesn't match since the file has been edited).

Here's some more technical info for those interested:

Code:
Vanilla 1.12 (WoW.exe+8E9B94)
Default farclip limit float value: 777
Default farclip limit hex value: 00 40 42 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

TBC 2.4.3 (WoW.exe+9A45F4)
Default farclip limit float value: 783.333313
Default farclip limit hex value: 55 D5 43 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

WotLK 3.3.5a (WoW.exe+8D7748) - farclip limit for WotLK/TBC zones
Default farclip limit float value: 1583.333374
Default farclip limit hex value: AB EA C5 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

WotLK 3.3.5a (WoW.exe+8D7748) - farclip limit for Vanilla zones
Default farclip limit float value: 791.666687
Default farclip limit hex value: AB EA 45 44
Patched farclip limit float value: 10000
Patched farclip limit hex value: 00 40 1C 46

Refer to this thread for more in depth info on how I patched the executables with the new hex values.
To wrap all of this up, it would be nice to have a way to lower or remove the fog which can hide a lot of detail in some zones, but I haven't found any info on this for these expansions/patch versions yet.

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#2
Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

rektbyfaith
11-04-2025, 12:44 PM #2

Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#3
Archived author: Rocky37 • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Thank you very much for these patches !
rektbyfaith
11-04-2025, 12:44 PM #3

Archived author: Rocky37 • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Thank you very much for these patches !

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#4
Archived author: Android14 • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Is there a way to make the tbc one work with wowme for tbc?
rektbyfaith
11-04-2025, 12:44 PM #4

Archived author: Android14 • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Is there a way to make the tbc one work with wowme for tbc?

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#5
Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: I don't really know Wowme or what it does exactly to be honest, I just heard that it's used for some model edits. However, I just did a quick test and it appears that Wowme still hooks onto the original WoW.exe file, and if using my modified executable the FoV fix does appear to work with it. Are you having any specific issues?
rektbyfaith
11-04-2025, 12:44 PM #5

Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: I don't really know Wowme or what it does exactly to be honest, I just heard that it's used for some model edits. However, I just did a quick test and it appears that Wowme still hooks onto the original WoW.exe file, and if using my modified executable the FoV fix does appear to work with it. Are you having any specific issues?

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#6
Archived author: Greensiberia • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Hello! You are the man whom i've been looking for last ten years. Please tell me is it real to fix grass draw distance in vanilla wow.exe?

World of Warcraft 1.12.1 Lights Hope Grasss draw distance - YouTube
rektbyfaith
11-04-2025, 12:44 PM #6

Archived author: Greensiberia • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Hello! You are the man whom i've been looking for last ten years. Please tell me is it real to fix grass draw distance in vanilla wow.exe?

World of Warcraft 1.12.1 Lights Hope Grasss draw distance - YouTube

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#7
Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Greensiberia
[Image: lastpost-right.svg]

Please tell me is it real to fix grass draw distance in vanilla wow.exe?

It sure is, or at least I've done it in TBC. However the FPS drawbacks were huge (on a 1070 mind you, so it wasn't a hardware bottleneck), so it didn't seem to be worth releasing. I never tested it in Vanilla though, I'll look into it and let you know how it goes.

EDIT: Okay, first of all I think you have the wrong idea about the "frilldensity" console variable (which I assume is the one you're changing since it has a 256 maximum value), it only changes the density of the grass/ground clutter, not its draw distance. Well, anyway, I started looking into it and I've kinda hit a roadblock: the console variable which changes the draw distance of the grass in tbc TBC, "groundeffectdist", doesn't exist in Vanilla. According to WoWWiki the "groundeffectdist" variable which got introduced somewhere in TBC replaced "frilldistance", however "frilldistance" is nowhere to be found in Vanilla. This spreadsheet should list all console variables available in Vanilla, but I haven't found anything yet. It could be possible that there is no equivalent to "groundeffectdist" in Vanilla, and that would make changing the default grass draw distance extremely hard.

If you know the name of the console variable I'm looking for please let me know.
rektbyfaith
11-04-2025, 12:44 PM #7

Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Greensiberia
[Image: lastpost-right.svg]

Please tell me is it real to fix grass draw distance in vanilla wow.exe?

It sure is, or at least I've done it in TBC. However the FPS drawbacks were huge (on a 1070 mind you, so it wasn't a hardware bottleneck), so it didn't seem to be worth releasing. I never tested it in Vanilla though, I'll look into it and let you know how it goes.

EDIT: Okay, first of all I think you have the wrong idea about the "frilldensity" console variable (which I assume is the one you're changing since it has a 256 maximum value), it only changes the density of the grass/ground clutter, not its draw distance. Well, anyway, I started looking into it and I've kinda hit a roadblock: the console variable which changes the draw distance of the grass in tbc TBC, "groundeffectdist", doesn't exist in Vanilla. According to WoWWiki the "groundeffectdist" variable which got introduced somewhere in TBC replaced "frilldistance", however "frilldistance" is nowhere to be found in Vanilla. This spreadsheet should list all console variables available in Vanilla, but I haven't found anything yet. It could be possible that there is no equivalent to "groundeffectdist" in Vanilla, and that would make changing the default grass draw distance extremely hard.

If you know the name of the console variable I'm looking for please let me know.

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#8
Archived author: Greensiberia • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Nikk0z
[Image: lastpost-right.svg]

It sure is, or at least I've done it in TBC. However the FPS drawbacks were huge (on a 1070 mind you, so it wasn't a hardware bottleneck

Perhaps it is strange, but I think you were bottlenecked by your CPU, check system monitor or install MSI afterburner to see more information about system load.

Imgur: The most awesome images on the Internet

I have tried to change every setting with any "dist" command, but with no luck. Sorry about 256 frilldistance. I was wrong. I set farclip for 177 and it was nearly five times longer distance than grass draw distance, perhaps we should calculate real parameter of grass draw distance. But it is difficult because depends from camera position at current time.
[Image: paperclip.svg] Attached Thumbnails
[Image: 57319d1508727101t-vanilla-1-12-1-tbc-2-4...-23-11-gif]
rektbyfaith
11-04-2025, 12:44 PM #8

Archived author: Greensiberia • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Nikk0z
[Image: lastpost-right.svg]

It sure is, or at least I've done it in TBC. However the FPS drawbacks were huge (on a 1070 mind you, so it wasn't a hardware bottleneck

Perhaps it is strange, but I think you were bottlenecked by your CPU, check system monitor or install MSI afterburner to see more information about system load.

Imgur: The most awesome images on the Internet

I have tried to change every setting with any "dist" command, but with no luck. Sorry about 256 frilldistance. I was wrong. I set farclip for 177 and it was nearly five times longer distance than grass draw distance, perhaps we should calculate real parameter of grass draw distance. But it is difficult because depends from camera position at current time.
[Image: paperclip.svg] Attached Thumbnails
[Image: 57319d1508727101t-vanilla-1-12-1-tbc-2-4...-23-11-gif]

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#9
Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Greensiberia
[Image: lastpost-right.svg]

Perhaps it is strange, but I think you were bottlenecked by your CPU, check system monitor or install MSI afterburner to see more information about system load.

That could be possible, but I remember checking both GPU and CPU usage and coming to the conclusion it just was the engine itself that couldn't keep up.

Originally Posted by Greensiberia
[Image: lastpost-right.svg]

perhaps we should calculate real parameter of grass draw distance.

Yeah, that's correct, however having a variable to change helps infinitely. Having no initial value to start looking for with Cheat Engine makes this extremely hard. I don't believe the value itself changes based on the camera distance though, it seems it's just applied to the camera position instead of the character position.
rektbyfaith
11-04-2025, 12:44 PM #9

Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Greensiberia
[Image: lastpost-right.svg]

Perhaps it is strange, but I think you were bottlenecked by your CPU, check system monitor or install MSI afterburner to see more information about system load.

That could be possible, but I remember checking both GPU and CPU usage and coming to the conclusion it just was the engine itself that couldn't keep up.

Originally Posted by Greensiberia
[Image: lastpost-right.svg]

perhaps we should calculate real parameter of grass draw distance.

Yeah, that's correct, however having a variable to change helps infinitely. Having no initial value to start looking for with Cheat Engine makes this extremely hard. I don't believe the value itself changes based on the camera distance though, it seems it's just applied to the camera position instead of the character position.

rektbyfaith
Administrator
0
11-04-2025, 12:44 PM
#10
Archived author: raeef • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Nikk0z
[Image: lastpost-right.svg]

WotLK 3.3.5a..

I think you uploaded the wrong 335 wow.exe. Because it don't work,

and every one I asked to try it it didn't work for them too.

Plz re upload the working 335 wow.exe.
rektbyfaith
11-04-2025, 12:44 PM #10

Archived author: raeef • Posted: 2025-11-04T13:44:52.417644
Original source

Quote: Originally Posted by Nikk0z
[Image: lastpost-right.svg]

WotLK 3.3.5a..

I think you uploaded the wrong 335 wow.exe. Because it don't work,

and every one I asked to try it it didn't work for them too.

Plz re upload the working 335 wow.exe.

Pages (2): 1 2 Next
Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)