Jump to content

grumbler

Premium Member
  • Posts

    124
  • Joined

  • Last visited

Nexus Mods Profile

About grumbler

grumbler's Achievements

Apprentice

Apprentice (3/14)

  • Conversation Starter
  • First Post
  • Collaborator
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. My problem with this "complaint" is that it isn't true. Bethesda said they planned to have the CS ready for release when the game was released. I have no reason to doubt that this was true. Their plans didn't get fulfilled, but that's understandable; the manpower may have been needed to make the initial release/first day patch as bug-free as possible. Documentation of the CK in a form uninitiated users can use has gotta be hard. They succeeded in the latter. I didn't have a single crash the entire time I played the game before the Nov 21st patch. Some people surely did, but that's unavoidable given the potential combinations of CPUs/motherboards/GPUs out there - nothing can be optimized for every rig. Not even windows. The Nov 21st patch, which broke the game for me (pretty much - I can get up to 40 minutes of playing between crashes) is another story.
  2. Try this: load the level 18 save, open the console, click on your character, type "kill," and close the console. Your character should die, and the game reload. That apparently clears some settings in the save, and could help out. That helped me in FO3 when i had a crash every time I tried to save. Nothing to lose, right?
  3. NVSE versions are backwards compatible, so I don't think your problem is that the plugin needs to be updated for the new version of NVSE. What I suspect is that your NVSE isn't properly installed. Follow the NVSE troubleshooting directions: - Launch NV, then open the console and type "GetNVSEVersion" (without the quotes). It should print back "NVSE version: 1". If this works, then NVSE is working properly. If it prints an error, then something is wrong. Recheck the installation instructions, especially to verify that you have installed everything to the correct directory. If this check is satisfactory, go to http://nvse.silverlock.org/ and get some email addresses of people who can help.
  4. Are you sure it is saving to the FONV folder and not the FO3 folder?
  5. Turn on archive invalidation in FOMM (under tools, IIRC) and see if that helps.
  6. Just the opposite for me - zero crashes since update. Do you use FO3Edit to create a merged patch of Wrye Flash to create a bashed patch? I use the latter, and find it aids stability a lot. In FO3 I used the former, also with some success. One weird solution to the "crash on save" bug that I used successfully in FO3 was to open the console, click on my player, and type "kill." My character would die when the console closed, the game would reload at the last successful save point, but it wouldn't crash on save for hours afterword.
  7. Here you go: http://www.newvegasnexus.com/downloads/file.php?id=34811
  8. Wow, neko1kitty, I must admit that I didn't see how this fix could work, but it does. You do not have to disassociate winamp from .ogg files, though, and that's probably a bad idea for other reasons. Thanks for the tip, I was at my wit's end with the sound problem, and I would never have thought of your solution in a million years.
  9. Uncheck all your mods and see if this still happens. If it does not, activate them one at a time until it recurs. If it doesn't recur on single mods, activate them all and deactivate them one at a time until the problem goes away. If it happens with no mods active, you have a real problem (install, or machine). Reinstall in that case.
  10. No mod altered that area, per se, because the crash occurs no matter where I am and happens with all mods turned off. It started without me making any mod changes. It doesn't happen after masterupdate is run, but that isn't a viable long-term solution because I will want to someday continue to modify my FO3 mod, and I cannot do that if my mod is a master. Thanks for the suggestion, though. It is all very mysterious to me, and I had (up to this point) thought I was pretty savvy about avoiding FO3 crash problems. :wallbash:
  11. I would prefer something less drastic, if there is a less drastic solution. I used master update during the patch fiasco, but didn't much like it.
  12. Mine just started top do this very same thing. I thought at first it was a memory leak issue, but a clean system start from power-off didn't resolve it. No mods added, no changes made in the .ini files, and it just went from perfectly stable to crash on save. :blink: It even crashes on a console save!
  13. You will love it, but be frustrated by the many zillions of mods. I would just note a couple: Better Bodies, and Non-generic NPCs. Get those before you get any others, and then search google for "essential Morrowind mods" and try them out one by one.
  14. I still go back to it every once in a while to get some gameplay out of the huge number of quest mods that the game has. Currently, I am trying to finish the Black Queen Chronicles. Oblivion has some awesome quest mods, but they are far fewer in number and scope to MW quest mods, because of the extra effort needed to make them work. There is nothing like The Underground available in any game more complex than Morrowind, and that keeps Morrowind alive, IMO.
  15. The original question was about Autumn's survival, but that was dealt with in the 10th post, and then we saw the very common tendency for threads to drift off topic, especially when the initial question has been solved but people have introduced extraneous suppositions in the meantime.
×
×
  • Create New...