Jump to content

Game always crashes near Westside


littleot316

Recommended Posts

@ Effeob

 

Ha ha! You're hilarious. I'm glad I forgot to come back. Did you learn anything new about your "crashy" area?

 

hehe thanks, i guess ;)

well um, actually, ive quit playing FNV for the time being.

my save game got so corrupted that it wouldnt even load the wasteland. i was at the sasparilla factory doing that mission to turn off the cap press. after doing that i went outside, went north, and started running into the crash problems near westside. i went back to my game and tried a bunch of .ini edits to make things load better, give it more cache memory etc...tweaks i hadnt yet done that are supposed to help the game run better (and my machine is a monster so it can handle anything). but no, then things just got worse - then i couldnt even load my game outside near westside. i had to revert back to my save while still inside the sasparilla factory. but i couldnt go outside. so i typed "coc" in console to port me somewhere else, far far away, but then i still couldnt go outside.

 

so now, seems my save game is totally corrupted and cant use it at all.

not willing at all to restart, because im using the underground hideout mod and have near fully stocked my armory with all the weapons and ammo in the game. hardcore 40+ hours of collecting and have done most of the side quests/companion quests before going on to finish the main quest, tho im still only about 2/3rd or maybe even halfway thru the main quest.

 

the very idea of having to restart my game because obsidian failed so hard at developing this game, just pisses me off entirely. i got a refund for the game, charged back on my credit card, and will never, ever, buy anything from obsidian again. possibly not even bioware.

 

this failure of theirs is so immense i just cant imagine how they could do it.

fallout: new vegas is by far one of the top 5 games of all time, give or take personal preference. for me, i might have even considered it the best game ive ever played. and ive played practically every major (and most minor) games since 1990. for them to fumble this and technically fail it this hard is like brazil being in the world cup final vs some country like the usa, or iraq, india, etc...you know, countries who dont even play footboll or suck hard at it...and then they LOSE HARDCORE. brazil would never, ever, be able to recover from an embarassment like that, no matter what they did. and that, my friends, is what obsidian has done. they had a winning ticket in their hands, and they godamn failed it so hard omfg.

 

looking back on the 100-200+ hours ive spent on this game (playing it, and modding it) the only real lasting memory i have of it is a lot of frustration.

frustration. yup, thats what this GAME has given me.

frikkin rediculous.

 

/rant off

for those of you having no issues like this, i sorely am jealous of you, and wish you the best of luck to not have crashes and game ending bugs. you are the lucky few who are able to enjoy this gem. be happy for it!

i am but one of the majority who has, finally as well, given up.

bye bye fallout NV, and screw you!

;-)

Link to comment
Share on other sites

Awe, don't be like that. You're giving gamers a bad reputation for being prima donna. Potentially the largest undertaking a developer could take would be creating a open ended worldspace. Much less one that has an avaliable 2 square mile main map. Plus there is development of the SDK roughly handing the keys to the tools that created the game to the players. You said yourself that it's a top 5 game. Games on this scale won't be created if we all act like a diva. FO3 is roughly 4 times larger in the size of the raw data than most games, FNV would be about 6 times. This being built on a long known buggy game engine. However the game engine is simple & concrete as a foundation an is what allows all the things we like about FO3 an FNV. You don't get to have your cake an eat it too.

 

Your game went corupt for a few reasons, which primally is your own fault. Myself along with all the other PC gamers are in fact glad that you decided to "Diva out" from the party. Thanks for leaving, maybe developers won't hate us as much anymore, and only make simple linear games quickly that work perfectly just to make a bunch of money. Seariously you are being childish, grow up, buy the game again, write a thank you letter this time, patch the game, don't use mods or learn how to use them first you big dufus.

 

1. You were using mods. More often than not these mods are not cleaned, and also created by people that have little if any idea what they are doing.

 

2. You played the game for long periods without rebooting the game or the computer system. Over time the system cache goes corupt or gets full.

 

3. You used the continue button at the main loading screen, quicksaved, or autosaved which promote coruption.

 

4. The game went partially corupt (not enough to crash) from abnormal conditions to which you saved the game afterwards thus locking that into all future loading of the save game.

 

5. FNV in particular was prone to go corupt at launch from the update process an the pre-order packs which has been fixed in the later patch.

 

