BobTheBull
Warlord
AH, step back and take ten deep breaths.
As has been pointed out several times, you have not given us one piece of information which could help us help you. Such information would include your hardware configuration, graphics driver, operating system, etc., the log files and any messages on screen. Because the logs and messages are incoherent to you does not mean they are to the rest of us. Quit telling us there is no useful information in the logs and let us decide that. As to which logs, all of them. Include the .ini file as well; speaking of that, you did enable logging in the .ini file, didn't you?
All crashes are justified; crashes always happen for a specific reason. The fact you do not understand it does not change anything. What you are trying to find is that reason; after you find it you look for a way to change/prevent it. Sometimes this means you may have to change the way you do things.
If you want a grasp of how to approach crashes, do what I told you: go through this thread and read everything about ctd's and maf's. Do this on several other threads and forums, such as main ROM2, Troubleshooting, modpacks RAND. Your approach to problem solving seems to be whenever something does not work the way you want it to you hit it with a hammer. Instead try to figure out how it does work and why. Then you may or may not be able to change the way it works. If you can't, do what the rest of us do and live with it.l
Follow the instructions earlier, I think by Stategyonly, and set up a game to run on autopilot using a completley unmodded RAND and see if you still get ctd's. If so send that save game to us. If not, then it is probably something you did. Quite frankly, when I have a problem ingame I go look at the last thing I changed and undo it; this fixes the problem most of the time.
Before I post a problem I always search through several forums for information. This has led me to the solution of 90% or more of my problems.
As has been pointed out several times, you have not given us one piece of information which could help us help you. Such information would include your hardware configuration, graphics driver, operating system, etc., the log files and any messages on screen. Because the logs and messages are incoherent to you does not mean they are to the rest of us. Quit telling us there is no useful information in the logs and let us decide that. As to which logs, all of them. Include the .ini file as well; speaking of that, you did enable logging in the .ini file, didn't you?
All crashes are justified; crashes always happen for a specific reason. The fact you do not understand it does not change anything. What you are trying to find is that reason; after you find it you look for a way to change/prevent it. Sometimes this means you may have to change the way you do things.
If you want a grasp of how to approach crashes, do what I told you: go through this thread and read everything about ctd's and maf's. Do this on several other threads and forums, such as main ROM2, Troubleshooting, modpacks RAND. Your approach to problem solving seems to be whenever something does not work the way you want it to you hit it with a hammer. Instead try to figure out how it does work and why. Then you may or may not be able to change the way it works. If you can't, do what the rest of us do and live with it.l
Follow the instructions earlier, I think by Stategyonly, and set up a game to run on autopilot using a completley unmodded RAND and see if you still get ctd's. If so send that save game to us. If not, then it is probably something you did. Quite frankly, when I have a problem ingame I go look at the last thing I changed and undo it; this fixes the problem most of the time.
Before I post a problem I always search through several forums for information. This has led me to the solution of 90% or more of my problems.
