I'm thinking about picking up a physical PC copy. My understanding is that it installs about 5GB and activates and downloads the rest via Steam. Once that's done, do I still need my disc, or can I chuck it?
I'm thinking about picking up a physical PC copy. My understanding is that it installs about 5GB and activates and downloads the rest via Steam. Once that's done, do I still need my disc, or can I chuck it?
You can chuck it. Once the cd key is tied to your Steam account, game is yours forever.
You can chuck it. Once the cd key is tied to your Steam account, game is yours forever.
I need some visual confirmation of this shit man. If that's the case I may as well just save a few dollars, get a GMG key, and download the 24 gigs overnight. I ask because Bethesda doesn't usually do this.
Hrm. Game worked for me this morning after installing the nvidia game ready drivers.
Just got home, the game installed an update, and now it just goes to a black screen and hangs.
Both modes work for me, but full screen is microstutter hell. You're better off with borderless windowed mode.Well, it will work in windowed mode but not full screen.
What do I do if I am getting stuck in furniture or terminals while playing Fallout 4 on PC?
Published 11/10/2015 07:57 AM | Updated 11/10/2015 01:49 PM
Many issues related to the game's physics can be traced to manual tweaking of the game's .INI file in order to try and uncap or raise the game's max framerate. These types of issues can also occur if the game/launcher incorrectly detects monitors that are set to refresh rates above 120Hz as being set to 120Hz.
In general, you are advised to keep the game's default settings and continue to play the game with a 60fps cap. The fps cap that the game uses is determined by the your monitor refresh rate (typically 60Hz or 120Hz), and dividing it by the "iPresentInterval" value.
Please note that if your monitor is set to 60Hz, the iPresentInterval value in your .INI file should be "1", and if your monitor is set to 120Hz, the iPresentInterval value should be "2". Setting it to "0" uncaps the framerate and can cause the issues mentioned above. If your monitor is set to a value larger than 120Hz (such as 144Hz), they are advised to set their desktop refresh rate to 120Hz instead, when playing the game.
Bethesda have made an official comment regarding the 144hz display fuckup:
So, if you have a 144Hz display (or higher), you are advised force 120hz mode ...![]()
Fuck that. 120Hz-mode looks like crap :/
I cannot get this to run well. I don't know WTF is going on, because it SHOULD be running decently. I even jumped it down the the medium presets and it's just... stuttering all over the place.
I have the latest nVidia drivers, 16 gigs of RAM, a 970, and an i7 4790k. It just keeps stuttering CONSTANTLY. HELP PLEASE.
I'm going to roll back to some older drivers and see if that helps.
Now that I'm getting into the city I'm seeing a lot more drops. Are these performance related, or is the game just janky like it is at Lexington?
It seems to have issues introducing new content into cells in particular and so areas with more entities have higher number of drops.
As for my issue. I think I am done trying. Just going to run it on the midspecced PC from now on. Such an odd problem and never experienced in a game prior.
How do I get Windows Borderless to go full screen? Right now its in the top left of my screen.
Same. It's small as fuck. Not sure it really matters though, because it's still not a smooth framerate.How do I get Windows Borderless to go full screen? Right now its in the top left of my screen.
Now that I'm getting into the city I'm seeing a lot more drops. Are these performance related, or is the game just janky like it is at Lexington?
Is anyone playing with uGrids increased? How's it working? Are saves still tied to the setting you choose?
It seems to have issues introducing new content into cells in particular and so areas with more entities have higher number of drops.
As for my issue. I think I am done trying. Just going to run it on the midspecced PC from now on. Such an odd problem and never experienced in a game prior.
I just discovered some kind of bug.
It's been bugging the heck out of me that my FPS will not go above 48fps no matter what setting I put it on. I have a 1440p Korean monitor OC'ed to 96 hz. 48 is half of 96. So strange it is halving my FPS.
Please note that if your monitor is set to 60Hz, the iPresentInterval value in your .INI file should be "1", and if your monitor is set to 120Hz, the iPresentInterval value should be "2". Setting it to "0" uncaps the framerate and can cause the issues mentioned above. If your monitor is set to a value larger than 120Hz (such as 144Hz), they are advised to set their desktop refresh rate to 120Hz instead, when playing the game.
Is anyone playing with uGrids increased? How's it working? Are saves still tied to the setting you choose?
Bethesda have made an official comment regarding the 144hz display fuckup:
So, if you have a 144Hz display (or higher), you are advised force 120hz mode ...![]()
From an earlier post:
So I shouldn't bother trying to tweak my settings to get it to not drop?
Ok so what do I do for 96hz? Set it to 2?
Can't really skim through this whole thread but can anyone sum up for me how the performance is for this game (I have a 970). I'm gonna pick it up from Target and I wasn't sure whether to go PC or Xbox.
Also does it come with a code in the box or do you have to install it (I lack a CD Drive)?
So does that mean setting the interval thing to 2 set the frame rate cap to 120?
It's probably set to 2 already, hence why your fps is halved. If you set it to 1 it should lock your fps at 96, but may cause physics problems.
I think I give up. I have tried running the game in low even, and it can't stop stuttering. I don't know what to do. It's infuriating.
I have an i7 4790k, a 970, and 16 gigs of ram. It shouldn't be running like this.![]()
I think I give up. I have tried running the game in low even, and it can't stop stuttering. I don't know what to do. It's infuriating.
I have an i7 4790k, a 970, and 16 gigs of ram. It shouldn't be running like this.![]()