|
|
Post by DAOWAce on Mar 22, 2022 17:48:39 GMT 10
Ok. I think I now have some idea what could be going wrong in your case. Can you please try this stripped out version of the cheatengine script? If it goes black again then it would be really helpful if you could post screenshot of memory viewer at address 0x48ceda. (PS: it would be nice to get some response before this weekend). Reviving widescreenfixer will require time which I am finding hard to spare these days but I will try something either this or next weekend. You doing this blind? I see the OP never responded, and I found this thread from a Steam guide comment section (about downgrading the version to work with widescreen fixer), so I tried testing it. Neither of the AOB CT's seem to work for me. Trying to check the box results in.. nothing happening. Is it built for a specific CE version? Additionally, the code at the end had an error in both versions. Version 1: <!-- </UserdefinedSymbols> -->This was mistakenly commented out. Version 2: <UserdefinedSymbols>
<SymbolEntry>
<Name>cameraDistanceReadAOB</Name>
<Address> 0048CEDA</Address>
</SymbolEntry>
</CheatTable>
Missing the closing </UserdefinedSymbols> Had a desire to play through the RE games I missed (6, Revelations 1/2), but they're completely unplayable without ultrawide and FoV mods, and sadly the fixes for Revelations ceased working a few years back. I don't really know anything about doing stuff like this, so without help from others, it's a lost cause.
|
|
|
|
Post by Mythic on Mar 23, 2022 14:44:17 GMT 10
|
|
|
|
Post by picoleet on Mar 30, 2022 4:54:13 GMT 10
Ok. I think I now have some idea what could be going wrong in your case. Can you please try this stripped out version of the cheatengine script? If it goes black again then it would be really helpful if you could post screenshot of memory viewer at address 0x48ceda. (PS: it would be nice to get some response before this weekend). Reviving widescreenfixer will require time which I am finding hard to spare these days but I will try something either this or next weekend. You doing this blind? I see the OP never responded, and I found this thread from a Steam guide comment section (about downgrading the version to work with widescreen fixer), so I tried testing it. Neither of the AOB CT's seem to work for me. Trying to check the box results in.. nothing happening. Is it built for a specific CE version? Additionally, the code at the end had an error in both versions. Version 1: <!-- </UserdefinedSymbols> -->This was mistakenly commented out. Version 2: <UserdefinedSymbols>
<SymbolEntry>
<Name>cameraDistanceReadAOB</Name>
<Address> 0048CEDA</Address>
</SymbolEntry>
</CheatTable>
Missing the closing </UserdefinedSymbols> Had a desire to play through the RE games I missed (6, Revelations 1/2), but they're completely unplayable without ultrawide and FoV mods, and sadly the fixes for Revelations ceased working a few years back. I don't really know anything about doing stuff like this, so without help from others, it's a lost cause. > You doing this blind? Yes, I am doing it blind because I do not have access to a windows machine. > Is it built for a specific CE version?
I have never used CE so not really sure. I modified the original script after reading the documentation.
> Neither of the AOB CT's seem to work for me
I wonder what I am doing wrong here. > I found this thread from a Steam guide comment section (about downgrading the version to work with widescreen fixer), so I tried testing it.
I know about this thread. I used it for discovering the offset in newer binary. >Had a desire to play through the RE games I missed ... so without help from others, it's a lost cause.
I would like to make it work for others. But need someone to provide critical feedback.
|
|
|
|
Post by picoleet on Mar 30, 2022 16:17:10 GMT 10
I have one more version I would like someone to try before I start working on widescreenfixer (which can take lot of time). This time the process is involved. You need to follow the following steps: - Download windbg. This link describes how: www.windbg.xyz/windbg/basics
- Start windbg
- Start the game, wait till title screen and then alt-tab out of it
- Or, you may start a campaign game if you wish to see the change immediately.
- In windbg, attach to the game's process:
- Steps: File -> Attach to a process -> select rerev.exe
- See this segment of video for visual guide:
- Once attached, enter the following commands in the command console (at the bottom) (see this guy entering some other command:
- Set the FOV value (0x42700000 (60.0) -- original varies from 30-50):
eb 0x0fcbd50 0xd9 0x5e 0x3c 0xc7 0x46 0x3c 0x00 0x00 0x70 0x42 0x8b 0xcb 0xe9 0x61 0xb3 0x4c 0xff - Patch jump:
eb 0x4970bd 0xe9 0x8e 0x4c 0xb3 0x0 - Quit and detach:
qd
- Now switch to the game and witness the wide FOV :^)
Let me know if it works! If it doesn't work, I would really appreciate if the user can provide screenshots of their actions and windbg. Thanks in advance!
|
|
|
|
Post by george54979 on May 5, 2022 10:20:19 GMT 10
I'm going crazy! It's a pain to play Can anyone handle this ct unusable problem? fearlessrevolution.com/viewtopic.php?t=2500I don't want to use the Roll Back method because the picture is fisheye effect Sorry English is not my native language I found its single float coordinate parameter But I really can't change the FOV camera distance FOV 1F6E8C70 Coordinate: Y 1F6E8C80 Coordinate: Z 1F6E8C84 Coordinate: X 1F6E8C88 Spinning: Param 1 1F6E8C90 Spinning: Param 2 1F6E8C94 Spinning: Param 3 1F6E8C98 Rotation: Horizontal 1F6E8CA0 Rotation: Vertical 1F6E8CA4 Rotation: Flip 1F6E8CA8
|
|
|
|
Post by teo on Aug 11, 2022 18:32:02 GMT 10
Damn, that windbg kept crashing the game once it tries to attach, so I kinda went back and checked that table Picoleet has posted, it's was missing some parts, I redid his work and stripped the initial table we used as a base and replacing the incorrect AOB and it worked, I'll be posting the table some time later
|
|
|
|
Post by teo on Aug 21, 2022 12:37:05 GMT 10
Okay, apparently there is a DLL available that gives the opportunity to set custom FOV, Shadow Map resolution, FPS limit, etc. ( This one), sadly the FOV change comes with the fish-eye effect which I don't like at all, so I'm posting the Cheat Engine table I made based on the initial CT file Cielos from fearlessrevolution.com made, huge thanks to Picoleet for locating the new addresses, explaining in a simple manner what was needed to be kept in the script and for general will to help. Here is the script, use it with Cheat Engine, toggle button is F11, FOV could be manipulated through lowering "fCustomCameraDistance: dd (float)-100.0" in the script itself.
|
|
|
|
Post by picoleet on Sept 6, 2022 4:48:18 GMT 10
Okay, apparently there is a DLL available that gives the opportunity to set custom FOV, Shadow Map resolution, FPS limit, etc. ( This one), sadly the FOV change comes with the fish-eye effect which I don't like at all, so I'm posting the Cheat Engine table I made based on the initial CT file Cielos from fearlessrevolution.com made, huge thanks to Picoleet for locating the new addresses, explaining in a simple manner what was needed to be kept in the script and for general will to help. Here is the script, use it with Cheat Engine, toggle button is F11, FOV could be manipulated through lowering "fCustomCameraDistance: dd (float)-100.0" in the script itself. Great work friend! Given that the script is small enough, perhaps you should paste the contents here as well in case the mega link stops working.
|
|
|
|
Post by teo on Sept 6, 2022 18:56:53 GMT 10
<?xml version="1.0" encoding="utf-8"?>
<CheatTable CheatEngineTableVersion="34">
<CheatEntries>
<CheatEntry>
<ID>1116</ID>
<Description>"Custom FOV value"</Description>
<Options moHideChildren="1"/>
<LastState Activated="1"/>
<VariableType>Auto Assembler Script</VariableType>
<AssemblerScript>[ENABLE]
//code from here to '[DISABLE]' will be used to enable the cheat
aobscan(cameraDistanceReadAOB,F3 0F 10 77 18 F3 0F 58 70 78)
registersymbol(cameraDistanceReadAOB)
label(fCustomCameraDistance)
registersymbol(fCustomCameraDistance)
alloc(newmem,2048)
label(returnhere)
label(originalcode)
label(exit)
label(setcameradistance)
newmem: //this is allocated memory, you have read,write,execute access
//place your code here
setcameradistance:
movss xmm6,[fCustomCameraDistance]
jmp exit
originalcode:
movss xmm6,[edi+18]
exit:
jmp returnhere
///
fCustomCameraDistance:
dd (float)-100.0
///
cameraDistanceReadAOB: //"rerev.exe"+48CEDA:
jmp long newmem
returnhere:
[DISABLE]
//code from here till the end of the code will be used to disable the cheat
dealloc(newmem)
cameraDistanceReadAOB: //"rerev.exe"+48CEDA:
db F3 0F 10 77 18
//Alt: movss xmm6,[edi+18]
unregistersymbol(cameraDistanceReadAOB)
unregistersymbol(fCustomCameraDistance)
</AssemblerScript>
<Hotkeys>
<Hotkey>
<Action>Toggle Activation</Action>
<Keys>
<Key>122</Key>
</Keys>
<ID>1</ID>
</Hotkey>
</Hotkeys>
</CheatEntry>
</CheatEntries>
<UserdefinedSymbols>
<SymbolEntry>
<Name>cameraModeReadAOB</Name>
<Address>0048BD33</Address>
</SymbolEntry>
<SymbolEntry>
<Name>fCustomCameraInterval</Name>
<Address>27CB00FB</Address>
</SymbolEntry>
<SymbolEntry>
<Name>iCustomCameraDistance</Name>
<Address>29F00017</Address>
</SymbolEntry>
</UserdefinedSymbols>
</CheatTable>
|
|
|
|
Post by Vork on Apr 14, 2023 15:25:12 GMT 10
|
|
