Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'd suggest start fresh with it wherever it's supposed to go, and only after you know that's working...
Though with that load order including not only a slightly-broken mod like that, but SS2, AND south of the glowing sea, and ... like, way too many others?
Nuke your mod list. Carefully read the mod descriptions for where they must go.
Did your game start crashing after installing a mod or mods ?
You could try my method of sorting which mod is doing this , assuming this is a mod issue .
And with your load order , this could take a couple of weeks .
Decide how mods to disable ( not delete ) ( maybe 25 at a time ? )
disable that first group of mods . then start your game up and see it your game crashes . If your still crashes , re-activate your mods and move on to the next group of mods .
Keep doing this to your game until your game suddenly starts up and doesn't crash . then
re-enable your mods ONE AT A TIME . then when your game crashes again you just ( hopefully ) the mod that's doing this .
The only problem with this , if there more one mod doing this , this will render this rough guide useless . .....
The question is whether this makes sense or not is something completely different. Every mod increases the risk of something is not working properly.
You don't necessarily notice this immediately, but after many, many hours of playing.
Even if you test all mods in a running game and they run without errors, the result can be completely different in a newly started game.
In short: less mods less problems.
The game only started crashing after I had cleaned up the mod order and removed a bunch of mods. Before that it was running crash free for nearly 30 hours of game time.
I have gone over it carefully and spent nearly a year putting together this mod list for my first playthrough. If I saw something that said mod x didn't work with mod y. I didn't download it. Now that said maybe I did download too many mods for fallout 4.
So do you think the crash might go away if I simply started a new game?
or do you think starting over completely (new mod order and everything) is what needs to be done?
Your game is crashing now because something is missing. restore the mods you have deleted or start a new game to fix this.
I am too.
Which version of The Forest are you using?
There was one that was unstable but has been superseded...
Try to go back a version or forward a version (overwrite current)
your.
...
your FIRST PLAY? And you did not play at least 1 full time of VANILLA?
yeah no, dude. reinstall the entire game from the ground up and don't use mods until you know 100% for certain that the game will run with your hardware and os.
Ask yourself some easy questions:
- How many ammo mods do i have installed and how checked them they are not conflicting?
- How many raider overhauls do i have installed changing the appearance? Do they work together?
- Do i have a plan for sim settlements 2 and america rising 2 in what order i have to do quest not to break them?
- Have i checked Overhauls e.g. Goodneighbour navmeshes at the CK aint overlapping?
If you cant answer all of these questions with a big yes trash your modlist now.
The current version 5.3
Oh no no. I did play through the first hour of the game before I even put down one mod to make sure the game ran on my os. then after all the mods I started my first proper playthrough. sorry for the confusion.