6. You were using mods without a Merge Patch-Bashed Patch, FO3 Master update, and without opening the whole load order to view what that poop you got is actually doing.

 

http://i895.photobucket.com/albums/ac156/grindedstone/Techsupport/fasdf.jpg

 

There was nothing special about the two westside map marker areas nor the westside worldspace itself.

It's a popular area that everyone ends up exploring often early in the game.

So I placed the Grinded guide here in the hopes to help you enjoy it.

So I placed the GrindedGuide here.

 

****Grinded Guide****

 

I make sure to have a copy of Visual C++ (any year) as well as the entire family of .NET framework installed 1 2 3 3.5 4.0 all of them, normally I get these thru microsoft downoads or automatic updates. I also make sure to have a Windows XP SP3 level version of windows, often fully updated by microsoft, but I always start with the service pack, an then use the web site to scan to see what is needed. You can get to the website really easy by going to the start menu, Set program access an defaults, Add programs, there's a button link that opens to the microsoft automatic updates, allow the Active X control which will allow microsoft to scan the computer for what it needs, pick the Service pack, then reboot, do it again, an take high priority, check to see you got .NET frame work, look around in optionals. I normally decline the signed drivers. Also I update WMP an set WMP as the default player for .wav an .mp3. Then the only other thing on the computer is Java an the adobe flash player. I use whatever drivers come in the box with my hardware, unless it's time to update from the website that makes the hardware (for example New Vegas I update from websites) Then I update my BIOS once every couple of years if that. However I will format the harddrives an start over fresh with empty hard drives about twice a year but you need a windows install disc to do that.

 

Also some players say un-installing Visual C++ an .NET framework then installing it again helped with crashing.

 

I run a Nvida 9800 GT it gots 1Gb of video memory, 1GB runs smoother than 512Kb.

I use these settings in the Nvidia control panel.

(location) *Game*

 

Use the advanced 3D image settings (in adjust image settings with preview)

 

(Manage 3D settings)

Anisotropic filtering *FNV* 2X

*FO3* 4X

 

Antialiasing- Gamma correction Off

Antialiasing- Mode Off

Antialiasing- Setting None

Antialiasing- Transparency Off

 

CUDA-GPUs All

Extension Limit Off

Maximum Pre-rendered frames 3

Multi-dislpay/mixed-GPU Accel Single display performance mode

 

Texture filtering- Anisotropic sample optimization On

Texture filtering- Negative LOD bias Clamp

Texture filtering- Quality High performance

Texture filtering- Trilinear Optimization On

 

Threaded Optimization Auto

Tripple buffering On

Vertical sync Force on

 

 

 

 

Game launcher settings.

 

(General)

1600x1200 (your native resolution)

Antialiasing Off (best performance)

Anisotropic Filtering Off (best performance)

Vertical Sync on

HDR On

 

(Detail)

Texture quality High

Radial Blur quality Medium

Depth of field On

Transparency Multisampling On

 

(Water)

Water refractions On

Water reflections On

 

Reflection quality Medium

Soft reflections On

 

Full Scene Reflections Off

Full Detail Reflections Off

Water displacement Off

 

Depth fog On

Water Multisamlping Medium

 

(Shadows)

 

Enable shadows on or off, it's only character shadows I use on most of the time.

 

Shadow quality Medium

Shadow filtering Medium

 

Max interior shadows 3

Max exterior shadows 3

 

(View distance) *Mainly set in-game see in-game settings below*

 

Object fade 6

Actor fade 4

Grass fade 2

Specularity fade 5

Light fade 15

Item fade 3.8

Shadow Fade 2

 

(Distant LOD)

Tree LOD fade 26

Object LOD fade 38

Land quality 100

 

 

 

In-Game settings (set by the number of clicks from left to right)

 

Actor fade 3 clicks

Item fade 3 clicks

Object fade 6 clicks

Grass fade 6 clicks

Shadow fade 3 clicks

Light fade 6 clicks

Specular fade 3 clicks

Object fade 8 clicks

Tree LOD 8 clicks

 

 

 

Fallout config .ini files

 

*FNV*

Fallout_default located at steam/steamapps/common/FNV This is the main config file.

Fallout located at my documents/mygames/FalloutNV This is the secondary config

