GothikaGeist Posted July 15, 2011 Share Posted July 15, 2011 The only other thing I can recommend that you UNINSTALL ALL FOMODS, reinstall the game, DLC, make sure you've updated, and finally install your mods again manually. Link to comment Share on other sites More sharing options...
GothikaGeist Posted July 15, 2011 Share Posted July 15, 2011 (edited) You can also check to see if you are loading the default amount of grids.In your Fallout.ini/Fallout_default.ini/Fallout_prefs.ini look for: uGridsToLoad=X And make sure it's 5 (FIVE) [The "X" corresponds to the number]However setting it lower than 5 increases performance, mine is 3.And with so many mods loading less than 5 grids might help you,since the chance of the game world overloading your computer and causing a crash is shot down. Edited July 15, 2011 by GothikaGeist Link to comment Share on other sites More sharing options...
maboru Posted July 15, 2011 Share Posted July 15, 2011 I believe Beth handed FNV (and the Havoc/Gamebryo engine) to Obsidian because they had to devote all their own resources to developing both their own new game engine and their own new game (Skyrim) while still maintaining customer interest in their cash cow Fallout franchise because they knew it would be quite a while before they could even begin to start developing FO4. Great business plan but I fear that they may not have offered Obsidian all the support needed to address the old engine's foibles and few at Obsidian had hands on experience with that old dog. None the less it's still Beth's ball and, at the moment, they're not exactly maintaining the type of interest they'd hoped for. Obsidian should be responsible for game bugs but Beth is still responsible for engine bugs, they're the ones who licensed it. Yes the engine is old and was never designed for today's modern hardware and operating systems but it none the less worked before and not so much now. A solution must be found or gamers will hold off purchasing not only new DLCs but hold off on Skyrim until reports come in about it's stability thus causing quite a hiccup in Beth's revenue flow. Not such a good business plan. Link to comment Share on other sites More sharing options...
TBDM5678 Posted July 15, 2011 Share Posted July 15, 2011 i noticed that for the short while i was traveling with cass(no mods for her installed whatsoever) the number of CTDs when fast traveling and occasionally traveling by foot increased incredibly (from none to many) i believe something may be wrong with the companions in general since the new update, since i do not seem to be the only person with the problem. if you have a companion with you or waiting somewhere, it may be causing the problems of crashing Link to comment Share on other sites More sharing options...
Splash93 Posted July 16, 2011 Author Share Posted July 16, 2011 Ok, I can confirm that those graphics mods are are defineately to blame for the crashes; just played for another hour with them disabled, no problems at all. Link to comment Share on other sites More sharing options...
DarkHighlord69 Posted July 16, 2011 Share Posted July 16, 2011 (edited) I already posted about the companions, and yeah , seems to be yet another issue that is making my game drop dead.--------I have found that most of the companions made before the 1.3 patch can cause huge lag problems, hangtimes, crashes and a lot of other nasty glitches because of the way the patches changed the AI packages and some leveled load lists. Some of them that are placed inside locations like Prospector Saloon and Vicky and Vance Casino actually cause crashes or total system lockdowns. I have been testing this as well as a friend who is a game designer, and we both have found this to be true. Looks like a lot of the AI issues with the old companions don't really show up until you either run a large load order, or have them out of place or writing over other vanilla AI packages and list commands. I hate this, as a lot of my old companions are bugging out the game or cause some very bad corrupted saves. One of the biggest problems I have found is companions built on the old GECK or made before the 1.3 patch is that they corrupt a lot of saves. I have a beta program I created to test save games for integrity, file errors and corruptions. In every issue or case where I had a save game corrupt or glitch, it was related to old AI packs or companions from the old patches and GECK. ------------------------------------------ YES, COMPANIONS ARE A HUGE PROBLEM AND CAUSE MANY CRASHES AND CORRUPT SAVES!!!! Last night I did the first run to Primm with Raider Girl Cyan as a companion. Was running fine for 5 minutes, then I could start seeing little issues like flashing textures, slow downs, freezes, and just that general feeling that the game was getting corrupted somehow. Also my save games started bloating and getting bigger with each new save. Start out with a 2.3 mb save and by the time I hit the front door of V+V my save was 3.9 mb. Also had 5 or more CTDs, three hangups where the FPS dropped so low it finally crashed, and several times in combat where I crashed while Cyan was killing someone. Went back and started from right before I hired Cyan and did the run again in as close a manner as possible. Save game is 2.5 mb when I hit the door to V+V, have only had one CTD I found was from IWS-Patrols and IWS-Guards. After I reset my load order and put IWS and Mo-Mod dead last, no crashes, no real graphic isses apart from my crappy sytem, and an overall smooth run for 3 hours. Then I tried to take a vanilla companion and see if it repeated the problem. For sure it did. I had Veronica with me and had 4 crashes, three load screen hangs, and a whole load of problems with textures not showing up, NPCs just frozen in place, combat causing CTDs, you name it and it happened. My save game was 2.1mb when I started and after only 30 minutes or so of play, it hit 4.9MB, like oh my how is that possible. OH CRAP!!!! Edited July 16, 2011 by DarkHighlord69 Link to comment Share on other sites More sharing options...
DarkHighlord69 Posted July 16, 2011 Share Posted July 16, 2011 Gothika, Hats off to you and a standing ovation for all your help and comments to people having problems. See you wading in and slugging it out with a whole host of issues on the forums, so major respect and love to you. It's stuff like this that makes us such a great community at Nexus. Increase and Blessing! Link to comment Share on other sites More sharing options...
DarkHighlord69 Posted July 16, 2011 Share Posted July 16, 2011 (edited) I believe Beth handed FNV (and the Havoc/Gamebryo engine) to Obsidian because they had to devote all their own resources to developing both their own new game engine and their own new game (Skyrim) while still maintaining customer interest in their cash cow Fallout franchise because they knew it would be quite a while before they could even begin to start developing FO4. Great business plan but I fear that they may not have offered Obsidian all the support needed to address the old engine's foibles and few at Obsidian had hands on experience with that old dog. None the less it's still Beth's ball and, at the moment, they're not exactly maintaining the type of interest they'd hoped for. Obsidian should be responsible for game bugs but Beth is still responsible for engine bugs, they're the ones who licensed it. Yes the engine is old and was never designed for today's modern hardware and operating systems but it none the less worked before and not so much now. A solution must be found or gamers will hold off purchasing not only new DLCs but hold off on Skyrim until reports come in about it's stability thus causing quite a hiccup in Beth's revenue flow. Not such a good business plan. ------The game that Obsidian recieved after the whole legal war was finished WAS NOT in any way, shape or form a product that could be released. I am really good friends with someone who just got laid off by Obsidian. He says that they got a game that was 80% complete and was full of bugs and errors that they had no idea how to fix, correct or work around. They did not know the game engine, and from the reports I have, they did not care or want to learn how to really fix it or make it better. Also I am told that the first version released on launch day was only about 85% completed and they all knew it was a sick dog that needed to be put down. Instead they let us have it way too soon, and in a totally broken state of existence. Evidently the base game is still only about 90-95% working, with about 10% data fault errors and completely broken commands and file modules. In particular they had and are still having huge issues with the AI packages and NPC commands. They evidently just decided to do cheap fixes or not even fix it, and this is resulting in the consumer's pain and suffering trying to make this thing work. Obsidian has a long history of releasing games in unfinished or broken condition, and this is well reported online and in industry forums. I know this for a fact because at one point I was beta-testing some of their products and working for another studio that was allied with them. They recently laid off their best project manager and most of the top level designers and software geniuses, which makes it even harder for them to fix the engine problems. They got rid of most, if not all of the people who might have been able to fine tune the engine, and also the ones who would have hammered away at the problem until a solution was found. A gutted and demoralized company would not be my first pick to try to fix or much less release and maintain software support for something that was already known to be out-dated and buggy from the base files up. Just for historic record that I am noting this. Explains why there are so many problems with this game compared to FO3. FO3 was a nightmare after release, but this is a never ending hell of seeing the huge and wonderful game, and then finding all the bad stuff and getting lost in hopeless frustration. An unplayable game will eventually stop being played and lose them lots of money they had counted on. According to some ex-employees and some current insiders, Obsidian is headed for some form of bankruptcy real soon. The problems with the release of FONV and the DLCs will not help at all to reverse their financial woes. Hope we are all not left in the cold looking at a beloved game that none of us can play. Edited July 16, 2011 by DarkHighlord69 Link to comment Share on other sites More sharing options...
GothikaGeist Posted July 16, 2011 Share Posted July 16, 2011 Thanks DarkHighlord69, and it's funny actually that you mention : "An unplayable game will eventually stop being played." I literally sit here in the forums, hitting "refresh" over and over, helping others with the information that I have cobbled together from days and days of trying to repair my Fallout each time it decides to crash for whatever reason. And it really sucks that Obsidian was not trained in the use of the engine at all. Getting rid of their most prominent employees, who had a chance at crushing the bugs, can really only hurt the consumers more than anyone else (Not counting the financial blow). Oh and Splash93, it probably is best to wait until EVE is out of beta or to just play without those enhanced graphic mods. BUT, if you absolutely need a graphic mod, try this out: http://newvegasnexus.com/downloads/file.php?id=38196 That's the "Detailed Normals - Texture Pack" It upgrades vanilla textures to look FAR better.I use it. Link to comment Share on other sites More sharing options...
Splash93 Posted July 17, 2011 Author Share Posted July 17, 2011 Oh and Splash93, it probably is best to wait until EVE is out of beta or to just play without those enhanced graphic mods. BUT, if you absolutely need a graphic mod, try this out: http://newvegasnexus.com/downloads/file.php?id=38196 That's the "Detailed Normals - Texture Pack" It upgrades vanilla textures to look FAR better.I use it. I already do use Detailed Normals, but I'll try disabling EVE. Link to comment Share on other sites More sharing options...
Recommended Posts