1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Rage 2

Discussion in 'Games, Gaming & Game-demos' started by Carfax, May 14, 2018.

  1. DerSchniffles

    DerSchniffles Ancient Guru

    Messages:
    1,586
    Likes Received:
    102
    GPU:
    Zotac GTX1080ti
    Is anyone else getting massive frame drops in MB TV? Especially on the "boss" fight at the end, I get drops into the 20's! I hope they release a patch soon, I will probably be finished with this game by the time they do haha. Performance is good for the most part, the most recent nvidia drivers gave a decent boost but sometimes fps can be all over the place and dosent make sense. I avg about 7-80 fps on a mix of high and ultra settings, 3440x1440. Fun game!
     
  2. Damien_Azreal

    Damien_Azreal Ancient Guru

    Messages:
    9,916
    Likes Received:
    1,062
    GPU:
    Gigabyte 1070 Ti
    Held solid frame rates for me, game hasn't dipped under 60fps since the hotfix patch they released last week.
    Before that, I would get the occasional stutter while driving around, but that was it.
     
    cerebus23 likes this.
  3. DerSchniffles

    DerSchniffles Ancient Guru

    Messages:
    1,586
    Likes Received:
    102
    GPU:
    Zotac GTX1080ti
    Interesting, MB TV is the ONLY place so far that has issues. Running around the world is pretty solid minus the occasional fps "freak out" that occurs.

    Man, I have all the guns and all the powers unlocked now...I am unstoppable. Normal mode is waaaaaay to easy, especially after you unlock everything. I should have played on a harder difficulty for sure. Perhaps if they add enough content through patches and/or dlc, I will do another playthrough on Nightmare.
    I really do wish the world was more full. I know it has been mentioned on here already but it can feel so empty.
     
    cerebus23 likes this.
  4. Witcher29

    Witcher29 Maha Guru

    Messages:
    1,094
    Likes Received:
    80
    GPU:
    1080 Ti Gaming X
    .I just bought the game aswell, what i didnt like is the game got no gamma/brightness slider what the hell was Bethesda thinking xD
    Besides that the game is great, i get a good fps on 1440p [without resolution scale its off] a fps between 70 and 110 on ultra settings, the game wont go lower as 70.

    I have to say tho the game can look dull @ times because its so freaking bright.
    Overal its a fun game, but i just cant ge used to the controls there are to much bindings and to many power ups i keep pressing the wrong buttons lol.

    Also without any aa on i see a weird ghosting effect when i move the character, with aa on i dont have such problems.

    I just wish besthesda could release a sharpness slider in there next patch, to bump up the clarity of the game.
     
    Last edited: May 26, 2019

  5. haste

    haste Master Guru

    Messages:
    657
    Likes Received:
    101
    GPU:
    GTX 1080 @ 2.1GHz
    The same goes for JC4. The same engine, the same problems. Somebody was extremely lazy to put gamma consts to their tone mapper I guess... I honestly don't understand how they could omit this.
     
  6. Witcher29

    Witcher29 Maha Guru

    Messages:
    1,094
    Likes Received:
    80
    GPU:
    1080 Ti Gaming X
    Yeah it makes no sense, game is to bright atm for my taste.

    Nvidia freestyle is an option but i refuse to install GFE.
     
  7. Damien_Azreal

    Damien_Azreal Ancient Guru

    Messages:
    9,916
    Likes Received:
    1,062
    GPU:
    Gigabyte 1070 Ti
    A Bethesda employee said he would pass along the request for a Sharpness slider to the team at Avalanche, and see if it's something that can be added.

    And yeah, there are a LOT of controls.
    Personally, I feel the Focus/Dash control should be the same button as sprint.

    But, my current control setup is...
    EDSF - movement, A - Jump, Z - Crouch, Spacebar - Use, R - reload, Shift - sprint
    Mouse 5 - Focus/Dash, Mouse 4 - Slam, Middle mouse - Melee
    G - throwable, H - swap throwable, X - Overdrive, C - Shatter, Q - Barrier, W - Vortex, Left Alt - Dash

    And finally... T - health infusion, Y - overdrive infusion, U - ability infusion


    I've been using GeForce Experience's Freestyle filters to add a sharpening filter to the game, and counter the blur.
    Works great, and really makes the game look a LOT better.
     
  8. haste

    haste Master Guru

    Messages:
    657
    Likes Received:
    101
    GPU:
    GTX 1080 @ 2.1GHz
    Sharpening already blurred image doesn't add any detail. If it's blurred by FXAA,TAA or MB, the image detail is already lost. Sharpening such image only makes the remaining detail more perceivable while adding another unwanted artifacts to the image.
    They should rather implement a proper reconstructive TAA with alternating pixel sample coverage. That's what Ubisoft games have been using since WD2.
     
  9. Stone Gargoyle

    Stone Gargoyle Ancient Guru

    Messages:
    5,744
    Likes Received:
    400
    GPU:
    GTX 1060 G1
    every time i think im starting to get bored i end up in a scrap with enemies that brings me right back in i had entered a base and found myself a little hidy hole at the top of a ladder and one by one the goon squad started climbin up to get at me which made dealin with them pretty easy even thyough they each take several shots to deal with armour playin on nightmare diff. i kept an eye on the red dots that indicate there positions around me and i could tell after some major effort and being downed once havin to use refib all my nades and health there was one single enemy left to deal with to clear the whole camp,, i waited at the top of the ladder as i had with the rest at about 50hp and right as i thought they was about to climb up n i was all set to use slam on him to finish in style a single grenade suddenly flew upward and landed at my feet...........and i died. yeah now i have to do it all again!!! not a single enemy had changed tactic all that much until the very last one lol! :oops::D

    anyone who says to me the ai is bad even tho its open world play it how its rly meant to be played on nightmare then come and tell me its bad again.
     
    Last edited: May 26, 2019
  10. Damien_Azreal

    Damien_Azreal Ancient Guru

    Messages:
    9,916
    Likes Received:
    1,062
    GPU:
    Gigabyte 1070 Ti
    Just saying what was said.
    It's one of the most requested "changes" for RAGE 2.
     

  11. DerSchniffles

    DerSchniffles Ancient Guru

    Messages:
    1,586
    Likes Received:
    102
    GPU:
    Zotac GTX1080ti

    Its too bright for you? Man, I feel like its too dark in a lot of areas. Ive heard others saying its too dark, but not bright as you say. How interesting....I also have my monitor calibrated for 2.4 gamma but in a dark room so that may be part of it but I do absolutely agree, a brightness slider would be very nice- its a basic function that should not have been omitted.
     
  12. The Janitor

    The Janitor Maha Guru

    Messages:
    1,208
    Likes Received:
    36
    GPU:
    GTX 1080 Ti
    Where are people making these requests? I'd make one for a resolution slider that scales up and not just down. And also a hotkey for the HUD toggle :D
     
  13. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    15,521
    Likes Received:
    1,526
    GPU:
    Sapphire 5700XT P.
    Yeah for the HUD I'm using Cheat-Engine plus a added in script for weapon/first-person FOV because it just looks better at a value of ~70 - 80 instead of 45 - 55 or what the default could be all up close and taking up most of the screen area.

    HUD/Free-camera. (HUD toggle also works for the photo mode.)
    http://fearlessrevolution.com/viewtopic.php?p=90018#p90018

    FOV plus weapon/1st person FOV. (I somehow managed to copy a existing script and add this in and then the value can be edited to what you prefer and just toggle on and done.)
    http://fearlessrevolution.com/viewtopic.php?p=90325#p90325
     
  14. The Janitor

    The Janitor Maha Guru

    Messages:
    1,208
    Likes Received:
    36
    GPU:
    GTX 1080 Ti
    Very cool thanks. But is there a way to add a hotkey and make it stick for the HUD toggle? I can add one in with cheat engine but I have to do that everytime I open it.
     
  15. Damien_Azreal

    Damien_Azreal Ancient Guru

    Messages:
    9,916
    Likes Received:
    1,062
    GPU:
    Gigabyte 1070 Ti
    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.
     

  16. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    15,521
    Likes Received:
    1,526
    GPU:
    Sapphire 5700XT P.
    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. :)
     
  17. AsiJu

    AsiJu Ancient Guru

    Messages:
    5,778
    Likes Received:
    1,245
    GPU:
    MSI RTX 2070 Armor
    Yep, sharpening and gamma / brightness sliders would be very useful.
     
  18. The Janitor

    The Janitor Maha Guru

    Messages:
    1,208
    Likes Received:
    36
    GPU:
    GTX 1080 Ti
    My bad, I accidentally made two CTs and was using the wrong one. Saving works :p

    May I also ask how exactly you added the weapon FOV to the CT?
     
  19. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    15,521
    Likes Received:
    1,526
    GPU:
    Sapphire 5700XT P.
    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.
     
    The Janitor and cerebus23 like this.
  20. The Janitor

    The Janitor Maha Guru

    Messages:
    1,208
    Likes Received:
    36
    GPU:
    GTX 1080 Ti
    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.
     

Share This Page