Jump to content

NilValue

Premium Members
  • Posts

    63
  • Joined

  • Last visited

  • Days Won

    2

NilValue last won the day on June 7 2018

NilValue had the most liked content!

Recent Profile Visitors

1,361 profile views
  1. Just checked the calculator and it seems perfect now
  2. Updating the input.ini works for me, just as the calculator states. However, there is no need to set different values for vertical and horizontal mouse since settings horizontal==vertical makes it 1:1. I have not tried actually making changes to the FG.MouseSensitivity value in the file.
  3. Hi I have started to play Satisfactory and noticed the following things: The calculator gives me different values for X and Y axis to configure in the config file. However, I do not think that this actually correct, it feels like (and I also measured it) it already is at 1:1 vertical to horizontal sensitivity. Also, the mFOV value does not exist in the config file (seems to be called "FG.FOV" now), while the bEnableMouseSmoothing=False key-value is not contained in the file either. I also think that there is a new mouse sensitivity setting available in the GameUserSettings.ini: "FG.MouseSensitivity". I think that the calculator configuration is very outdated
  4. Is that intended? Does the game need me to do that? I would expect that this would result in different sensitivities for vertical and horizontal (which I do not think anyone would want, at least not by default).
  5. Btw, some additional info: - The Steam version seemed to be fine (Vulkan and DirectX). I bought it on Ubi Store directly and after installing the Ubisoft Connect Only version, the raw input seems inconsistent. - I play the Vulkan version
  6. 1000hz mouse, raw input seems bugged to me when I measure it (360° turn distance is inconsistent). Can anyone here confirm this?
  7. Ah damn, game didn't actually apply the FOV settings, just noticed. Sorry, my bad /closed
  8. The configuration for Insurgency Sandstorm states that when I set the FOV in the settings to 100, then it would actually be 107 on a 16:9 screen. I just measured this and it is wrong. When I set it to 100° ingame, it is actually 100° horizontal FOV on my 16:9 screen.
  9. Oh I see that now... The problem is then that when you switch between config and ingame, the settings of the other dropdowns change, too. From a UX perspective, wouldn't it make the most sense if the calculator retained the same settings that it had when first selecting the game?
  10. Bug is as follows: 1.) Select any game to convert from. 2.) Select to convert to Rainbow Six Siege 3.) Switch from config file to ingame 4.) Switch back to config file. Result: The "Aim" dropdown does not contain the option "All" anymore.
×
×
  • Create New...