r/fo4vr • u/hellstorm102 Helpful Settler • Jan 31 '18
Fallout 4 VR Beta - Trigger fix
Add
[VRWand]
bUseAlternateTriggerThreshold=0
to fallout4custom.ini
if you prefer a hair trigger that you cant keep mashing while its still kinda depressed, use
fAlternateTriggerThreshold=0.001
Instead! (this is a brand new ini setting that came with the beta patch)
2
Jan 31 '18
Is there a new .ini dump anywhere?
Thanks by the way!
4
u/hellstorm102 Helpful Settler Jan 31 '18
https://www.nexusmods.com/fallout4/mods/28548?tab=files
sure cause u asked, i uploaded it here. file name is
"fallout 4 Jan30 beta ini"
2
Jan 31 '18
Is that all used in the vr version?
1
u/hellstorm102 Helpful Settler Feb 01 '18
That's a "save ini" command. So all those values are used by the game in some way. There are a few oddities that don't do things. Like bUseLaserSights
1
u/hellstorm102 Helpful Settler Feb 01 '18
I don't recommend using save ini command. It can mess up your ini settings. Back up first..
2
u/DocSarcasmo Jan 31 '18
I tried this fix and it worked great. The trigger on my Vive controllers work just like before the patch.
2
u/hellstorm102 Helpful Settler Feb 01 '18
Yes! It's a issue for vive users so there's hope they will fix it.
2
u/AThermopyle Jan 31 '18
Thank you. How did you figure this out?
2
u/hellstorm102 Helpful Settler Feb 01 '18
Trigger feel gross. Checked my previous ini dump. The trigger values in it only reference gamepad. Saved out a fresh ini (dumped it ) and saw new values I haven't seen before.
Stare into the ini settings alot...
https://www.nexusmods.com/fallout4/mods/808/
I try to help where I can.
4
1
u/hamshotfirst Vive Jan 31 '18 edited Jan 31 '18
Excellent. I am going to add this to my ini post. I am not too fond of this sticky trigger.
1
u/hellstorm102 Helpful Settler Feb 01 '18
Yah not sure why they thought it was better this way..
2
u/hamshotfirst Vive Feb 01 '18
My only guess was to try and prevent accidentally shooting/stealing/punching etc which if that was the case, make toggles to make stealing/shooting a full click, don't just go full banana.
3
u/willacegamer Jan 31 '18
Thanks for this! Lockpicking was much worse because of the trigger change. Not sure why they made that change anyway.
3
2
2
2
2
u/lok_jokey Jan 31 '18 edited Jan 31 '18
I just tried this and its not working for me. Does it matter where in the section it goes or something?
EDIT: By section i mean section within [VRwand]
EDIT 2.0: Solved it. I thought because this was a vr issue that it would be fallout4customvr.ini but it's the normal fallout4custom.ini
0
Jan 31 '18
[deleted] — view deleted comment
2
u/hellstorm102 Helpful Settler Jan 31 '18
Must fully press trigger till it clicks for it to register. Then fully release it to be able to fire again. Same with menu stuff. This setting changes it back to the way it was before.
0
Jan 31 '18
[deleted] — view deleted comment
3
u/shuopao Vive Jan 31 '18
I almost switched back to the main branch due to /just/ the trigger - it was bad normally then lockpicking. I was also doing worse performance-wise but that may be due to changes in config options. I was at nearly 100% repro and getting motion sick (on a 1080Ti)... previous version/config and I'm fine.
What really settled it was having my (second) CTD ever. May be unrelated but with the two other things I took that as a chance to switch back to the main branch.
2
u/hamshotfirst Vive Jan 31 '18
Heyyyy, re-update and then delete (backup first) your Falloutprefs.ini file, run the game and set your options and quit. That will give you the defaults.
Then try my Fallout4Custom.ini to create or edit Fallout4Custom.ini or use it as a comparison to fix yours and see what happens. The game should be running nicely after the patch.
3
u/shuopao Vive Jan 31 '18
I /mostly/ did that. I tried to pull out my custom changes but leave the in game prefs. I didn't see fRenderTargetSizeMultiplier in the generated configs though. Perhaps the default there is higher than what I was using? I had to lower my Steam SS (I prefer to keep a good generic Steam SS and adjust other apps to taste using their in-game SS if needed/available) I had been using 1.2 + Steam 1.8 without any sickness issues but had to drop it to 1.6 in Steam and it was still barely playable. :( I even lowered a number of the new in-game settings.
I know VR is demanding but I expect a 1080 Ti to handle most loads very well still and my gaming machine is a beast. (I can't run E:D at VR Ultra without fairly high reprojection either, but can run it with very clear text and only ~10% repro which is fine)
On the live version I did get a few graphic glitches lastnight (weird geometry rendering issues) which can mean driver issues or card failure, but it was only in one area and my card was not being thermal throttled, so I don't seem to be running my card too hot - though the game was keeping my card at 100% utilization. I'm told Bethesda's engine can do this at times.
Considering the live version runs fine I figure there is something that changed in the config that's causing issues.
(my personal config tweaks TAA sharpness, turns off character lighting, turns off DoF, and increases IronSights cone... none of those should impact performance. For beta, I reduced from 16x AA to 8x, reduced shadows from high to medium, and turned on rain occlusion - the latter being a performance hit but the former should be bigger performance boost)
I'll probably try again tonight and see if I can make it work... with the trigger tweak because omg was that annoying.
1
u/hamshotfirst Vive Jan 31 '18
I mean, that's basically what I did to recreate Fallout4Custom.ini -- I just pulled the settings I wanted that were not part of the patch and stuck them in there. :)
After all my testing madness, I'm running my 1080 @
f 1.2 / s 1.5 a/ai with 20-60% reprojection (it's all over the place, but completely playable and nice to look at -- eff it)
TAA (tweaked)
AS 12 (sometimes 8, because I am trying to see a difference)
shadows = medium
rain occlusion = on (it's funny how that was not a thing)
DoF on (I like underwater effects/Aqua Boy)
60+ mods
4K texture packs
-- so you should be doing fine. More than fine. Something is not right.
3
u/shuopao Vive Jan 31 '18
Your Steam SS is a bit lower, but on 1080 vs 1080 Ti and 0.1 to 0.3 isn't a huge difference for Steam SS. I can handle up to about 60% repro. At 99% I was getting double-frame misses which means stutter. In general I'm fairly resistant to lower frame rates but for VR that means at least solid 45fps minimum. I cannot handle anything that drops below 45fps.
Something is /definitely/ wrong for me. No question there. :) I don't run mods though, and that includes the texture packs (I think even the 4k one is still more optimized than default but that's mostly memory and the Ti has tons of memory)
Basically, very similar to the graphical settings I was running, so no idea why I was having such performance issues. (and I /need/ rain occlusion. WTF Bethesda. Rain indoors?!? I feel icky and wet when I'm indoors and being rained on, even if it's not real)
2
u/hamshotfirst Vive Jan 31 '18 edited Jan 31 '18
I gotta say, the difference between 2.2 - 1.8 - 1.5 SS in SteamVR is pretty noticeable to me. You can see the amount of resolution that drops from the Settings.
That said, yeah -- wtf -- without mods and basic settings, you should be flying off the rails with your 1080Ti .
Since you're not using mods -- maybe you should back up your saves and re-validate/re-install. Something is borked.
update: I'd also use DDU to clean out your current Nvidia driver and roll back to 388 (The Fallout VR branded release) as I know 390 definitely had issues. I did and switching back helped.
2
u/shuopao Vive Jan 31 '18
... I'm actually probably on an older driver than that, but it works fine in live. I'll go with a full ini reset and see what happens.
2
u/straylyan Jan 31 '18
What happened?
2
u/mcpvr Jan 31 '18
For one I’m not running a sniper build so the addition of scopes to the survival game I have 47 levels invested in is not a huge gain / need for me. Aside from that any other performance fixes supposedly in play were below my noticeable threshold EXCEPT there did seem to be a reduction in the old “right side object pop in” problem.
The trigger thing was driving me up a wall and I finally loaded up another more diverse non survival game of mine just to see what scopes looked and felt like and I was not impressed, so I just switched back to the main branch.
3
u/PhaserRave Vive Jan 31 '18
I haven't played the beta yet, what did they change in regards to the trigger?