wogz187

I'm happy to hear that your solution helped your game run smoothly. The only reason I discovered the above solution is because FFS, frame-pacing, ect. didn't work for me. Keep in mind this is a catch-all solution for poor presentation. It works just as well at 60 FPS (on a 120 hz) monitor. So, if I plug my laptop into a external 120 Hz display, it will automatically play at 60 FPS without any further configuration. Regardless of what solution worked for you, this solution is fantastic for people playing on a laptop. Nothing to install, easy to implement, saves on battery, saves strain on the hardware and works on all Bethesda (and likely Gamebryo) games.

Hulk, "A mod called "Fallout 4 works" is the real answer. " The real answer to what? This post is the real answer to the original problem and the program you listed is a borderless fullscreen, which is not a solution at all.

Hey, I'm glad to hear the fix above helped smooth your FPS. If I understand the new problem correctly, you now see a lag/delay/FPS loss when opening workbenches, and FPS loss when you pass through fluorescent lights. These two issue may not be related. I would troubleshoot the one or the other first. When considering the lights, have you recently installed anything that effects lighting/lights or textures? Could you have accidentally changed something to affect those things in the .ini? As far as the workbench is concerned, when did this issue start? Was it a result of implementing the fix above? If the issue pops up all-of-a-sudden, it probably means you've changed something about the configuration. There are a couple articles on this page that seem to touch on your issue. Take a look around NEXUS for a fix.

Check out my post from today on "ipresentinterval". You may find helpful.

Interesting stuff: Borderless Windowed did not fix this issue. Setting "ipresentinterval" to "0" made much of the game run ~80 FPS with interior cells reaching hundreds of FPS and menus 1000's-- not an efficient use of energy. The default "ipresentinterval" of "1" was not smooth even when the FPS was exactly 60. Going to just about any interior cell would put the frame-rate at a consistent 60 with no variation (spinning around, moving, ect.) however the same "Jumpy" micro-stutters were present. I believe this means that FRAPS is reporting the "average FPS" but within that single second there could have been some frames rendered at 60 FPS and some at ~60 FPS which results in micro-stutter. That said, micro-stuttering was less as the FPS reached a solid 60. So the higher the current FPS the less the perceived stuttering. "ipresentinterval" is a ratio. 1= 1:1 monitor refresh rate. Therefor a 60 Hz monitor at "ipresentinterval= 1" is set to 60 FPS. Using "ipresentinterval= 2" on a 120 Hz monitor should make the cap, again, 60 FPS. This could be helpful if you have a slower PC connected to a nice monitor or TV. It also means you may be able to run Fallout 4 smoothly at 20 FPS on a potato, if you have one. (Change the monitor refresh rate to 40 and set "ipresentinterval= 2" to cap the game at 20 FPS. Same thing applies to a 48 Hz monitor at 24 FPS). Hypothetically, as long as the system can run the game ~25 FPS, this should make the experience feel much smoother.

High FPS but stuttering game-play? Tried every solution in the forum to no effect? Try this: When I first installed Fallout 4 I noticed that despite a high frame-rate (50-60 fps, 40 looking down on Diamond City), the display was stuttering all over the place. Walking while moving the camera made everything look like it was jumping around. I may as well have been playing at 10 FPS-- but the computer wasn't even breaking a sweat! Having had similar problems with other Bethesda games I immediately looked to the forums for a solution. The most common solution is setting the Fallout Prefs configuration file (fallout4prefs.ini) "ipresentinerval" to "0" to "unlock" the frame-rate, which it does. However this solution causes ridiculous amounts of screen tearing. Forcing the driver to VSYNC doesn't seem to improve the image much, if at all. So that "solution" was a non-starter-- just one messy screen to another, different, but equally bad messy screen. After trying a few other things I gave up and just dealt with it not displaying properly. Until I found this solution. "ipresentinterval" is in fact the solution but setting it to "0" can cause all kinds of problems-- VSYNC and animation sync not the least of which. The actual solution is to set "ipresentinterval" to a value of "2", which caps the frame-rate at 1/2 your monitor's refresh rate. How the solution works: Fallout can be a demanding game even on high-end hardware so if you system can't maintain a solid 60 fps you will have stuttering. If you are like me and see frame-rates between 40-60, setting "ipresentinterval" to "2" will lock the frame-rate at 30 and present a very consistent and smooth image. Trust me, 30 FPS smooth is better than ~60 FPS and stuttering. Plus the added benefit of putting less strain on your system which is ideal for laptops. There may be other issues setting "ipresentinterval" to 2 but none so far I have determined. Did this work for you? Did you find any bugs at interval 2? Have fun!

