[BUG] Stuck after using terminal

Post » Fri Nov 27, 2015 9:00 am

Like I said, that's a different problem entirely. It would probably be a good idea to make a list of locations where that happens and make a dedicated bug thread for it. Personally, I've had the most trouble getting stuck when trying to use a terminal because of Dogmeat getting in the way of the automatic movement toward the terminal. I can't get control back and Dogmeat won't move out of the way so I am forced to reload.

User avatar
Amy Smith
 
Posts: 3339
Joined: Mon Feb 05, 2007 10:04 pm

Post » Thu Nov 26, 2015 5:34 pm

Had the same issue. I limited fps to 60 and the issue has not recurred.

User avatar
Etta Hargrave
 
Posts: 3452
Joined: Fri Sep 01, 2006 1:27 am

Post » Fri Nov 27, 2015 8:12 am

When I did all of the above, I was having 0.1 second delay or something on my mouse movement. It was very bad. Maybe this is what they call input lag? I don't know.

Anyway, here's how I fixed it:

I did all of the above in my first post but added/changed these:

Nvidia control panel:

*Instead of using the standard display technology, I enabled G-sync

*Turned off V-sync

*Max pre rendered frames to 1 (be sure to enable the right one... there's one similar option for VR)

*Enabled threaded optimization

*I then set iPresentInterval=0 (look in the steamcommunity site guide on how to do this)

*I set all 4 of the .ini files to read only. Rightclick the files on your computer, go to preferences. There you can tick a box so no program (or you) can make any changes to it... I don't know if this is required, but I just did it to make sure (someone else suggested this). Remember that if you're making any changes to the options in game, they will be changed for that session, but if you quit the game and go in again, it will be restored to what you had before you set the .ini files to read only. To unset them to read only, Just untick the box.

Now my gameplay experience is butter smooth and enjoyable :) The mouse movement is very responsive like it should be and I've not had any huge issues for many hours. The only issue I have now is that when I'm lockpicking it's super fast and I break my bobby pins super fast, but I've managed to pick all novice locks anyway (can't pick advanced locks yet). It helps to have some experience from previous Bethesda games on how to pick the locks :P

My frame rate isn't capped, but my frame rate is around 60-80 fps and I guess that's why everything is working. When I pick locks or use terminals, the fps shoots up to 300 or something though. But I havn't got stuck anymore. But now I just press F5 to quicksave before trying anyway.

And I guess my fix won't help everyone, but if you have a G-sync monitor with 144 hz, 2560x1440 and a GTX 970 I think this might help you. If you have a stronger graphics card than me, you will get even more frames per second and there's a higher chance the problems will appear.

User avatar
Jesus Duran
 
Posts: 3444
Joined: Wed Aug 15, 2007 12:16 am

Post » Thu Nov 26, 2015 8:28 pm

Yeah this doesn't work. My desktop is set to 120Hz and iPresentInterval set manually to 2 and i still get stuck. I think this is a different bug than just getting stuck in furniture and physics glitches. Really odd to have a game be buggy because your hardware is TOO good. I want to play this game badly but I don't want to be reloading saves every 10 mins.

User avatar
Danger Mouse
 
Posts: 3393
Joined: Sat Oct 07, 2006 9:55 am

Post » Fri Nov 27, 2015 7:23 am

I think you might be talking about another bug. The terminal bug results in player controls being disabled after leaving the terminal. You can still move the camera around but the mouse sensitivity is doubled and your character does not move with the camera (it's the same camera mode as when you're frozen in the vault.) You are also unable to interact with anything because the interaction target is based on where your character is looking, not where the camera is. This bug is strictly caused by high framerates and capping the framerate below 100 fps, no matter the iPresentInterval setting prevents this from happenining 99% of the time.

User avatar
aisha jamil
 
Posts: 3436
Joined: Sun Jul 02, 2006 11:54 am

Post » Thu Nov 26, 2015 9:53 pm

No, I was referencing the same bug as you described. Go to terminal, enter with E, exit, WASD is dead. I can jump and look and thats all. Someone suggested that iPresentInterval and 120Hz thing from Bethesdas sticky. Just saying it didn't work is all.

User avatar
Stephanie Valentine
 
Posts: 3281
Joined: Wed Jun 28, 2006 2:09 pm

Post » Thu Nov 26, 2015 6:12 pm

Ah ok. Does iPresentInterval=2 limit you to 60 fps at 120Hz?

User avatar
Mr. Allen
 
Posts: 3327
Joined: Fri Oct 05, 2007 8:36 am

Previous

Return to Fallout 4