Support NeoGAF

[JudgmentJay]

Running in borderless windowed caps it at 60 doesn't it?

I have fraps open and it never goes past 60, even in the menu's, whereas if I run in fullscreen the menu's will go up to 400+ fps.

As long as it's capped to 60 fps it can't bug out can it?

I'm pretty sure the problems that arise from that tweak occur when you drop below 60, not go above it. They may occur regardless of framerate, not sure. You only need to read the last few pages in this thread to see what a bad idea it is.

Regarding stuttering, I tried various methods of capping my FPS at 60 to eliminate the stutter, but using RivaTuner alongside vsync is the only thing that fixed it for me.

 

[HooYaH]

Nobody's wondering when Bethesda is gonna patch the game or is everyone content with the communities efforts?

They probably all went on vacation and patch won't be till next year. I do hate holiday games nowadays due to so little dev support from Thanksgiving, Xmas, and New Year.

 

[spannicus]

They probably all went on vacation and patch won't be till next year. I do hate holiday games nowadays due to so little dev support from Thanksgiving, Xmas, and New Year.

Got ya.

 

[Spinifex]

For any AMD users interested, seems worth upgrading to the new drivers.

 

[chekhonte]

The titan x can run this just fine in 4k with everything ultra but AA on low.

 

[Orthogonal]

I noticed my framerate started to dip a bit in the last day or so. Just checked and my God Ray settings got turned up. However, everytime I try to lower them, the game resets it back up. Same goes for any other setting. I cant turn any setting down. They all reset back to Ultra.

 

[Stiler]

I'm pretty sure the problems that arise from that tweak occur when you drop below 60, not go above it. They may occur regardless of framerate, not sure. You only need to read the last few pages in this thread to see what a bad idea it is.

Regarding stuttering, I tried various methods of capping my FPS at 60 to eliminate the stutter, but using RivaTuner alongside vsync is the only thing that fixed it for me.

Yeah, after reading some previous pages I decided to not use it, not worth game breaking bugs.

I sometimes get dips to 55'ish or so and I'm not going to risk game breaking bugs.

Just going to have to deal with the micro stuttering and hope for a patch or something to fix it.

Though with it being a problem in all the previous games I am not holding my breath.

 

[Aurongel]

Uhh so yeah, my fov keeps resetting itself to console vomit levels no matter what changes I make to the ini file. I had this set up and working fine but for some reason today it just reverted and won't change back. Typing fov 100 into the console causes it to temporarily widen but it reverts immediately.

This is game breaking for me so if anyone has any tips then I'm all ears.

 

[Spinifex]

Uhh so yeah, my fov keeps resetting itself to console vomit levels no matter what changes I make to the ini file. I had this set up and working fine but for some reason today it just reverted and won't change back. Typing fov 100 into the console causes it to temporarily widen but it reverts immediately.

This is game breaking for me so if anyone has any tips then I'm all ears.

Put the settings you want into the INI and set it to read-only. The game constantly wants to change some settings back to their default setting, it will always try to enable vsync, for example.

The downside of this is if you want to change settings in-game, like changing the difficulty, it won't preserve after quitting.

 

[Ragona]

2500k @4,3
1600mhz 8 gb ram
390 nitro

Playing with godrays low, shadow distance medium rest on ultra. Getting pretty heavy drops to low 40s in higher places in the city. Got newest drivers installed.
Is the 2500k reaching its limits now? Or are there any fixes that help without making the game look like shit? Thanks in advance.

 

[Ogimachi]

I'm just one case, could be something specific to my PC, but it might help someone:

