Loading Game Stallout - help please
aimlesscoyote:
Hi guys, I made the mistake of patching to 4.2.32.7001 and now I cannot open any saved-games (or create new ones) that have Awesomemod. I do have the latest version of Awesomemod, released mid-July 2010. Here is what's happening:
The game starts up just fine. No problems on the splash screen or intro. It gets to the "load a game" screen with the swampy Ambitions background. I can select a saved game, or try to create a new game, click the check-mark to begin... and sit, and sit, and sit.
The green loading bar gets to the very end, where just a tiny-bit is empty... and stops. No more RAM is allocated to the process (topping out around 720,000-880,000k) and CPU usage falls between 25-40%. I let it struggle for up to 15 minutes before ctrl-alt-deleting it out of its misery. I've attempted loading several different saved games and one new game so far.
So how do I fix it, please? Is it a problem with the patch, or Awesomemod, or perhaps a different mod altogether? In another post here, Pescado noted that a stalled load-bar which is moving is the sign of a failed patch. So I downloaded the 4.2 patch and did a manual re-patch (ignoring the game's various protests). Still no luck.
Can someone give some advice, please?
Motoki:
Been talked about many times. It's not Awesomemod and patching is not a mistake. It's one of your other mods and/or pieces of custom content. Check your other mods first for updated versions. Many of Twallan's mods have been updated for the patch and in particular the old non-updated version of his computer causes this very issue so if you have it, go get the new version.
Somehow Awesomemod gets blamed every time there is a new patch and every other Tom, Dick and Harry's mods or content need to be updated. I don't understand this. I also don't understand why people don't go looking for updates to all their mods when they patch and why they don't use a process of elimination to actually, you know, check if Awesomemod is really causing a problem before posting on the Awesomemod forum. It's not like it's hard to yank everything else out and try testing the game with only Awesomemod.
I guess most people would rather post without searching and have someone else give them the answer. ::)
aimlesscoyote:
You know, I had typed up this long post and then I realized... given the tone of your response, you wouldn't read it, or really give a damn.
So, thank you for the info. I can do some troubleshooting with that.
As a side note, I feel sorry for you, because you can't answer a simple question without dissolving into whining and insults. Contrary to what you insinuate, some people do come to this forum with legitimate questions. More importantly, a huge number of people avoid contributing to this forum, because of responses just like yours. After all, why speak up, when some smart-ass kid is just going to smack you down, so he can feel better about himself and high-five his buddies about how cool he is?
Well, hey. Some people just can't help being what they are. Sorry to say. Maybe you'll grow out of it.
But thanks for the info, anyway.
Anria:
Not that I agree with aimlesscoyote's attitude, but I feel I should point out that I've had this exact same issue and all the evidence points towards it being Awesomemod. My game worked before I went on holiday last week, and when I came back from holiday all I did was download the new version of Awesomemod and suddenly it sits on the loading screen.
And before you ask, yes I do have the most recent versions of all other mods I use, and yes I have checked that those mods are compatible with the current EPs/SPs I have installed and with each other/Awesomemod. I have only updated Awesomemod, and now my game sits on the loading screen. Take Awesomemod out, and it doesn't do that. Pretty sure that indicates that the loading screen thing - for me, at least - is a problem with Awesomemod.
J. M. Pescado:
A loadscreen stalling possibly indicates an FSE occurring that you can't dismiss because you can't see it. To see if an FSE is occurring, look in your luserdirectory for a "ScriptError" XML, and if you find it, attach it here.
Navigation
[0] Message Index
[#] Next page