SimplyOhSo Posted February 13, 2018 Share Posted February 13, 2018 (edited) Hello does anybody know why my rig isn't able to handle fnv modding. I had a computer that can max out games like battlefield 4 and titan fall 2, but it still lags on the strip with no mods. It's still a stable 60fps in other areas ,but when I throw on a simple enb and some mods it sh**s the bed all around, stutters, lag my rig just couldn't handle it. I've used nv 4gb, stutter remover, anti-lag, fake window mode, and all the tricks and bug fixes you can name, it helped to an extent but not as much as I see it helping others. I know it seems obvious and the recomendation would be simply to not play with enb and not too many mods, but I'm just dumbfounded how mod reviewers like Alchestbreach, NCRVet, and other people on the Nexus can play with harsh ENBS, high res texture packs, and a ton mods and still pull off a full 60 fps and I still couldn't even get it to run 20 fps on the strip vanilla. I'm a little bummed about it, I'd like to get into gaming and get a rig again but if I can't get New Vegas to work right I'm just about to stay away from it :(. PS: idk the specs to my old rig, haven't been home for a while but I can guarantee it should've good enough to handle fnv lol. Edited February 13, 2018 by SimplyOhSo Link to comment Share on other sites More sharing options...
SimplyOhSo Posted February 13, 2018 Author Share Posted February 13, 2018 (edited) And the enb was melenia enb any normal enb would destroy my game. Edited February 13, 2018 by SimplyOhSo Link to comment Share on other sites More sharing options...
sa547 Posted February 13, 2018 Share Posted February 13, 2018 This thread should be somewhere in the New Vegas subforum, but what's your full system specs? Download Speccy to determine what's your setup -- and you're supposed to know much about the PC in question. Link to comment Share on other sites More sharing options...
JimboUK Posted February 13, 2018 Share Posted February 13, 2018 You can't compare NV with modern games, the engine is a dog. I hover around the 100 frames a second mark in Assassin's Creed Origins maxed out at 1440p, I get 45 to 50 on the Strip in New Vegas (i7 6700k@4ghz, 32 GB DDR4, 1080ti) New games make full use of the hardware, this doesn't, look at the numbers, I can almost hear the GPU snoring. http://puu.sh/zmXzl/2eea9aeb32.jpg Link to comment Share on other sites More sharing options...
dubiousintent Posted February 13, 2018 Share Posted February 13, 2018 First you have to accept (as pointed out by jim_uk) the game engine is not up to modern game standards. A 'steady FPS' is the first expectation to go. It will fluctuate up and down all the time. Stop watching that counter and focus upon gameplay. While some have reported higher rates, anything from 20 to 60 FPS is "playable" for this game. The recommendation is to limit your FPS to 60 as that is the maximum the game was designed for. Larger/"hi-rez" textures require more pixels, and larger screen display monitors multiply that requirement in a non-linear way. While your hardware may technically be able to handle it, the game was published in late 2010, designed for Windows Vista with maximum screen displays of 1920x1080, with default image sizes of 512x512 pixels. The game engine texture cache tends to be the bottleneck: causing "stutter". Image size matters. A 4096 x 4096 image with 16 bit color resolution is 32 MB of data. If your screen is displaying 100 different models with textures that size, that's 3.2 GB of data just for the textures. Since a 32 bit program can only address up to 4 GB of data in total, you can see how trying to display a lot of high resolution models is going to run the game out of memory very quickly. (Thank you for the perspective madmongo.) Now, VRAM is not directly addressed by the program; it's controlled by the video card and can hide the actual addressing from the program, but you get the idea.Another thing to consider is that larger images take longer to pass through the video pipeline. When such larger sizes were not considered in the game design (and they weren't at the time), bottlenecks are to be expected.All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The following are "mitigations" that have been found to help some people.Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries.* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.* For ENB issues, see the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section in the same "Troubleshooting" guide.Reading from or writing to disk for any reason is the slowest thing the game does.As you can see, there are a number of things that can underlie your problem. If one of these doesn't fix it, I would be interested to hear about any eventual solution that does.-Dubious- Link to comment Share on other sites More sharing options...
JimboUK Posted February 13, 2018 Share Posted February 13, 2018 The one modern thing the game does benefit from is being put on an SSD, load times aren't improved that much but stutter is greatly reduced and the pause when the game autosaves with CASM is gone. Link to comment Share on other sites More sharing options...
SimplyOhSo Posted February 14, 2018 Author Share Posted February 14, 2018 (edited) I know the game enigine is old and can't handle that much, but I see some people being able to pull off the seemingly impossible with performance, while making the game look insanely good with enbs and high res textures (ex. The youtuber NCR Vet), so I thought there might be extra to do or I was just missing something... Thank you for the help everybody, I got a better understanding on the way the game and all works now. Edited February 14, 2018 by SimplyOhSo Link to comment Share on other sites More sharing options...
Recommended Posts