FalloutPrefs located at my documents/mygames/FalloutNV This is also a config file

 

I check all three so they match exactly, an look for these tested settings I use.

Basiclly the same thing for fallout 3 only there are just 2 files to change.

 

 

1=True 0=False in most cases

1=On 0=Off in most cases

 

bRunMiddleLowLevelProcess=0 !EXPERIMENTAL!

 

bUseThreadedBlood=1

bUseThreadedMorpher=1

bBorderRegionsEnabled=0

 

bPreemptivelyUnloadCells=1

 

iPreloadSizeLimit=Set acording to tweekguide from http://www.tweakguides.com/Fallout3_10.html

 

bUseHardDriveCache=1

bUseThreadedParticleSystem=1

bUseThreadedAI=1

bLoadFaceGenHeadEGTFiles=1

 

fDecalLifetime=300.0000 (5 minutes)

 

bAllow30Shaders=1 (Requires switching shader packages acording to tweekguide)

 

iMaxDecalsPerFrame=30

 

bAlwaysRunByDefault=0

 

(put in controls section)

fForegroundMouseAccelBase=0

fForegroundMouseAccelTop=0

fForegroundMouseBase=0

fForegroundMouseMult=0

 

iAudioCacheSize=4096

iMaxSizeForCachedSound=512

 

bEnableBorderRegion=0

bCloneModelsInBackground=1

iNumHavokThreads=5

 

bForceFullLOD=1 (distant bushes)

 

iBackgroundLoadLoading=1

bUseBackgroundFileLoader=1

bBackgroundLoadLipFiles=1

bLoadBackgroundFaceGen=1

 

bSelectivePurgeUnusedOnFastTravel=1

bCloneModelsInBackground=1

 

bUseFaceGenLOD=1

 

uMaxDecalCount=300

bProfileDecals=1

 

Run Archive Invalidation invalidated in NVMM (FOMM) Toggle it on to apply, it's in the tools tab now, then near the bottom of the falloutdefault.ini check to see that the corrections were applied to the load list of archives with AI! being first, then above that archive file= listed as blank.

 

Once this part is done I play the vanilla game for as long as I can have fun with it, at least past level 10, in order to see how well the game is running on this current install. I try to re-boot the computer after about 4 hours of fallout play, but sometimes it goes for 8 hours. The system cache will go corupt eventually, which will crash you or ruin your save games. So it's good to reboot. I will do a soft re-boot often, save, exit the game, then launch the game again, but after a while it's time to restart the whole computer.

 

Mod selection- If everything goes smooth. Then I'll download tons of mods, an put each in a seperate folder which is named based off what it does or how much I'm scared of it breaking the game. Also inside these folders the seperate parts of large mods are in seperate folders named 1 2 3 4 5 in the order of install, if there is a update it goes in a update folder, if there is a optional then it goes in a optional folder. Once my brain is fried from downoading mods. I then start looking at them to see what I want to install. It's got to be a dang sparkly diamond that I just can't resist, something that I just have got to have an won't play fallout without for me to even consider installing it. However I will install one mod I'm not sure about, but this is only as a test to see if that poop even works, keep in mind though that if that one mod doesn't work you'll have to do all this crap listed above again, which is really really bad, hence, I really really got to have the mods I install otherwise I wouldn't bother installing them. But fear not, the more builds you make the better you get.

 

FNV edit or FO3 edit- When the load order is installed an put into a order where things that are the same are grouped together with the main .esm at the top. I will load the whole thing with FNV edit or FO3 edit then I'll fix everything that is causing problems as far as the .esm an .esp. Though I never change a DLC as a way to avoid having to save the DLC possibly breaking them. I will fix the DLC by adding overrides that load last an use the DLC as masters. These are basicly small quarantine mods just for the DLC. Think of it as a way to make the DLC work with the player made mods but without changing the actual DLC's. The other stuff gets seperate overrides too if needed. Basicly anything you can't fix by Drag an drop or copy paste or fix very easy, gets fixed inside a override. To do this you right click the top of the mod in the right window, where the mods name is or the entry in the left window, then pick copy as override into, create a new file, name it based of what it's doing. Override-Drugs, Override-Dialog, Override-Scripts, Override-NPC This being done as a way to further seperate them avoiding a landmine going off from having too many masters in on one override. You never wana add a mod as a master to another mod as a way to fix them, quarantine it, use a override. Since we are here below copy as override into, there is copy as new entry into, which basicly makes a new version of this entry for you to do whatever you want with. It takes a while but you can pretty much make anything just using FO3 edit. Just save it before you change something you don't know what it is or how to fix, then go to the geck main page to find out what that data actually is.

 

