[Archive] Vanilla 1.12 & TBC 2.4.3 - Permanent FoV fix (patched WoW.exe)
[Archive] Vanilla 1.12 & TBC 2.4.3 - Permanent FoV fix (patched WoW.exe)
11-04-2025, 12:44 PM
Original source
Quote: As many of you probably already know the field of view in Vanilla and TBC is different than WotLK and all other expansions past WotLK (image representing what I mean here).
First of all, most of the credit goes to namreeb: thanks to the memory addresses he posted here I managed to patch WoW.exe for both Vanilla and TBC, thus making the FoV change permanent so that it no longer gets reset on /reload and disconnects like it did with memory edits.
The FoV value is set to 1.925, which should be similar to the one used in WotLK+.
Here are the patched executables:
WoW.exe - Vanilla 1.12.1 - FoV @1.925
WoW.exe - Vanilla 1.12.1 - FoV @2.0
WoW.exe - Vanilla 1.12.1 - FoV @2.1
WoW.exe - TBC 2.4.3 - FoV @1.925
WoW.exe - TBC 2.4.3 - FoV @2.0
WoW.exe - TBC 2.4.3 - FoV @2.1
Virustotal scans:
WoW.exe - Vanilla 1.12.1 - FoV @1.925
WoW.exe - Vanilla 1.12.1 - FoV @2.0
WoW.exe - Vanilla 1.12.1 - FoV @2.1
WoW.exe - TBC 2.4.3 - FoV @1.925
WoW.exe - TBC 2.4.3 - FoV @2.0
WoW.exe - TBC 2.4.3 - FoV @2.1
For anyone who is interested in the explanation on how I did it, here it is:
All I used was Cheat Engine and an hex editor (I used HxD). I already knew the memory address I wanted to patch so that made things easier.
I started WoW.exe normally (there is no need to login), then attached Cheat Engine to it and manually added the address 0x8089B4 for Vanilla or 0x8B5A04 for TBC.
Then I changed the value type to float, and the address was shown to hold a value of ~1.57, which is the default FoV in Vanilla and TBC.
I then changed the value type to array of bytes and the value shown was now DB 0F C9 3F E6 F1 47 40 00 00 (which I assume is the hex representation of 1.57, however it does not seem to be equal to 1.57, maybe only part of it represents the float value? If you know more about this feel free to shed some light).
After changing the value type back to float and changing it to the desired value (in my case 1.925) I changed back the value type to array of bytes once more, and it now reported a value of 66 66 F6 3F E6 F1 47 40 00 00.
The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00.
That's all, I hope this has been useful!
rektbyfaith
11-04-2025, 12:44 PM #1Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: As many of you probably already know the field of view in Vanilla and TBC is different than WotLK and all other expansions past WotLK (image representing what I mean here).
First of all, most of the credit goes to namreeb: thanks to the memory addresses he posted here I managed to patch WoW.exe for both Vanilla and TBC, thus making the FoV change permanent so that it no longer gets reset on /reload and disconnects like it did with memory edits.
The FoV value is set to 1.925, which should be similar to the one used in WotLK+.
Here are the patched executables:
WoW.exe - Vanilla 1.12.1 - FoV @1.925
WoW.exe - Vanilla 1.12.1 - FoV @2.0
WoW.exe - Vanilla 1.12.1 - FoV @2.1
WoW.exe - TBC 2.4.3 - FoV @1.925
WoW.exe - TBC 2.4.3 - FoV @2.0
WoW.exe - TBC 2.4.3 - FoV @2.1
Virustotal scans:
WoW.exe - Vanilla 1.12.1 - FoV @1.925
WoW.exe - Vanilla 1.12.1 - FoV @2.0
WoW.exe - Vanilla 1.12.1 - FoV @2.1
WoW.exe - TBC 2.4.3 - FoV @1.925
WoW.exe - TBC 2.4.3 - FoV @2.0
WoW.exe - TBC 2.4.3 - FoV @2.1
For anyone who is interested in the explanation on how I did it, here it is:
All I used was Cheat Engine and an hex editor (I used HxD). I already knew the memory address I wanted to patch so that made things easier.
I started WoW.exe normally (there is no need to login), then attached Cheat Engine to it and manually added the address 0x8089B4 for Vanilla or 0x8B5A04 for TBC.
Then I changed the value type to float, and the address was shown to hold a value of ~1.57, which is the default FoV in Vanilla and TBC.
I then changed the value type to array of bytes and the value shown was now DB 0F C9 3F E6 F1 47 40 00 00 (which I assume is the hex representation of 1.57, however it does not seem to be equal to 1.57, maybe only part of it represents the float value? If you know more about this feel free to shed some light).
After changing the value type back to float and changing it to the desired value (in my case 1.925) I changed back the value type to array of bytes once more, and it now reported a value of 66 66 F6 3F E6 F1 47 40 00 00.
The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00.
That's all, I hope this has been useful!
rektbyfaith
11-04-2025, 12:44 PM #2Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
11-04-2025, 12:44 PM
Original source
Quote: If all you're using CheatEngine for is the float to hexadecimal conversion, just an FYI that I use this site for that: Floating Point to Hex Converter
rektbyfaith
11-04-2025, 12:44 PM #3Archived author: namreeb • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: If all you're using CheatEngine for is the float to hexadecimal conversion, just an FYI that I use this site for that: Floating Point to Hex Converter
11-04-2025, 12:44 PM
Original source
Quote: Thanks for the input, however I had already tried using that website, but I get different hex values than on Cheat Engine.
Cheat Engine:
Website:
Am I missing something?
![[Image: shjkim.png]](https://a.doko.moe/shjkim.png)
![[Image: squqvd.png]](https://a.doko.moe/squqvd.png)
rektbyfaith
11-04-2025, 12:44 PM #4Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Thanks for the input, however I had already tried using that website, but I get different hex values than on Cheat Engine.
Cheat Engine:
Website:
Am I missing something?
11-04-2025, 12:44 PM
Original source
Quote: Nice one! However I do have a few questions though.
1) Any chance you have tested this on Kronos 1.12.1? I'm curious if their warden will detect it and auto-ban you.
2) Does this WoW.exe contain the 256 sound channel modification/fix? From this one: GitHub - Doctorbeefy/Wow.exe-256-Sound: Allows 256 sound channels
Thanks in advance!
EDIT:
Originally Posted by Nikk0z
For anyone who is interested in the explanation on how I did it, here it is:
All I used was Cheat Engine and an hex editor (I used HxD). I already knew the memory address I wanted to patch so that made things easier.
I started WoW.exe normally (there is no need to login), then attached Cheat Engine to it and manually added the address 0x8089B4 for Vanilla or 0x8B5A04 for TBC.
Then I changed the value type to float, and the address was shown to hold a value of ~1.57, which is the default FoV in Vanilla and TBC.
I then changed the value type to array of bytes and the value shown was now DB 0F C9 3F E6 F1 47 40 00 00 (which I assume is the hex representation of 1.57, however it does not seem to be equal to 1.57, maybe only part of it represents the float value? If you know more about this feel free to shed some light).
After changing the value type back to float and changing it to the desired value (in my case 1.925) I changed back the value type to array of bytes once more, and it now reported a value of 66 66 F6 3F E6 F1 47 40 00 00.
The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00.
I managed to do it myself by following your last step. So basically what I did was downloading the client with the sound channel modification and then added the FOV modification into it.
It all seems to work as intended and so far there has been no issues on Kronos
Cheers!
![[Image: lastpost-right.svg]](https://www.ownedcore.com/forums/images/styles/OwnedCoreFX/buttons/lastpost-right.svg)
![[Image: smile.png]](https://www.ownedcore.com/forums/images/smilies/smile.png)
rektbyfaith
11-04-2025, 12:44 PM #5Archived author: AG007 • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Nice one! However I do have a few questions though.
1) Any chance you have tested this on Kronos 1.12.1? I'm curious if their warden will detect it and auto-ban you.
2) Does this WoW.exe contain the 256 sound channel modification/fix? From this one: GitHub - Doctorbeefy/Wow.exe-256-Sound: Allows 256 sound channels
Thanks in advance!
EDIT:
Originally Posted by Nikk0z
For anyone who is interested in the explanation on how I did it, here it is:
All I used was Cheat Engine and an hex editor (I used HxD). I already knew the memory address I wanted to patch so that made things easier.
I started WoW.exe normally (there is no need to login), then attached Cheat Engine to it and manually added the address 0x8089B4 for Vanilla or 0x8B5A04 for TBC.
Then I changed the value type to float, and the address was shown to hold a value of ~1.57, which is the default FoV in Vanilla and TBC.
I then changed the value type to array of bytes and the value shown was now DB 0F C9 3F E6 F1 47 40 00 00 (which I assume is the hex representation of 1.57, however it does not seem to be equal to 1.57, maybe only part of it represents the float value? If you know more about this feel free to shed some light).
After changing the value type back to float and changing it to the desired value (in my case 1.925) I changed back the value type to array of bytes once more, and it now reported a value of 66 66 F6 3F E6 F1 47 40 00 00.
The last step is opening WoW.exe in an hex editor and looking for the hex values DB 0F C9 3F E6 F1 47 40 00 00 and replacing them with 66 66 F6 3F E6 F1 47 40 00 00.
I managed to do it myself by following your last step. So basically what I did was downloading the client with the sound channel modification and then added the FOV modification into it.
It all seems to work as intended and so far there has been no issues on Kronos
Cheers!
11-04-2025, 12:44 PM
Original source
Quote: Glad to know that you managed to make it work. I'll still answer your questions, if someone else is wondering.
Originally Posted by AG007
1) Any chance you have tested this on Kronos 1.12.1? I'm curious if their warden will detect it and auto-ban you.
2) Does this WoW.exe contain the 256 sound channel modification/fix? From this one: GitHub - Doctorbeefy/Wow.exe-256-Sound: Allows 256 sound channels
1) I haven't tested this on Kronos, the only realms I tested this on are Elysium (Vanilla) and Hellfire (TBC), and neither got me auto-banned, although I heard Hellfire doesn't have Warden implemented. I honestly can't say if this can get picked up by Warden or not though, I have no knowledge about it. Maybe namreeb could give a more in depth answer about that?
2) No, it doesn't. No other modifications have been implemented except for the one described in the OP.
rektbyfaith
11-04-2025, 12:44 PM #6Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Glad to know that you managed to make it work. I'll still answer your questions, if someone else is wondering.
Originally Posted by AG007
1) Any chance you have tested this on Kronos 1.12.1? I'm curious if their warden will detect it and auto-ban you.
2) Does this WoW.exe contain the 256 sound channel modification/fix? From this one: GitHub - Doctorbeefy/Wow.exe-256-Sound: Allows 256 sound channels
1) I haven't tested this on Kronos, the only realms I tested this on are Elysium (Vanilla) and Hellfire (TBC), and neither got me auto-banned, although I heard Hellfire doesn't have Warden implemented. I honestly can't say if this can get picked up by Warden or not though, I have no knowledge about it. Maybe namreeb could give a more in depth answer about that?
2) No, it doesn't. No other modifications have been implemented except for the one described in the OP.
11-04-2025, 12:44 PM
Original source
Quote: Any screenshots of what this looks like?
I know what FOV does in a first person game, but fail to see how this would be beneficial in a third person game where we can spin the camera?
Is it just increasing the view distance of the camera or is it doing something more complex?
rektbyfaith
11-04-2025, 12:44 PM #7Archived author: Deviner • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Any screenshots of what this looks like?
I know what FOV does in a first person game, but fail to see how this would be beneficial in a third person game where we can spin the camera?
Is it just increasing the view distance of the camera or is it doing something more complex?
11-04-2025, 12:44 PM
Original source
Quote: Well, I would say that other than increasing the view distance it also increases (or decreases, depending on the value) the camera's angle of view. For some screenshots check out this thread on the Elysium forums:
Will FoV fix for 1.12 clients be allowed on Elysium? - General Discussion - Elysium Project
rektbyfaith
11-04-2025, 12:44 PM #8Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Well, I would say that other than increasing the view distance it also increases (or decreases, depending on the value) the camera's angle of view. For some screenshots check out this thread on the Elysium forums:
Will FoV fix for 1.12 clients be allowed on Elysium? - General Discussion - Elysium Project
11-04-2025, 12:44 PM
Original source
Quote: Any fix for the OS X client? I edited the hex value as shown in your last step but it had no effect.
rektbyfaith
11-04-2025, 12:44 PM #9Archived author: bastion05 • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Any fix for the OS X client? I edited the hex value as shown in your last step but it had no effect.
11-04-2025, 12:44 PM
Original source
Quote: Well, I don't have any Mac OS X devices to test this with but I'm assuming it would work the same way. I'll see if I can manage to get a Hackintosh VM going and take a look.
EDIT: I got an Hackintosh VM up and running, however I can't actually test the game since 3D acceleration is not supported while emulating Mac OS X. I was able to patch the .app executable (World of Warcraft.app/Contents/MacOS/World of Warcraft) by opening it with 0xED. I'm assuming that's the same thing you did though. If that's not working my guess would be that the Mac executable is coded differently (kinda weird though, since the hex values I replaced on the Windows executable are still there); you'll need to do some snooping around with Cheat Engine to get the fix working on mac, refer to this thread (FoV in wow) for some useful info.
rektbyfaith
11-04-2025, 12:44 PM #10Archived author: Nikk0z • Posted: 2025-11-04T13:44:52.316474
Original source
Quote: Well, I don't have any Mac OS X devices to test this with but I'm assuming it would work the same way. I'll see if I can manage to get a Hackintosh VM going and take a look.
EDIT: I got an Hackintosh VM up and running, however I can't actually test the game since 3D acceleration is not supported while emulating Mac OS X. I was able to patch the .app executable (World of Warcraft.app/Contents/MacOS/World of Warcraft) by opening it with 0xED. I'm assuming that's the same thing you did though. If that's not working my guess would be that the Mac executable is coded differently (kinda weird though, since the hex values I replaced on the Windows executable are still there); you'll need to do some snooping around with Cheat Engine to get the fix working on mac, refer to this thread (FoV in wow) for some useful info.
Recently Browsing
1 Guest(s)
1 Guest(s)
Recently Browsing
1 Guest(s)
1 Guest(s)