Widescreen Gaming Forum

domomunk wrote:

Cirez wrote:I edited the .exe with Hex-Editor MX

great. was able to get it working. thanks a lot! 21:9 better than 16:9.
32:9 would be good if i was able to find the code to change, but not complaining.
totally unplayable before. lol

qq308169172 wrote:https://onedrive.live.com/redir?resid=3009E45C2F9E13C7!3348&authkey=!ABKgG4DMfs1l-To
download

domomunk wrote:

qq308169172 wrote:https://onedrive.live.com/redir?resid=3009E45C2F9E13C7!3348&authkey=!ABKgG4DMfs1l-To
download

thanks!

PyrDas wrote:

domomunk wrote:

qq308169172 wrote:https://onedrive.live.com/redir?resid=3009E45C2F9E13C7!3348&authkey=!ABKgG4DMfs1l-To
download

thanks!

When I used that the game said I had to download an update, version mismatch... How did u get it to work?

PyrDas wrote:Any1 found the new codes for 21:9? Tried finding "35 FA 0E 3C BA" but couldnt find it, found "35 FA 0E 3C 35" and changed that but that just resulted in my camera spinnin like crazy.

PyrDas wrote:Any1 found the new codes for 21:9? Tried finding "35 FA 0E 3C BA" but couldnt find it, found "35 FA 0E 3C 35" and changed that but that just resulted in my camera spinnin like crazy.

Rose wrote:For 2560x1080, you can hex edit \Archon\Binaries\Win64\Dauntless-Win64-Shipping.exe and search for 35 FA 0E 3C BA and replace it with D7 CB 2C 3C BA to get the FOV to match that of 1920x1080.

You can also edit the config as instructed here to be able to see the character at the creation screen.

dauntless.png

Fuzzybutt wrote:

Rose wrote:For 2560x1080, you can hex edit \Archon\Binaries\Win64\Dauntless-Win64-Shipping.exe and search for 35 FA 0E 3C BA and replace it with D7 CB 2C 3C BA to get the FOV to match that of 1920x1080.

You can also edit the config as instructed here to be able to see the character at the creation screen.

dauntless.png

Made an account just to say thanks! Hex Edit code seems to now be 35 FA 0E 3C DB but replacing for above still works. I wondered why the FOV gauge wasn't working, and why the camera was so close! I kept telling my friends I couldn't see damage numbers and certain events and they had no idea why..

qq308169172 wrote:

Fuzzybutt wrote:

Rose wrote:For 2560x1080, you can hex edit \Archon\Binaries\Win64\Dauntless-Win64-Shipping.exe and search for 35 FA 0E 3C BA and replace it with D7 CB 2C 3C BA to get the FOV to match that of 1920x1080.

You can also edit the config as instructed here to be able to see the character at the creation screen.

dauntless.png

Made an account just to say thanks! Hex Edit code seems to now be 35 FA 0E 3C DB but replacing for above still works. I wondered why the FOV gauge wasn't working, and why the camera was so close! I kept telling my friends I couldn't see damage numbers and certain events and they had no idea why..

35 FA 0E 3C DB

35 FA 5A 3C DB

qq308169172 wrote:

Fuzzybutt wrote:

Rose wrote:For 2560x1080, you can hex edit \Archon\Binaries\Win64\Dauntless-Win64-Shipping.exe and search for 35 FA 0E 3C BA and replace it with D7 CB 2C 3C BA to get the FOV to match that of 1920x1080.

You can also edit the config as instructed here to be able to see the character at the creation screen.

dauntless.png

Made an account just to say thanks! Hex Edit code seems to now be 35 FA 0E 3C DB but replacing for above still works. I wondered why the FOV gauge wasn't working, and why the camera was so close! I kept telling my friends I couldn't see damage numbers and certain events and they had no idea why..

35 FA 0E 3C DB

35 FA 5A 3C DB

Jacob Singer wrote:Ok, this fix for the character creation screen worked great. Has anyone posted a fix or hexedit for 32:9? Apologies if I missed it. The .exe I downloaded just crashed on startup.

qq308169172 wrote:

Jacob Singer wrote:Ok, this fix for the character creation screen worked great. Has anyone posted a fix or hexedit for 32:9? Apologies if I missed it. The .exe I downloaded just crashed on startup.

HDX >35 FA 0E 3C DB >35 FA 64 3C DB

Bit89 wrote:Since the latest Dauntless patch I cannot get HDX >35 FA 0E 3C DB >35 FA 64 3C DB to work. Has it worked for anyone else? Thanks!