Merge Patch- If you load up the whole load order in FNV edit or FO3 edit, you can click the box on the left that has all the mods in it, Ctrl A (select all) then right click the selection, you can create a merge patch. What this does is create a new mod which uses all of your mods as masters, thus allowing any content in those mods to be used in the MergePatch.esp you just created, then it picks up on common areas of conflicts that could be fixed just by merging them, this is often list type data, like a bunch of entrys spread out like a shotgun blast, Merge Patch brings them all together in one list so that everything gets used, not just the one that was loading last in the load order. The more mods you have the more you need a merge patch but I run one anyway an see if it picks up on anything, if it doesn't then I just don't save it. Also it's a good idea to view what it picked up on an go thru each entry an fix things if they need it.

 

Bashed Patch- This is the same thing basicly as Merge Patch only it's done with Wyre Bash, Bash Gary, Gary bash, something like that. I was too tired to learn how to use it. I have too many other things to learn like scripting an making models that actually work for a change.

 

Master update- FNV edit or FO3 edit has the ability to clean up some hidden data an also turn all of the mods in the load order into psudo .esm, which is cleaner than .esm with .esp after because we don't really stick to the rules when we are creating mods. Also the main reason I use it, is that it has the ability in both games to prevent crash upon saving the game, an even fix save games which are crashing upon save. In FNV this happens around 7 hours into the game. Any time I change something in the load order, even if it's just a tiny thing I know that I should master restore before I change it, then master update afterwards. Thankfully it's a fully automated process. You add -masterupdate an -masterrestore to the target line of the shortcut to FNV edit or FO3 edit to launch those. Also it creates backup copies of your .esm an .esp before it changes them just in case all you do is rename the back to what they were an bam instant .esm or .esp, though I have only had to use one or two over the last few years, so I delete them most of the time.

 

 

In closing- The only other thing I do is give the computer time to actually boot up, it's a couple of minutes now that I have norton 360 installed again. Then also when I launch fallout 3 or fallout new vegas I won't skip to the main loading screen, I wait an let it get there on it's own. Then I only use the load an new buttons at that main menu. I'll load a save game, then press Esc as soon as the screen pops up. Also I might fast travel somewhere spin the camera around an press Esc an load the same save game again (double load) usually the second load is smoother, but I don't do this very often. Then when I want to save the game I press ESC which pauses the game, then save, then create new save. Each time. I turn off the autosave an I never quick save because they are not full saves an they are prone to coruption. I never overwrite a save game. Then I won't delete any of the save games until I'm ready to delete them all. I also don't install mods until I'm ready to delete all the save games. Most of the time I play on the 1 death rule, when the character gets killed I have to start over an go thru the tutorial again as a penalty (it really makes you wana stay alive) Then losing characters is sad so you feel a bit of sadness from the death. However there are muligans sometimes, an as a rule there is a 3 deaths in one day limit, an then yah they are really dead after that. So I'll delete all the saves an maybe get another mod an start over, crying my way thru the tutorial.

Edited by GrindedStone
Link to comment
Share on other sites

  • 6 years later...

I don't know if this is the right forum but whatever. I experience and massive bug in my game where when I enter certain area's, the game fails to load resources, leading to some missing textures models, and eventually a corrupt save file. When i exit to the desktop and re enter game, the saves are no longer corrupt. Has anyone else encountered this issue, and more importantly, is there anyway to fix it? :ninja:

Link to comment
Share on other sites

Please see the Nexus "Terms of Service" about not resurrecting old threads. I think we can all agree that six years is "old".

 

Based solely upon those symptoms this could have any of several causes: ranging from "too many plugins" through the issues listed in the 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. And just because a save file loads does not mean it is not corrupt. Please provide the information requested in the wiki "How to ask for help" article.

 

-Dubious-




Link to comment
Share on other sites

  • Recently Browsing   0 members

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