Loading Crash

[kenhal]

Hi,

I've played for about 60h without any problem using an ultra graphic configuration. I've visited all the map experiencing a few crashes (mostly game bugs or textures errors).

The problem began yersterday...while playing, I teleported my pg from Goodsprings to camp McCarran and the game crashed (infinite loading screen), tried again few times with the same result. So I teleported near Vegas and reached the camp by foot :)...everything well except for a strange lag looking towards the vegas ruins (never lagged before!). Now, from yesterday, I can't load any savegame in Vegas zone (both outside and inside buildings) for an unknown reason :wallbash:

I tried using the Nvidia d3d9 perf fix (it goes only the first time then I can't load anymore). The game seems to be playable only if I disable both antialiasing and anisotropic filtering (horrible :yucky: ). I also tried disabling antialiasing and anisotropic from the game and forcing them from the Nvidia CP...

 

My hardware configuration (Win7 Professional x64, CPU I5 2500k 4GHz, 8 Gb Ram, GeForce GTX 275 1768MB) supported the game for a week o_O ...

Can anyone solve this mistery?

Edited January 22, 2012 by kenhal

[GrindedStone]

You corupted the save game, give me a minute. It's shouldn't crash very often if at all.

 

I would say first that I heard about Win7 using seperate folders for 32 an 64 bit applications, now the question is if you run something in compatabilty mode is it the same thing, or is it that only certain software needs to be installed in one folder or the other. x86 an x64 folder At any rate Steam suggests to install both the 32 an 64 bit versions of Visual C++, That is the C computer language of the 1970's that has been developed over an over into the plus plus it is today.

 

Sound plays more of a part than you think in both performance an the kind of issues we have in FO3/FNV, don't underestimate it. A trick is to turn down the master volume slider in the main menu, this basicly disables sound, a useful tool. The two games were designed to use what Windows Media Player uses, an it's wise to set WMP as the default program for .Wav an .Mp3 because of this, but you can also update WMP.

 

.NET framework is from Microsoft an it's been used in just about everything. It comes in 1 2 3 4, an odd ones like 1.5 or 3.5, I get as many as I can find an just install them. Though it isn't required, it's recommended. Now overtime it's unavoidable that a computer system gets trashed... So you see a few players that have tried un-installing Visual C++, WMP, an .NET framework, then installing them again after a reboot. To fix crashing an problems, somewhat linked to coruption.

 

Ultra settings are really really stupid. First off it puts Water to use full scene an detail reflections which is by an large the largest performance eater, an thus a cause of system tax, thus a possible cause for coruption. Next the sliders get jacked way up even when anything past 1/4 is basicly a waste because FO3/FNV render 4-8 times as much as Oblivion. 1/4 to 1/2 should be enough, stop being greedy, because it's directly linked to the frame stutter that FO3 an FNV suffer from.

 

HDR an Bloom run well in Direct X 9 10 11, so it's not a big deal using it. These two things only add the glowing light effect, like neon. For what it adds to a scene it takes away a lot more, for example developers an modders can't use anything even near the color white. There are still light beams an plenty of FX built into the game itself without HDR or Bloom. So the smart thing is to trade off HDR an Bloom for a little more AA an AF.

 

Shadows are pretty stupid in the game unless you tweek them to draw like 16 shadows, because if it's just 2-6 eventually you'll end up watching shadows switch between the moving NPC's. It's also a big performance eater on just about every game that ever came out with character shadows. The world shadows are built into the game thru directional lighting so it's kind of like switch this off to avoid watching them switch back an forth.

 

Tweeking the game is next. Thankfully nowdays you can use a app to do that for you. FNV configurator Select purge on fast travel, but not preemptively unload cells. Then if you have a sound card, jack the audio cache all the way up. Multithread everything but audio. Background load everything, an run 5 havok threads. Defrag your drive unless it's SSD.

 

You shouldn't autosave, quicksave, or use the continue button. It can cause coruption. You also shouldn't ever overwrite a save game. You should press Esc an create a new one each time. Keep them all until you are ready to delete them all. You also shouldn't leave you computer on 24 hours a day like a dufus. You should Exit the game an launch it again every 4 hours, then every 8 hours you should reboot it.

 

You shouldn't run the whole time, like across the wasteland. It's roughly 2 square miles so it's a lot of data to load, particularly with the idiots that run ultra settings for bragging rights. All that is doing is shaving time off your hardwares lifespan. It slows down your physics too. You should run across the wasteland to test it. If you have the settings correct you shouldn't notice frame skipping or stutter. Then when you are playing try walking more than running. Every load order ends up with dirty mods in it, I suggest you learn how to clean them. You should also get the vanilla game running smooth an tested for a while before installing mods, so you know it's the mods that broke your game.

Edited January 24, 2012 by GrindedStone

[Jeoshua]

I would like to add on, do not use the d3d9 perf fix. It is depreciated and disabled anti-aliased multisampling (that's why your grass looks like barf).

 

I use, with great success, the ENBSeries ANTIFREEZE 0.9 Patch file. It's technically made for a newer version of the same engine as New Vegas, although it says "Skyrim" on the tin. It doesn't disable the Antialiasing, although it does introduce some strange lighting glitches... nothing so bad as a slowdown or a crash, tho (and gets about 2x the framerate on my rig as vs. Vanilla or d3d9-perffix)

[trog69]

Hi,

I've played for about 60h without any problem using an ultra graphic configuration. I've visited all the map experiencing a few crashes (mostly game bugs or textures errors).

The problem began yersterday...while playing, I teleported my pg from Goodsprings to camp McCarran and the game crashed (infinite loading screen), tried again few times with the same result. So I teleported near Vegas and reached the camp by foot :)...everything well except for a strange lag looking towards the vegas ruins (never lagged before!). Now, from yesterday, I can't load any savegame in Vegas zone (both outside and inside buildings) for an unknown reason :wallbash:

I tried using the Nvidia d3d9 perf fix (it goes only the first time then I can't load anymore). The game seems to be playable only if I disable both antialiasing and anisotropic filtering (horrible :yucky: ). I also tried disabling antialiasing and anisotropic from the game and forcing them from the Nvidia CP...

 

My hardware configuration (Win7 Professional x64, CPU I5 2500k 4GHz, 8 Gb Ram, GeForce GTX 275 1768MB) supported the game for a week o_O ...

Can anyone solve this mistery?

 

I am seeing the exact same problem. I have a higher-end system, and I only have Project Nevada, MCM, and AWOP isntalled as mods, and I have never had a problem until after leaving OWB. Now, all the top 3 to 5 saves become corrupted, never loading. I can't believe this happens after it's played flawlessly for 32 levels. I'm also getting occasional CTD, something I never had happen before yesterday.

 

EDIT; I too, started having this problem, right after I confronted Benny and went to his suite. No loads from the Strip, nor from Hoover Dam; I kinda fear that that's coinkidink, and I'll have the same problems w/save games no matter where I go.

Edited January 28, 2012 by trog69

[trog69]

You corupted the save game, give me a minute. It's shouldn't crash very often if at all.

 

I would say first that I heard about Win7 using seperate folders for 32 an 64 bit applications, now the question is if you run something in compatabilty mode is it the same thing, or is it that only certain software needs to be installed in one folder or the other. x86 an x64 folder At any rate Steam suggests to install both the 32 an 64 bit versions of Visual C++, That is the C computer language of the 1970's that has been developed over an over into the plus plus it is today.

 

Sound plays more of a part than you think in both performance an the kind of issues we have in FO3/FNV, don't underestimate it. A trick is to turn down the master volume slider in the main menu, this basicly disables sound, a useful tool. The two games were designed to use what Windows Media Player uses, an it's wise to set WMP as the default program for .Wav an .Mp3 because of this, but you can also update WMP.

 

.NET framework is from Microsoft an it's been used in just about everything. It comes in 1 2 3 4, an odd ones like 1.5 or 3.5, I get as many as I can find an just install them. Though it isn't required, it's recommended. Now overtime it's unavoidable that a computer system gets trashed... So you see a few players that have tried un-installing Visual C++, WMP, an .NET framework, then installing them again after a reboot. To fix crashing an problems, somewhat linked to coruption.

 

Ultra settings are really really stupid. First off it puts Water to use full scene an detail reflections which is by an large the largest performance eater, an thus a cause of system tax, thus a possible cause for coruption. Next the sliders get jacked way up even when anything past 1/4 is basicly a waste because FO3/FNV render 4-8 times as much as Oblivion. 1/4 to 1/2 should be enough, stop being greedy, because it's directly linked to the frame stutter that FO3 an FNV suffer from.

 

HDR an Bloom run well in Direct X 9 10 11, so it's not a big deal using it. These two things only add the glowing light effect, like neon. For what it adds to a scene it takes away a lot more, for example developers an modders can't use anything even near the color white. There are still light beams an plenty of FX built into the game itself without HDR or Bloom. So the smart thing is to trade off HDR an Bloom for a little more AA an AF.

 

Shadows are pretty stupid in the game unless you tweek them to draw like 16 shadows, because if it's just 2-6 eventually you'll end up watching shadows switch between the moving NPC's. It's also a big performance eater on just about every game that ever came out with character shadows. The world shadows are built into the game thru directional lighting so it's kind of like switch this off to avoid watching them switch back an forth.

 

Tweeking the game is next. Thankfully nowdays you can use a app to do that for you. FNV configurator Select purge on fast travel, but not preemptively unload cells. Then if you have a sound card, jack the audio cache all the way up. Multithread everything but audio. Background load everything, an run 5 havok threads. Defrag your drive unless it's SSD.

 

You shouldn't autosave, quicksave, or use the continue button. It can cause coruption. You also shouldn't ever overwrite a save game. You should press Esc an create a new one each time. Keep them all until you are ready to delete them all. You also shouldn't leave you computer on 24 hours a day like a dufus. You should Exit the game an launch it again every 4 hours, then every 8 hours you should reboot it.

 

You shouldn't run the whole time, like across the wasteland. It's roughly 2 square miles so it's a lot of data to load, particularly with the idiots that run ultra settings for bragging rights. All that is doing is shaving time off your hardwares lifespan. It slows down your physics too. You should run across the wasteland to test it. If you have the settings correct you shouldn't notice frame skipping or stutter. Then when you are playing try walking more than running. Every load order ends up with dirty mods in it, I suggest you learn how to clean them. You should also get the vanilla game running smooth an tested for a while before installing mods, so you know it's the mods that broke your game.

 

I'll probably try some of your suggestions, but you're sort of a jerk, and the way you "recommend" we play the game sucks. Walk across the Wasteland. Yeah, that'll fix everything. Like I'm the only player that runs in most areas. I've never heard of that being a problem.

[GrindedStone]

Next time I write a book, you can quote it. It's not required that the person reading what I have to say has to like or even agree with it. Run Forest RUN!

[SimpleGlitch]

Grindstone, some of what you said is good information, but a few things were incorrect.

 

Turning your computer off every night will not increase performance, or prolong its life. It will save energy costs, but not help your computer. Actually, turning off your computer too much will cause stress on the components in your system. Also walking across the wasteland may not be necessarily. Generally loading errors caused by moving between cells is due to having too little of RAM in a computer. Unless your walking into a specific cell that is very intensive (such as an area with a lot of npcs fighting), there shouldn't be a problem, and running won't effect the problem he has with teleporting/fast traveling.

 

However, bringing up where the program is installed and checking .net framework is good information

[trog69]

Next time I write a book, you can quote it. It's not required that the person reading what I have to say has to like or even agree with it. Run Forest RUN!

 

...aaand the jerkwad-ness continues....

[GrindedStone]

...aaand the childish sensitivity continues...

[luthienanarion]

This is another shining example of why I usually avoid threads where GrindedStone has indiscriminately showered everyone with his opinions.

 

 

This is a tech support forum; the general idea is to help people with technical issues and not berate them or flood them with unrelated information or advice.