Jump to content

ygdrad

Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

950 profile views

ygdrad's Achievements

  1. The strange mouse behavior I was experiencing with the sensitivity changing all the time was also present in Space Hulk Deathwing, another Unreal Engine 4 game. In that game I was able to fix it by adding the following lines in input.ini [/Script/Engine.InputSettings] bEnableMouseSmoothing=False bViewAccelerationEnabled=False I'm guessing it can fix it in Fortnite too, but I'm not sure which file it needs to be added to in this case, input.ini is blank. Can anyone with more UE4 knowledge chime in?
  2. I thought it was because I was playing in windowed fullscreen, but it wasn't, the problem is still there. For me at least, the game keeps messing with sensitivity, lowering it randomly and every now and then increasing it. I have no idea what's making it do that as I have both mouse acceleration and smoothing off. I can stand still, do a rough cm/360 test in game and get heavily different results a couple times in a row. Usually ending up at. I'd be willing yo blame my logitech G402 mouse if other games weren't behaving just fine.
  3. There also is a mouse smoothing option in Epic Games\Launcher\Engine\Config\BaseInput.ini which may mess with sensitivity and these two lines which affect mouse sensitivity based on fov. bEnableFOVScaling=true FOVScale=0.01111
  4. I haven't compared it to UT4 but I did input the same value as I do for all games, 24.88cm/360. The calculator gives me the right value for Overwatch though. Edit: The shifting sensitivity seems to have been linked to windowed fullscreen mode. After switching to standard fullscreen the sensitivity stayed the same but the calculator still didn't match the cm/360. Edit2: nope, problem still present :/
  5. I set the sens in the config file, was supposed to get roughly 1.5 turns on my mouse pad, got 1.25. The only part of the config file that seems to be getting overwritten for me is the mouse acceleration. The calculator was telling me to input 0.041350, but after some manual fiddling around I ended up at 0.051020 to roughly get what it should be at.
  6. How did you change your FoV? Edit: I tried using the value from the calculator in the ini file and disabled mouse acceleration(gotta make the file read-only or it goes back on), but the result was a lower cm/360 than expected by a fair amount.
  7. Does this still work? I tried using this to set my FOV, but when I pressed the key nothing happened. I did edit the LUA file to remove all the sensitivity-related stuff since I already use a sens mod that lets me go lower than the default settings. What I'm left with is: fov = 103.3 fov = math.deg(2.0*math.atan(math.tan(math.rad(fov/2.0))*9.0/16.0*4.0/3.0)/65.0) managers.user:set_setting("fov_multiplier", fov) if alive(managers.player:player_unit()) then managers.player:player_unit():movement():current_state():update_fov_external() end
  8. I just tried converting my usual sensitivity to 7 days to die and the result was roughly 20-30% too high. Edit: after some manual fiddling around, the value giving me the result I wanted was around 0.045 when the tool said to use 0.05512320.
  9. Was the calculator fixed for PS2?
  10. The calculator says I need 2.4% sensitivity, but only mentions how to reliably change it by 5%. After testing, it seems 5% on the sensitivity bar can be further broken down into 15 different settings for 0.33 repeating percent per smallest change on the bar. Might want to lock the calculator's result to thirds of a percent and show the discrepancy from there. The results from the calculator also seem to be off by a fair amount on my end.
×
×
  • Create New...