Vypir

Obviously, the more texture mods you have, the bigger this problem will be. I don't use the vast majority of the mods recommended by S.T.E.P. - I seem to prefer a more vanilla experience than most people. Most of the textures in my data folder are for armor mods, and I also have SMIM. So far that hasn't been enough to necessitate running a texture optimizer on my Data folder. Have you tried using the vanilla normal maps? Whoever came up with that idea deserves a cookie.

+1 on texture optimization. I use a GTX 460 768MB. After I installed the official Hi-Res DLC, I would get stuttering (disk thrashing) after varying amounts of play time. Switching to post-process anti-aliasing (SMAA or FXAA) and using Bethesda Hi-Res DLC Optimized (Hybrid + Vanilla normal maps) seems to have eliminated this problem. I have not used the "Optimize Textures" program, though. Being able to play on Ultra (tweaked) using decent anti-aliasing and quality ambient occlusion, with so little VRAM, is wonderful.

I know this doesn't answer your question, but Tom's Hardware had a good piece about using large amounts of RAM for gaming. It looked at using RAM disks for swap and temp files. You might want to give that a try and see if you can eke out some more performance with all that extra RAM available.

Hi all, I recently discovered a problem and a fix that I would like to share. I'll try to keep it as simple as possible. A) Problem: When using Nvidia's Adaptive Vsync, tearing would occur at the same place on the screen, every frame, at 60FPS.When using Nvidia's Standard Vsync under the same conditions as #1, framerate would drop to around 40FPS with what felt like small stuttering.B) Additional information: The problem was most noticeable and easily reproducible when moving around the world map with WASD keys. (The only map mods I use reduce the size of markers and remove the HUD.)Both problems would only occur when RCRN was being used. Everything was perfectly smooth when I used the Pause button to switch to vanilla.Maximum Pre-Rendered Frames was set to 1 via the Nvidia driver.C) Solution: When I set Maximum Pre-Rendered Frames to 2, 3, or Application-Controlled, the problem disappeared and everything was perfectly smooth with RCRN enabled. I don't have the option to set it to 0. Mouse lag was not noticeably affected, and VRAM usage has only gone up a few megabytes, if at all.Edit: Actually, after more play, I realized that some mouse lag was introduced when increasing pre-rendered frames from 1 to 2. See my update. D) Other thoughts: I suspect this may be a problem with post-process injection altogether and not just RCRN. I had the same problem as #A.1 when using the SMAA injector and framerate limiter (60 FPS cap via Nvidia Inspector). I don't use SMAA anymore but I may go back to it for further testing. Basically, I suspect that vertical synchronization is designed with the expectation that post process injection will NOT be used and that it can throw the frame buffers out of sync even though it still limits the framerate. This is just an educated guess.I don't recall having this problem when I used a post-process injector that simply limited the framerate to 60. It showed up when I ditched that injector for the SMAA injector, and again when I ditched SMAA for RCRN. Perhaps controlling Vsync via post-process injection will ensure that the frame buffers are synchronized?E) My Specs: