Loading Game Stallout - help please
Motoki:
Quote from: DMantle on 2010 August 04, 04:41:01
In reference to the original poster's issue: game loads fine, but loading a new or save game stalls with a sliver to go on the load bar; I'm having exactly the same issue.
Patched to the latest, with WA and Ambitions Installed.
Everything installed under the Documents\..\Mods\Packages method
Reran Delphy's framework, everything looks good.
Load the game without Awesome Mod - works fine, loads right in to save game.
Add awesome mod and the cfg to the Packages folder:
- game loads, but completely stalls with a sliver to go on opening a save game or a new game
No copies of the modded .dll anywhere, but I highly doubt that is a factor, as the base game loads.
Windows Vista 64, 4 GB RAM
No sign of any ScriptError reports
Running the game in a window, so no sign of hidden crash errors or alert windows.
Let me know if there is anything else I can provide that might help.
You're doing it wrong. Go back and re-read the help section at Mod the Sims on Installing Sims 3 Package Files: Setup & Files (the new way).
DMantle:
I shall clarify: I installed the awesome.cfg file in the packages directory along with awesome.package.
My resource.cfg (or whatever its called, I'm not at my home pc right now) is correctly in the Mods directory. I know that aspect of things works fine as all my other mods load fine in the game if awesome mod is not in the packages folder.
Yes, I am aware that thorough troubleshooting would require removing every mod I had and trying to run just awesome mod - I have not gotten around to doing that yet, I'll probably try it tonight just to rule everything else out.
The issue does not appear to be related to disk thrashing or file access, as I've tried running proc mon in the background while loading, and nothing unusual comes up.
wizard_merlin:
Quote from: DMantle on 2010 August 04, 18:55:02
I shall clarify: I installed the awesome.cfg file in the packages directory along with awesome.package.
My resource.cfg (or whatever its called, I'm not at my home pc right now) is correctly in the Mods directory. I know that aspect of things works fine as all my other mods load fine in the game if awesome mod is not in the packages folder.
Yes, I am aware that thorough troubleshooting would require removing every mod I had and trying to run just awesome mod - I have not gotten around to doing that yet, I'll probably try it tonight just to rule everything else out.
The issue does not appear to be related to disk thrashing or file access, as I've tried running proc mon in the background while loading, and nothing unusual comes up.
How do you know all the other mods are loading fine and not just being ignored? It could be that AM is actually catching the problem and showing it to you.
I suspect there may be an error in the resource.cfg file, which again is a problem that has been discussed at length previously.
DMantle:
While I appreciate the fact that covering the basics is part of troubleshooting 101, it seems to be a common thread here that if anyone reports an issue, the assumption is that the reporter is an inept buffoon that has no clue as to what he is doing.
That being said, I will go over the details.
- my resource.cfg is in the mods folder, and is exactly as described on MTS
- I know my other mods work, as I can see them all directly in the game when I don't have awesomemod installed - therefore my basic setup appears correct
- when I first reinstalled awesome mod, I forgot to remove a core slider hack from the folder
- I ran the game, and awesome mod detected the conflicting core mod and gave me warning - thus showing that awesome mod was loading
- I removed the conflicting mod and ran it again, and everything goes fine until the very end of the load bar, at which point it stalls.
- I have left it sitting there for 20 minutes to see what happens, and it never progresses.
- if I remove awesome mod, the game loads just fine
I will now move out all of my .package mods and try the game with nothing but awesome mod, not even awesome.cfg, just to see what happens...
wizard_merlin:
Quote from: DMantle on 2010 August 05, 01:20:03
While I appreciate the fact that covering the basics is part of troubleshooting 101, it seems to be a common thread here that if anyone reports an issue, the assumption is that the reporter is an inept buffoon that has no clue as to what he is doing.
In probably 99.9% of cases that is a correct assumption.
Perhaps if you had been reading all the issues previously about shit not working when the problem was a basic error, such as a bad resource.cfg file, or placing said file in the wrong location, and insisting that they did it right, and they know what they are doing and that AM is the sole cause of all their problems, and the root cause of all the problems in the world today, you would understand why people here adopt the attitude and position they do.
Navigation
[0] Message Index
[#] Next page
[*] Previous page