I was getting the constant invisible weapon glitch (no weapon in 1st person, can't shoot or do anything until it appears) and textures were taking way too long to load, so I tried every .ini tweak, ENBoost and whatnot, but nothing fixed it.
In the end, it was the fact I was running both Shadowplay and the Rivatuner OSD from Afterburner in-game. I tried turning them off separately, and turns out the problem was definitely the OSD. I know this sounds very odd, but I tested it closing and loading the game 10 times turning it on and off, and the results were the same 100% of the time.
With no afterburner sometimes I still get a small hiccup while switching weapons, but the issue itself seems to be gone. I'm now using only ShadowPlay and Inspector to tweak the GPU.

 

[Aurongel]

Put the settings you want into the INI and set it to read-only. The game constantly wants to change some settings back to their default setting, it will always try to enable vsync, for example.

The downside of this is if you want to change settings in-game, like changing the difficulty, it won't preserve after quitting.

Tried that, set FOV to 100 in the .ini and set read-only permissions to the file and the game starts like this:

Entering fov 100 into the console temporarily widens the FOV from the crummy default:

 

[Mad Season]

Either use Nvidia Inspector to limit specifically the game's framerate , or download MSI Afterburner.

MSI Afterburner will install a program called RivaTuner, which you'll be using to cap your framerate. You'll need to enable the RivaTuner system tray icon to gain access to it, which you'll do by going into Afterburner's preferences and into the User Interface tab, unchecking the 'Single tray icon mode' option. This'll add the pink and blue RivaTuner icon into your system tray. Then just open that up and you'll see an option for 'Framerate limit'. Voila! You're all set.

no need for afterburner. Just install rivatuner separate

http://www.guru3d.com/files-details/rtss-rivatuner-statistics-server-download.html

 

[Soodanim]

Uhh so yeah, my fov keeps resetting itself to console vomit levels no matter what changes I make to the ini file. I had this set up and working fine but for some reason today it just reverted and won't change back. Typing fov 100 into the console causes it to temporarily widen but it reverts immediately.

This is game breaking for me so if anyone has any tips then I'm all ears.

I gave up using the console and ini files and just used the tool at Nexus Mods. Top rated tool, does the trick for me.

I never quite got the refreshini thing, but maybe that's because I don't know exactly how it works. The end result is nothing new, but maybe if I knew its inner workings I'd understand why.

 

[Renekton]

2500k @4,3
1600mhz 8 gb ram
390 nitro

Playing with godrays low, shadow distance medium rest on ultra. Getting pretty heavy drops to low 40s in higher places in the city. Got newest drivers installed.
Is the 2500k reaching its limits now? Or are there any fixes that help without making the game look like shit? Thanks in advance.

The INI fixes are hit or miss so far.

One idea is to upgrade your RAM speed to 1866 or more, as benchmarks show the game bottlenecked at 1333 and 1600.

 

[texhnolyze]

For any AMD users interested, seems worth upgrading to the new drivers.

Installing!

 

[Amneisac]

OK, this freaking terminal glitch is really dragging me down. I've tried the one fix where you change a setting in the txt file and nothing. I don't want to mess with any third party programs to lock the framerate. Any other options?

I've also verified the game files twice and uninstalled/reinstalled once. Nothing changes.

I was stuck on a quest for a while yesterday because I couldn't escape a terminal after I had to use it to open a door to progress.

If your refresh rate is 60 play in borderless windowed mode. If it's over 60 set it to 60 in Windows and okay in borderless windowed mode.

 

[Amneisac]

Tried that, set FOV to 100 in the .ini and set read-only permissions to the file and the game starts like this:

The console command is:
fov 100 100
or else it doesn't stick when you close console. There are also 4 files where I added the FOV changes before they stuck.

 

[Takuan]

The INI fixes are hit or miss so far.

One idea is to upgrade your RAM speed to 1866 or more, as benchmarks show the game bottlenecked at 1333 and 1600.

I don't think my motherboard even supports speeds faster than 1600. Is there any point to upgrading in this case?

 

[TheExhaustedWalrus]

I installed the new AMD drivers and I've seen a noticeable change in FPS and performance in general.

 

[Red Hood]

Can 280X owners download the new AMD driver and report how much better exactly it's running now on 1080p maxed out? I'd appreciate it!

 

[Takuan]

I installed the new AMD drivers and I've seen a noticeable change in FPS and performance in general.

Which gpu, bredda? I'm on a 7950, so I'm eager to know what sort of boost old gpus will get. I'm out of the country right now and can't see for myself until Saturday.

 

[wild_fire987]

I haven't seen anything on this in the past few pages. Game runs great, but I get a lot of textures (specifically cars, building sides, billboards) that look straight out of the N64 era, I have texture quality set to ultra and have tweaked a few settings, but cannot for the life of me figure out why it's doing this.

Anyone have any suggestions or can point me towards a solution, or is this going to have to wait for a patch?

 

[smokeandmirrors]

I installed the new AMD drivers and I've seen a noticeable change in FPS and performance in general.

Same. random drops in certain locations aren't as frequent anymore for me.

 

[bobeth]

I don't think my motherboard even supports speeds faster than 1600. Is there any point to upgrading in this case?

No

 

[x3sphere]

I've seen people talk about issues at high refresh rates (100 Hz+), I just tried 90 Hz and it seems to be running fine though.

 

[AstuteClass]

Here's mine:

https://www.youtube.com/watch?v=XVHutswfem4

Ultra everything. Get 60FPS around my base here. When going out into the Wasteland, it can drop to low 20s.

Got i7 4770k, 16GB RAM, EVGA 780Ti SC.

Thinking of buying a used 780Ti just to run in SLI.

Or I might go for a new 980 Ti. Thoughts?

 

[Corpekata]

I've seen people talk about issues at high refresh rates (100 Hz+), I just tried 90 Hz and it seems to be running fine though.

The game's physics and whatnot are tired to the FPS. If you do things like jump at 144hz/FPS it's noticeably shorter than a jump at 60. And you also can get stuck in computer terminals.

Probably affects a lot of other things that would need further analysis, though I think the terminal bug has kept most from looking into it too much anyway.

 

[Renekton]

I don't think my motherboard even supports speeds faster than 1600. Is there any point to upgrading in this case?

No XMP?

(Edit: oops ignore this)

 

[Rushersauce]

Downloading the new AMD Beta drivers. Will report soon (r9 390)

 

[0.1.1.2.3.5.8.13.21.34.55]

So what's the word on SLI? Still no official support.

 

[wanderjahr]

So what's the word on SLI? Still no official support.

https://twitter.com/ManuelGuzman/status/666672147541065728

 

[Rushersauce]

Well... performance seems a little better. But it was obvious I wouldn't be able to crack shadow distance to Ultra and expect locked 60fps.
To do that, Bethesda needs to put some work it its code.

 

[Dusktildawn48]

I'm using a controller. Is there any way to up the sensitivity above the defaults max setting?

 

[Leetums]

No matter what i do i cant get the game to not dip to 25 in spots. No matter how low the settings. r9 280x fx8320 @ 3.8ghz 8gb ram. Good thing i know battlefront runs great.

 

[Rushersauce]

No matter what i do i cant get the game to not dip to 25 in spots. No matter how low the settings. r9 280x fx8320 @ 3.8ghz 8gb ram. Good thing i know battlefront runs great.

That's normal on any pc. Yes, even guys with gtx980ti are having problems with this mess.

 

[zXe]

Has there been any news on a new patch/nvidia driver? just curious as they (bethesda) must be aware of the many issues on pc atm.

 

[JudgmentJay]

I'm using a controller. Is there any way to up the sensitivity above the defaults max setting?

A related question, is there a way to remove the huge dead zones on the 360 controller in this game?

 

[Dick Justice]

Welp, good thing I had a save before entering the subway containing Vault 114. If anyone else encounters the bug with it not opening, you need to disable the ifpsclamp setting if you're using it before entering the area (also, disabling it brought back the terrible stuttering).

 

[seat]

For any AMD users interested, seems worth upgrading to the new drivers.

This saved the day for me. I was getting a weird occasional snow-like graphics glitch (sort of looked like gray diagonal diamonds) when playing on my new 390X. I seriously thought I'd have to get an RMA, but after the new drivers the glitch has disappeared completely. Lucky night!

 

[Karak]

I hilariously keep returning here hoping there is a fix for my frame pacing issue lol. Hope is a sad thing. bahahaha.

 

[statham]

Anyone play this on a FX-8320 or 8350 with 7850?

 

[jorimt]

Welp, good thing I had a save before entering the subway containing Vault 114. If anyone else encounters the bug with it not opening, you need to disable the ifpsclamp setting if you're using it before entering the area (also, disabling it brought back the terrible stuttering).

Yup, I read your previous post about how you were having an okay time with iFPSClamp. A couple of us had already been discussing the Vault 114 bug a little before that, so I wasn't sure if you had seen it, and found a way around it, or simply disregarded it.

As you said, the stutter can be really bad without the tweak, but I found a combination of fullscreen (not borderless), a 60 FPS cap via RTSS, vsync forced in Nvidia Inspector (game's built-in vsync disabled via ini), along with max pre-rendered at "3," heavily reduces it, at least on my 980 Ti/4770k.

The max pre-rendered frames (for Nvidia users) was what really seemed to help though. I originally had it set to "1," but seeing as this game relies mostly on CPU processing, that actually introduced even more stutter. A setting of "3" seems to give the CPU/GPU communication more breathing room, and thus less perceivable stutter.

 

[Vex_]

That's normal on any pc. Yes, even guys with gtx980ti are having problems with this mess.

Well that's because this game isn't gpu bound, right? You could have a gtx 1020 and it still would be shitty.

Thought it was cpu + ram speed that mattered the most?

 

[bobeth]

Here's mine:

https://www.youtube.com/watch?v=XVHutswfem4

Ultra everything. Get 60FPS around my base here. When going out into the Wasteland, it can drop to low 20s.

Got i7 4770k, 16GB RAM, EVGA 780Ti SC.

Thinking of buying a used 780Ti just to run in SLI.

Or I might go for a new 980 Ti. Thoughts?

Honestly? Going with the 980ti would give you a whole Gb of additional vram, and avoid the headaches SLI often brings..

 

[Takuan]

No XMP?

(Edit: oops ignore this)

Yea, I'm pretty sure my mobo is an Asus P8z68 LX and it doesn't state anywhere on the product page that XMP is supported. No biggie. I just looked up prices on some DDR3-2400 modules and I'm not going to pay ~$150 for a performance boost in one game, anyway, since my next desktop is likely going to require DDR4.

Hopefully the driver update provides some sweet gains, but I'm not particularly bothered by the performance as it is.

 

[Rushersauce]

Well that's because this game isn't gpu bound, right? You could have a gtx 1020 and it still would be shitty.

Thought it was cpu + ram speed that mattered the most?

The game is a fucking mess, yes. Memory perf. Is overblown since people with ddr4 are reporting the same issues as people with lower frecuency ram. It's a hit or miss when it comes to perf.

 

[Wag]

Terrible port. I am getting random crashes to the desktop- it's totally unplayable for me on my 3way 980ti SLI setup.

 

[Vex_]

Terrible port. I am getting random crashes to the desktop- it's totally unplayable for me on my 3way 980ti SLI setup.

Wait. Sli isn't even officially supported last I heard?


...is it?

 

[Dick Justice]

Yup, I read your previous post about how you were having an okay time with iFPSClamp. A couple of us had already been discussing the Vault 114 bug a little before that, so I wasn't sure if you had seen it, and found a way around it, or simply disregarded it.

As you said, the stutter can be really bad without the tweak, but I found a combination of fullscreen (not borderless), a 60 FPS cap via RTSS, vsync forced in Nvidia Inspector (game's built-in vsync disabled via ini), along with max pre-rendered at "3," heavily reduces it, at least on my 980 Ti/4770k.

The max pre-rendered frames (for Nvidia users) was what really seemed to help though. I originally had it set to "1," but seeing as this game relies mostly on CPU processing, that actually introduced even more stutter. A setting of "3" seems to give the CPU/GPU communication more breathing room, and thus less perceivable stutter.

Yeah, I had noticed some talk about vault doors bugging out, so I made a save beforehand just in case. I'll have to try that pre-rendered frames thing. Remember testing it out in GTA V, and the input lag was pretty bad.