Jump to content

LOD Problems


Dubik123

Recommended Posts

Most computer shops don't keep older versions of any hardware components around long after newer ones come out. It's just good business. Not more than a generation or so, and only because they are still "stuck" with that stock on hand. Your current hardware (including the motherboard), if it is old enough, may not be compatible with the newest technologies being built into the current line of motherboards, cases, disk drive connections, and "addon card slots". In addition, power requirements always increase as performance improves. When you upgraded your video card, it required more power than the older model. That probably was within the range of your older power supply, but a new motherboard might push it over that range. Upgrading any one component runs a risk of creating a "cascade of purchases" to bring everything in line.

 

That is all I am cautioning you about: it may not be as simple as replacing just one component. But you won't know until you investigate your options, which means: get a diagnostic run on it to see what will be needed and what your options are. You won't "know" anything until you do. And remember that any shop will want to "sell up"; get you to buy the most expensive and maximum number of components it can. It's your responsibility to keep it in budget by inquiring about lower cost options like re-using older components or buying the previous year's model.

 

By "leave the computer running" I am saying leave the power on the computer. (You can power off the monitor, but if you wear out that power switch, you can only replace the entire monitor. Modern monitors have their own energy saving "sleep" mode, so I recommend leaving it on as well.) Logged in to an account if you have programs scheduled to run while you are asleep and the computer is physically secured against unauthorized use, or logged out if not. But leave the power on so the heat in the computer case stays in a stable temperature range. Preferably in a room with a stable temperature range as well. If you power off the heat dissipates over night, and then startup when you power on again in the morning causes heat stress from the initial power surge and as it warms up again (which we in the business call "morning sickness"; as in "it was fine when I shut it down last night, but wouldn't start this morning").

 

-Dubious-

Link to comment
Share on other sites

  • 3 weeks later...

from my experiance saves become "corrupted" over time. saves start messuring large in file size then seize up get slow get varius bugs. fallout nv and 3 were ment to be played thugh to a point and then mopping up the other missed content on a new save file. i typically try to start a new save file everytime i reinstall windows to help avoid this.

Link to comment
Share on other sites

  • 6 months later...

-Dubious-

Hey there, I'm experiencing the same sort of issue. What you said about trying to reduce the amount of Z fighting and that could have caused the "pop in." This fellow said that he hasn't changed the ini files therefore he doesn't know why he is experiencing this. However I did change the ini files to reduce Z fighting and ever since then I've been experiencing these problems (Pop In.) I have restored the default ini files but it still seems to be an issue. Would you mind telling me what files I might have changed to reduce Z fighting and therefore affected the game, and what text in my ini files to restore to their normal state? Thanks!

Link to comment
Share on other sites

The most common adjustment to reduce Z-fighting that I am aware of is to adjust the various "distance" settings under "[Display]". As Z-fighting usually occurs only in the LOD distance, the various "LODMin/MaxStartFade" settings are common, but others may have been tweaked.

 

To reset them, suggest you follow the steps regarding INI files in the 'Game INI files' and 'Restoring to "Vanilla"' sections of the wiki "FNV General Mod Use Advice" article.

 

The other possibility is installing new texture files, and/or not rebuilding the LOD files using FNVLODGen after doing so. See my post #7 in this thread where I discuss this.

 

Since the original discussion in this thread, I have learned of a possible "fix" for the "blur" effect: the mod Blur Killer by sortitus. It removes "all blur effects in Imagespace Modifiers (but not depth of field effects, because it's simple to disable that without a mod)".

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...