Description: Ever since the patch my game does not save any progress at all. It shows the saving icon in the corner but if I log out to desktop it does not save. I do not have folder control enabled so I konw that is not the cause. I also disabled Steam Cloud saves and that has not resolved the issue. Additionally, I had to make a new account just to post on this forum even though I had the same email address tied to the account for my game that I downloaded thtough Steam. Not sure if it is a related issue
Got any AntiVirus Software installed? If so, make an exception for the the following file path; Documents - Avalanche Studios - Generation Zero - Saves - Random Numbers. This can be done for Windows Defender as well.
I also just lost all my saves i have many hours of gameplay that i refuse to replay. please find a fix soon so i can get my saved data back.
i would also want to learn the origin of the problem so i can avoid this happening again
I am also experiencing the same issue with my saved game. I contacted Microsoft PC game pass support first and they directed me here. I see I am not alone with this and glad to see it is being looked into. Hopefully there is a fix available.
This has happen to me twice now. It seems to happen after I start the game on my Xbox and then go back to the PC version. I only started it on the console to see if the saves were cross platform/play anywhere.
I FIX! Do the following, create a new save game, look for the original save in that wsg folder, open it in notepad until you find the slot with the date and time it was your last save, close it, open again it with "Microsoft visual studio "or another code reader (I think notepad does not work). Copy all encrypted code, then open the save game you created and paste it into it! When you start write the wrong zone name, but then just enter and save in the game.
The first thing you need to know about saving your game in Just Cause 4 is that there does not appear to be any kind of manual save feature. What this means is that you cannot save whenever you would like to, and so you must instead rely on Just Cause 4 to auto-save instead.
You can tell when Just Cause 4 is autosaving because a floppy disc icon appears in the corner screen, indicating that an automatic save is in progress. As to when this occurs, you can expect to see the autosave trigger after the completion of every mission, objective and whenever your Army of Chaos Level increases. Simple stuff.
Keep your eyes open in the coming days for more Just Cause 4 content as we go big on the features that you can expect to see in the game, as well as a range of guides telling you how to get the stuff that you need the most from Avalanche Studios latest effort.
The central contention of this essay is that a just cause for war is a wrong that is of a type that can make those responsible for it morally liable to military attack as a means of preventing or rectifying it. This claim has many implications that conflict with assumptions of the currently orthodox theory of the just war. Among the implications explored in the text are that the requirement of just cause is logically and morally prior to all the other requirements of a just war, that this requirement governs all phases of a war and not just the resort to war, that it is thus impermissible to continue to fight a war once the just cause or causes have been achieved, that it is impermissible to fight at all in a war that lacks a just cause, that just cause is a restriction on the type of aim that may be pursued by means of war and is not a matter of scale, that a war that lacks a just cause may be morally justified even if it is not just, and that a belligerent can pursue both just and unjust causes in the same war, which may then have elements or phases that are just and other elements or phases that are unjust.
To save this article to your Dropbox account, please select one or more formats and confirm that you agree to abide by our usage policies. If this is the first time you used this feature, you will be asked to authorise Cambridge Core to connect with your Dropbox account.Find out more about saving content to Dropbox.
To save this article to your Google Drive account, please select one or more formats and confirm that you agree to abide by our usage policies. If this is the first time you used this feature, you will be asked to authorise Cambridge Core to connect with your Google Drive account.Find out more about saving content to Google Drive.
Do you have any conflicting interests? *Conflicting interests helpClose Conflicting interests help Please list any fees and grants from, employment by, consultancy for, shared ownership in or any close relationship with, at any time over the preceding 36 months, any organisation whose interests may be affected by the publication of the response. Please also list any non-financial associations or interests (personal, professional, political, institutional, religious or other) that a reasonable reader would want to know about in relation to the submitted work. This pertains to all the authors of the piece, their spouses or partners.
So Im enjoying my mostly stable game, no CTD's or bad textures, decent frame rate (with a little bit of macro stutter when loading new cells, no biggie, rather keep some of my texture mods), when suddenly out of nowhere I start CTDing like crazy.
1-2 As you play the game instances, references, and threads are created and recorded that are attached to many things from the story and quests, to items, to lights, and basically everything in the world all the way down to the bugs and fish (or critters, which can cause a lot of problems actually). If these references (lines of code) aren't executed, analyzed, and basically discarded properly (which can happen for a number of reasons) they will in essence get stuck. When that happens you get problems. Since the engine isn't smart enough it can only do what it is told and will keep compounding the same erronious code through repitition and eventually papyrus will overload. It is called save bloating because it makes your save file enormous with compacted errors and information that doesn't need to exist. When "the game" tries to read the save file and it is too massive and corrupt it becomes overwhelmed resulting in ILS and CTD.
Here are some steps on how to use it. You will want to have as clean a save as possible. Meaning in as small and empy a cell (room) with NO followers or NPCs. I use the last room of the Hall of the Dead in Whiterun for convenience.
8. Now open your save folder and you will see one or two files starting with the word EDIT. Copy and paste all the other files into a new folder on your desk top as a back up. Go back and name the EDIT files the same name as your last save file (copy paste).
When you say "repeat these steps" on number 10. What do you mean? Repeat them twice in a row before starting the game again? Or just repeat these steps periodically when playing (like say every 2-3 hours of gameplay)?
this might be something that is supposed to happen, but ive never seen it before. A Werewolf just attacked an Imperial Soldier, killed him, then was attacked by a bunch of other imperials, then the werewolf died, when I walk over to loot it, it is labeled as an Imperial Soldier.
By repeat these steps, I mean congruently, or back to back. So, "clean/new/hard save", use the papyrus scalpel and go through the steps, start and load the game and just let your character stand there for a bit. Save again and repeat the steps.
The things you listed don't really seem related to the advice I've given you. They seem mod related other than the issue you had with your followers, which again you should always dismiss before using any save cleaner.
I rarely have to do this and I have nearly 400 mods running 250 of which are plugins. I have never had the lock picking side affect. But, then again I use Kenmomod's lock pick pro mod because "I ain't got time for that".
The soul absorbtion issue is wierd, I've never experienced that and I doubt it has to do with the cleaning. Waiting awhile in game and/or sleeping for 72 to 744 hours in game can fix several issues and also allows things to load properly.
I just made the mother of all mod lists but I did not perform all the proper conflict resolution and I did not create all the patches (or patch if you want a single one) that is required to make everything play nice.
Not doing this will create save bloat in a very very short timespan since data from mod A gets overwritten by mod B... however now Mod A has a script that needs what was overwritten to be a certain way.. and it does not execute properly.
The Dragon Soul thing has to do with a mod that I have that adds animation to absorbing Dragon souls. There are multiple types of animations included in the mod, I selected only 1, but after using scalpel it tried to mix and match the various animations at random intervals.
Just STEP core on its own will not produce save bloat etc. So issues with for example save bloat come down to people adding more stuff on top without making sure what they add will play nice with the existing list.
If you do have a reproduceable CTD like you describe then it should be rather easy to locate the culprint mod and work from there. Make sure to run tes5edit and check for all conflicts and resolve them. Especially make sure to look for "cannot be resolved" errors that might have sneaked in during a mod update etc. Since those will always produce CTDs when the asset is trying to load.
c80f0f1006