Bethesda made a news post/stickied post on the Steam forums, detailing their upcoming patch plans. People kept replying about wanting a sharperning slider, and Bethesda replied that they would pass it on to the devs.
Saving the table after editing in a hotkey toggle should also save the hotkey into the CE file. I'm using the F function keys for some of these since the Vulkan API has less programs like ReShade or similar but Cheat-Engine works pretty well thanks to user made scripts allowing for some pretty good control although with the little caveat that game updates risk breaking some of these unless the author updates them, I'm still learning for finding addresses and using the program for more than basic numerical values or editing existing scripts slightly so I'm not very good at it myself.
My bad, I accidentally made two CTs and was using the wrong one. Saving works May I also ask how exactly you added the weapon FOV to the CT?
I made a copy of one of the scripts and edited it's content with the provided info in that thread for the weapon FOV. So near the bottom of the original table it looks like this from a text editor: Code: [DISABLE] FOV_change: db F3 0F 2A 90 A0 04 00 00 unregistersymbol(fov) unregistersymbol(FOV_change) dealloc(newmem) cheatFOV: dd 1 { // ORIGINAL CODE - INJECTION POINT: "RAGE2.exe"+A011B4 "RAGE2.exe"+A0118D: CC - int 3 "RAGE2.exe"+A0118E: CC - int 3 "RAGE2.exe"+A0118F: CC - int 3 "RAGE2.exe"+A01190: 48 83 EC 48 - sub rsp,48 "RAGE2.exe"+A01194: 48 8B 05 3D 5B 66 02 - mov rax,[RAGE2.exe+3066CD8] "RAGE2.exe"+A0119B: 0F 57 D2 - xorps xmm2,xmm2 "RAGE2.exe"+A0119E: F3 0F 10 1D DE 68 D2 01 - movss xmm3,[RAGE2.exe+2727A84] "RAGE2.exe"+A011A6: 0F 57 C9 - xorps xmm1,xmm1 "RAGE2.exe"+A011A9: 0F 29 7C 24 30 - movaps [rsp+30],xmm7 "RAGE2.exe"+A011AE: 44 0F 29 44 24 20 - movaps [rsp+20],xmm8 // ---------- INJECTING HERE ---------- "RAGE2.exe"+A011B4: F3 0F 2A 90 A0 04 00 00 - cvtsi2ss xmm2,[rax+000004A0] // ---------- DONE INJECTING ---------- "RAGE2.exe"+A011BC: F3 0F 59 15 80 62 D2 01 - mulss xmm2,[RAGE2.exe+2727444] "RAGE2.exe"+A011C4: 0F 28 C2 - movaps xmm0,xmm2 "RAGE2.exe"+A011C7: F3 0F 59 05 49 64 D2 01 - mulss xmm0,[RAGE2.exe+2727618] "RAGE2.exe"+A011CF: F3 0F 2C C0 - cvttss2si eax,xmm0 "RAGE2.exe"+A011D3: F3 0F 2A C8 - cvtsi2ss xmm1,eax "RAGE2.exe"+A011D7: F3 0F 59 CB - mulss xmm1,xmm3 "RAGE2.exe"+A011DB: F3 0F 5C D1 - subss xmm2,xmm1 "RAGE2.exe"+A011DF: 0F 2F 15 1A 68 D2 01 - comiss xmm2,[RAGE2.exe+2727A00] "RAGE2.exe"+A011E6: 76 08 - jna RAGE2.exe+A011F0 "RAGE2.exe"+A011E8: F3 0F 58 15 64 6D D2 01 - addss xmm2,dword ptr [RAGE2.exe+2727F54] } </AssemblerScript> <CheatEntries> <CheatEntry> <ID>90823</ID> <Description>"fov"</Description> <VariableType>Float</VariableType> <Address>fov</Address> </CheatEntry> </CheatEntries> </CheatEntry> </CheatEntries> </CheatEntry> </CheatEntries> </CheatEntry> </CheatEntries> <UserdefinedSymbols> <SymbolEntry> <Name>cheatoncam</Name> <Address>13B9DED0000</Address> </SymbolEntry> <SymbolEntry> <Name>cheatTimeOn</Name> <Address>13B9E5F0000</Address> </SymbolEntry> <SymbolEntry> <Name>cheatFOV</Name> <Address>13B9DED0020</Address> </SymbolEntry> </UserdefinedSymbols> <Comments>Time: On/Off - Ctrl + Num* Day - Ctrl + Num2 Night - Ctrl + Num0 Morning - Ctrl + Num1 Evening - Ctrl + Num3 Forward - Ctrl + Num8 Backward - Ctrl + Num5 Fast Forward - Ctrl + Alt + Num8 Fast Backward - Ctrl + Alt + Num5 // // Free Camera: On/Off - Alt + R Move - WASD Space C (original in-game hotkeys) Move Faster - hold Shift Move Slower - hold Ctrl Jump to Waypoint - Shift + R // // FOV: Normal Change - Num4 or Num7 Fast Change - Ctrl + Num4 or Ctrl + Num4 Virtual-Key codes for chaing hotkeys inside LUA scripts: http://nehe.gamedev.net/article/msdn_virtualkey_codes/15009/ </Comments> </CheatTable> And then with the added in section it looks like this instead. Code: [DISABLE] FOV_change: db F3 0F 2A 90 A0 04 00 00 unregistersymbol(fov) unregistersymbol(FOV_change) dealloc(newmem) cheatFOV: dd 1 { // ORIGINAL CODE - INJECTION POINT: "RAGE2.exe"+A011B4 "RAGE2.exe"+A0118D: CC - int 3 "RAGE2.exe"+A0118E: CC - int 3 "RAGE2.exe"+A0118F: CC - int 3 "RAGE2.exe"+A01190: 48 83 EC 48 - sub rsp,48 "RAGE2.exe"+A01194: 48 8B 05 3D 5B 66 02 - mov rax,[RAGE2.exe+3066CD8] "RAGE2.exe"+A0119B: 0F 57 D2 - xorps xmm2,xmm2 "RAGE2.exe"+A0119E: F3 0F 10 1D DE 68 D2 01 - movss xmm3,[RAGE2.exe+2727A84] "RAGE2.exe"+A011A6: 0F 57 C9 - xorps xmm1,xmm1 "RAGE2.exe"+A011A9: 0F 29 7C 24 30 - movaps [rsp+30],xmm7 "RAGE2.exe"+A011AE: 44 0F 29 44 24 20 - movaps [rsp+20],xmm8 // ---------- INJECTING HERE ---------- "RAGE2.exe"+A011B4: F3 0F 2A 90 A0 04 00 00 - cvtsi2ss xmm2,[rax+000004A0] // ---------- DONE INJECTING ---------- "RAGE2.exe"+A011BC: F3 0F 59 15 80 62 D2 01 - mulss xmm2,[RAGE2.exe+2727444] "RAGE2.exe"+A011C4: 0F 28 C2 - movaps xmm0,xmm2 "RAGE2.exe"+A011C7: F3 0F 59 05 49 64 D2 01 - mulss xmm0,[RAGE2.exe+2727618] "RAGE2.exe"+A011CF: F3 0F 2C C0 - cvttss2si eax,xmm0 "RAGE2.exe"+A011D3: F3 0F 2A C8 - cvtsi2ss xmm1,eax "RAGE2.exe"+A011D7: F3 0F 59 CB - mulss xmm1,xmm3 "RAGE2.exe"+A011DB: F3 0F 5C D1 - subss xmm2,xmm1 "RAGE2.exe"+A011DF: 0F 2F 15 1A 68 D2 01 - comiss xmm2,[RAGE2.exe+2727A00] "RAGE2.exe"+A011E6: 76 08 - jna RAGE2.exe+A011F0 "RAGE2.exe"+A011E8: F3 0F 58 15 64 6D D2 01 - addss xmm2,dword ptr [RAGE2.exe+2727F54] } </AssemblerScript> <CheatEntries> <CheatEntry> <ID>90823</ID> <Description>"fov"</Description> <VariableType>Float</VariableType> <Address>fov</Address> </CheatEntry> </CheatEntries> </CheatEntry> </CheatEntries> </CheatEntry> </CheatEntries> </CheatEntry> <CheatEntry> <ID>93339</ID> <Description>"FOV"</Description> <Options moHideChildren="1"/> <LastState Activated="1"/> <Color>008000</Color> <VariableType>Auto Assembler Script</VariableType> <AssemblerScript>[ENABLE] aobscanmodule(_PlayerFOV,RAGE2.exe,F3 41 0F 10 86 E0 00 00 00 F3 0F) // should be unique alloc(newmem,$1000,"RAGE2.exe"+5EA64B) label(code) label(return) newmem: mov [r14+000000E0],(float)70 code: movss xmm0,[r14+000000E0] jmp return _PlayerFOV: jmp newmem nop nop nop nop return: registersymbol(_PlayerFOV) [DISABLE] _PlayerFOV: db F3 41 0F 10 86 E0 00 00 00 unregistersymbol(_PlayerFOV) dealloc(newmem) </AssemblerScript> <Hotkeys> <Hotkey> <Action>Toggle Activation</Action> <Keys> <Key>17</Key> <Key>106</Key> </Keys> <ID>0</ID> </Hotkey> </Hotkeys> </CheatEntry> </CheatEntries> <UserdefinedSymbols> <SymbolEntry> <Name>cheatoncam</Name> <Address>13B9DED0000</Address> </SymbolEntry> <SymbolEntry> <Name>cheatTimeOn</Name> <Address>273A7A90000</Address> </SymbolEntry> <SymbolEntry> <Name>cheatFOV</Name> <Address>13B9DED0020</Address> </SymbolEntry> </UserdefinedSymbols> <Comments>Time: On/Off - Ctrl + Num* Day - Ctrl + Num2 Night - Ctrl + Num0 Morning - Ctrl + Num1 Evening - Ctrl + Num3 Forward - Ctrl + Num8 Backward - Ctrl + Num5 Fast Forward - Ctrl + Alt + Num8 Fast Backward - Ctrl + Alt + Num5 // // Free Camera: On/Off - Alt + R Move - WASD Space C (original in-game hotkeys) Move Faster - hold Shift Move Slower - hold Ctrl Jump to Waypoint - Shift + R // // FOV: Normal Change - Num4 or Num7 Fast Change - Ctrl + Num4 or Ctrl + Num4 Virtual-Key codes for chaing hotkeys inside LUA scripts: http://nehe.gamedev.net/article/msdn_virtualkey_codes/15009/ </Comments> </CheatTable> With the added part being this. Code: <CheatEntry> <ID>93339</ID> <Description>"FOV"</Description> <Options moHideChildren="1"/> <LastState Activated="1"/> <Color>008000</Color> <VariableType>Auto Assembler Script</VariableType> <AssemblerScript>[ENABLE] aobscanmodule(_PlayerFOV,RAGE2.exe,F3 41 0F 10 86 E0 00 00 00 F3 0F) // should be unique alloc(newmem,$1000,"RAGE2.exe"+5EA64B) label(code) label(return) newmem: mov [r14+000000E0],(float)70 code: movss xmm0,[r14+000000E0] jmp return _PlayerFOV: jmp newmem nop nop nop nop return: registersymbol(_PlayerFOV) [DISABLE] _PlayerFOV: db F3 41 0F 10 86 E0 00 00 00 unregistersymbol(_PlayerFOV) dealloc(newmem) </AssemblerScript> <Hotkeys> <Hotkey> <Action>Toggle Activation</Action> <Keys> <Key>17</Key> <Key>106</Key> </Keys> <ID>0</ID> </Hotkey> </Hotkeys> </CheatEntry> mov [r14+000000E0],(float)70 The 70 is the value you can edit to any value, I found it to be a pretty good one but 65 - 80 should all work without being too far out with the arm models and less zoomed in than the default and then just untick and tick the script enabled again and it updates immediately with the new value if you change it. Just feels better for regular gameplay than the default value, FOV should be horizontal and not vertical so a slightly higher value. I really miss this as a option in many games since Crysis allowed for changing it though it was a console variable in that game and that also goes for the regular FOV and the sprint FOV where the view slightly expanded giving a sense of speed but many games use these really large zoomed in on gun models which just takes up a lot of screen space and also personally it doesn't look very good.
Works like a charm, thanks. I found 55 to be the sweet spot for guns so they don't look too chunky, and not too small.
Hmm sounds like I might be using a bit of a large value then having the poor ranger stretch his arms way out in the distance to clear up the screen ha ha. Well should try a slightly lower perhaps and maybe see how anything not assault rifle looks like. Though it's not DOOM style at least although centering it like that had it's uses too back in the day.
Just finished the game in 31 hours not bad Game is great just dont expect to much, loved the ending btw. Cant wait for more story dlc.
I saw this in steam, We wanted to take a minute to cover just some of the reported issues we are working to address: Audio fixes, such as NPC audio dips Menu optimizations (reduction in latency) Several crash fixes Racing bug issues, including finishing in 1st place but receiving 2nd place (how rude!) Reducing the amount of Wasteland Wizard locations (from 15 to 3!) A dialog prompt issue with Kvasir Mouse acceleration/smoothing options New AMD sharpness algorithm for all platforms (to address “blurry” complaints) Nicholas Raine armor fix Outside of squashing bugs, the team is also working on adding new features to the game. We’ve seen the feedback that you want to be able to revisit some of the bandit camps that you’ve previously cleared. We love that feedback! In the near future, select bandit camps that you’ve cleared are going to be repopulated at an even higher difficulty with a reward incentive. The best part? The challenge is ongoing, so you can test your skills as you attempt to clear the outposts again and again, with the outposts getting more difficult each time. More details to come. Looks like a nice list of fixes we can expect.
hmm the wizzard guy i thought was one dude that travels around. i had to fly between his stops to find him, not sure why there were 15 of him nor where the 15 were at. as far as for wtf the wizzard/s are they do f all to explain it, hes a wacky character in a wacky silly world and its and fps game, how much world building and story are we expecting? a bit more i think via reviews. and criticisms. they had a good fun game but they needed a bit more of that stuff to elevate it to something more.
Finished it today in 15hrs and did about 60% of the map (didn't even find all the guns). Anyway, it's an OK game but I really didn't feel like completing the map and I don't think it will be that memorable to me. On to the next game!
It's a single player only game. Still surprises me that people try to judge a game's quality by the amount of people playing it at any given time. You'll see a rise in players when the first big patch comes out, when new content is released every month. But, this whole "There are only this many people playing... this must suck" mentality is very, very flawed.
Yep, the game didn’t die people have finished it. I love the game and am still playing after 25 hours.
I'll return to play more with the next run of updates, fixes and free content they are adding. Plus, the two DLC packs will be a nice boost.
here is the issue with rage they sell it as a open world game, but that open world is deep as a puddle. so yea as long as your having fun with the combat, and doing random stuff on occasion, but the npcs and world are so dead. the main npcs do not have any dialogue outside their missions, the quest npcs will never go back to their farms or town once you cleared it out that would have been amazing to see since they tell you that they want you do the task so they can return then they just stand in the same spot for the rest of the game doing nothing but spouting the ty for your help and how they will be rushing back......man its been weeks...... a co op mode would have helped this game if you could up the spawns in the game, because co op is always more fun than solo play especially when the combat and powers are as dynamic as they are could have made some great streaming/videos. that would have given it a tad more shelf life. until they could add to or deepen the world building/activities.