G'day Nexus! Trying to enjoy Skyrim but plagued by strange frameskipping. Firstly, take everything about performance and framerate and forget about it. The framerate is constant, even during the 'frameskipping'. This problem only happens around certain interior light sources-- Inns, for example, around the counter. While the framerate counter remains exactly the same, the actual onscreen output looks like a slideshow. Let me reiterate, capped (or not capped) at 60 FPS or 30 FPS it doesn't matter-- the frameskipping around these light sources is atrocious. Surely somebody has resolved this since the game was released. For some reason playing in a borderless window either fixes the issue or at least mitigates it to the point of it being playable, however borderless windows come with their own set of issues. I'd rather play the game properly in fullscreen. If you have a suggestion I'd love to hear it, unless your suggestion has something to do with "optimizing framerate" because if so you're not paying attention to what I've said and are likely looking for an excuse to get down to some good, old fashioned self aggrandizement. Thanks!

Still reading...

I've been reading forums today and I have to say that I'm a little bit disturbed. As I read- I notice the tone here is different than on the rest of the site. I like the new rating system. Further more- it's exactly what you asked for. Read a few pages of the: Yet another "we're banning you because you can't read" news post and you'd think that half of Nexus is psychic. Dark0ne gave us what we collectively wanted. Yay. My only suggestion- since I now see that some suggestions actually get implemented, would be that there is a system in place where the rating "cool-down" is removed from veteran accounts. You weren't born knowing how to give proper feedback. It's something you learn. Chances are, if you've made it to say, 200 hundred or so posts and haven't been shown the door, you could be considered a reasonable person. I've made mistakes. I broke the rules at least once that I can remember. We're all human. Here- I'll admit it: I rated Sharing & Caring Companions before I even tried it! I gave that file an instant 10 because I loved Companion Share and recruit for TES:IV so much- and then realized there were several errors when I play-tested. In this example, at least, it was a positive mistake. I rated high as opposed to mouthin' off. The result? I contacted ZableBlaze and we became friends whilst trying to solve the issues. All positive. Yay. The point? I learned from that mistake. SCC was the last file I ever rated before trying- and it was one of my first ratings. I guess what I'm saying is that I can be trusted to rate files appropriately and so can many other Nexus users I know- but we did not posses that talent on day one. You start with extremes and slowly find moderation. (or moderation finds you with it's ban-hammer!) The "cool-down" timer is like the 10 day waiting period for firearms in the US. We've (collectively) proven we aren't responsible enough to rate properly. Indeed we've been shooting one another far too often. You can usually earn back lost privileges though. We now have a rating system which is nearly idiot proof. It'd take some serious effort to screw up the whole Thumbs-Up, Thumbs-Down system. So with these new tools we should try to prove to Dark0ne that we can be trusted to follow the rules and behave- well, like adults. As a general rule: Always start your comment with something positive. If you can't come up with at least one solid positive point you have no business on the comments page. The three hours is perfectly reasonable (like the rest of the system) but my usual method is: a) check the file page out. b) install the mod. c) play-test the new mod (making detailed notes if necessary) and finally d) rate/comment Some mods can't even be properly assessed in Three hours. I'll use my own 187GURLZ as an example. If you were able to test out each feature in three hours it means you were smashing through it too quickly to give proper feedback. As the designer it takes me a couple hours just to unlock everything and that's using console commands. But for the most part the process described above usually only takes an hour or so (depending on the mod) and I like to get the comments out while it's fresh in my head. If I find something wrong I won't rate but instead leave an insightful comment and reserve rating for another day. There are, however, instances where I wait too long and forget- or I think I've rated but haven't. Since the new system has been in place I've been rating files in notepad- then pasting it after the timer runs down. There's nothing wrong with that but I think it affects the tone of my message. It's like I'm talkin' to notepad instead of a file author. So I don't want the "cool-down" timer to evaporate- I want a chance to prove it's not required for many avid Nexus users. Perhaps knowing that there is a reward for diligent, responsible ratings (I'm not gonna say "thumbings") will encourage new users to adopt this attitude more quickly. Dark0ne I apologize for the aforementioned trespass. I'll say 50 Hail Hammonds before bed tonight as penance. (oh and SCC really is 10/10 now!- uhm, I mean a thumbs up!)