The proof Dooping is not the Prob. It's Exploring and doing Side Missions.
Writing to file functions as intended, as it's stopping at it's file size limit of 8192KB. Player information being stored in memory is functioning as intended, otherwise the application would throw an error when you exceeded 8192KB. The 8MB limit is a legacy limitation from older versions of REDengine. In those versions, 8MB was more than enough, so there was no reason to know, or assume, that now 8MB wouldn't be enough.I don't understand why you are dissecting my words, but either way I'm not trying to discount any work that anybody is doing here. The work is good. There's nothing wrong with it. I'm simply saying that us as people that aren't on the development team cannot say without a doubt that we know the root cause of what's going on so we shouldn't make absolute statements in that regard.
I don't want people to feel suppressed from presenting other information due to somebody declaring that "We've found the exact issue". There are all sorts of various cases of what might actually be wrong. Maybe the "bloat" is working as designed but the writing to disk isn't. Maybe they have a save clean-up algorithm but it's not being triggered at the right moment. Etc.
The exploration and side missions aspect of the file bloat is something that we've discovered and known for a little while.The proof Dooping is not the Prob. It's Exploring and doing Side Missions.
Well, there are instances of the game keeping bodies in memory indefinitely. Like if you exploit back into Konpeki plaza, all of the bodies from The Heist mission, dead or alive, are still there. Including the loot they dropped. So this could point to a garbage collector process either not functioning at all, or just not functioning correctly. So far in my 49 hours of playing, before I stopped after learning about this issue, I had yet to run into an issue with bodies persisting. However, I know it's an issue for some people with dead robots never being cleaned up, or people reporting stolen cars remaining where they left them for multiple in-game days.I did a quick test regarding bodies and crates. I entered the area of an organized crime hustle which had 12 scavengers, and conveniently, the capacity for 12 bodies in the crates (6 crates with 2 capacity each). I incapacitated all of the scavengers and looted all items in the area, including items dropped from the bodies, but left all bodies where they fell. I then saved and checked file size. I then stored all 12 bodies in the provided crates and checked again. The difference was a reduction in file size of about 10k.
Certainly this single test is very limited, especially since any number of things could have gone on during the time I was storing the bodies. For example, some other garbage collection method could have run in the mean time between saves. It's just another bit of info to add to the list.
I also still do not know for sure if and under what conditions bodies might naturally de-spawn. Others have reported bodies and one time NPCs persisting forever, but is that all bodies? Most bodies? Just certain ones? I have no idea. If the average body does eventually de-spawn naturally, then any space savings from putting them in crates would be only temporary when compared to leaving them on the ground.
Were you able to keep track of how much your file size increased when you entered a new district?Tested the duping glitch at a terminal; can confirm, it does NOT increase the save file size.
Made 100 Epic and legendary components, a few weapons and about a thousand of the silly paintings you can sell for money. Save file doesn't change size.
Ironic since our games were corrupted by using game mechanics rather than exploits.
As for natural file size increase: side missions such as the gigs and ncpd missions account for about 2kb each. The main missions, estimate about 50-100kb depending on the mission. (at least act 1 and the beginning of act 2. Havent progressed too far).
I don't really know if this contributes to save file bloat or just another problem/bug that this game should fix but in my case, even cops and car traffic is persisting in one place for so long if you disrupt them. Example in my case, I shot an officer outside no-tell motel then it caused traffic, after I evaded the police they just stayed there after a while. When I went back there to finish Lizzy's quest, the officers and car traffic are still outside doing nothing.[...]
Well, there are instances of the game keeping bodies in memory indefinitely. Like if you exploit back into Konpeki plaza, all of the bodies from The Heist mission, dead or alive, are still there. Including the loot they dropped. So this could point to a garbage collector process either not functioning at all, or just not functioning correctly. So far in my 49 hours of playing, before I stopped after learning about this issue, I had yet to run into an issue with bodies persisting. However, I know it's an issue for some people with dead robots never being cleaned up, or people reporting stolen cars remaining where they left them for multiple in-game days.
I've linked all my tests in this previous post.Were you able to keep track of how much your file size increased when you entered a new district?
Offset(h)
007FFF50 61 74 61 80 01 00 00 FF FF FF FF 9F DE BF 00 EC ata€...ÿÿÿÿŸÞ¿.ì
007FFF60 00 00 00 88 69 74 65 6D 44 61 74 61 81 01 00 00 ...ˆitemData....
007FFF70 FF FF FF FF 9A DF BF 00 1C 00 00 00 88 69 74 65 ÿÿÿÿšß¿.....ˆite
007FFF80 6D 44 61 74 61 82 01 00 00 FF FF FF FF C5 DF BF mData‚...ÿÿÿÿÅß¿
007FFF90 00 1C 00 00 00 88 69 74 65 6D 44 61 74 61 83 01 .....ˆitemDataƒ.
007FFFA0 00 00 FF FF FF FF F0 DF BF 00 59 00 00 00 88 69 ..ÿÿÿÿðß¿.Y...ˆi
007FBE40 78 B9 A4 01 13 01 00 00 8E 43 6F 6D 70 6F 6E 65 x¹¤.....ŽCompone
007FBE50 74 73 53 74 61 74 65 C0 02 00 00 FF FF FF FF 7C tsStateÀ...ÿÿÿÿ|
007FBE60 B9 A4 01 D1 00 00 00 9A 43 61 6D 65 72 61 43 6F ¹¤.Ñ...šCameraCo
007FBE70 6D 70 6F 6E 65 6E 74 52 65 6E 64 65 72 4C 61 79 mponentRenderLay
007FBE80 65 72 FF FF FF FF FF FF FF FF 4D BA A4 01 3E 00 erÿÿÿÿÿÿÿÿMº¤.>.
007FBE90 00 00 A1 74 7F 00 45 4E 4F 44 ..¡t..ENOD
MaxProfileSize = 4194304
MaxSaveSize = 8388608
MaxSaveSizeTotal = 12582912
MaxSettingsSize = 4194304
MaxProfileSize = 8388608
MaxSaveSize = 16777216
MaxSaveSizeTotal = 25165824
MaxSettingsSize = 8388608
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00800AF0 95 43 6F 6D 70 6F 6E 65 6E 74 73 53 74 61 74 65 •ComponentsState
00800B00 53 79 73 74 65 6D FF FF FF FF 2E 03 00 00 F9 70 Systemÿÿÿÿ....ùp
00800B10 A4 01 13 01 00 00 8E 43 6F 6D 70 6F 6E 65 74 73 ¤.....ŽComponets
00800B20 53 74 61 74 65 2F 03 00 00 FF FF FF FF FD 70 A4 State/...ÿÿÿÿýp¤
00800B30 01 D1 00 00 00 9A 43 61 6D 65 72 61 43 6F 6D 70 .Ñ...šCameraComp
00800B40 6F 6E 65 6E 74 52 65 6E 64 65 72 4C 61 79 65 72 onentRenderLayer
00800B50 FF FF FF FF FF FF FF FF CE 71 A4 01 3E 00 00 00 ÿÿÿÿÿÿÿÿÎq¤.>...
00800B60 21 83 7F 00 45 4E 4F 44 !ƒ..ENOD
The problem is that the crafting system was designed with mass crafting in mind. Put the levelling aside, it's the random nature of crafted gear too. All the weapons you craft will get random stats from a list of potential stats. All the armour you craft will get a random number of mod slots (0-4 for inner and outer chest, 0-3 for everything else). Some of the mods you craft will be common to epic. Did they honestly expect people to craft once and just settle with whatever bad result they got? There's no way it was not intended to be mass crafted.Final bit of testing for tonight, I think.
Just crafted 100 maxdoc 2's. Save game went from 3.82 to 3.84. Disassembled 100 maxdoc 2's. Save game is still 3.84. Disassembled my remaining 40 maxdoc 2's. Save game is still at 3.84.
It seems to me that for now we should *not* mass craft stackable items, be it consumables or grenades.
You have to make file extensions visible in File Explorer. In the ribbon, click View. Under SHow/Hide tick "File name extensions".how do i name a file ini ???
That is clear but what i mean is, as we Edit the values of the save sizes can anybody say that they are work as intended?800B60 = 8391520 which is greater than the original file size limit of 8388608Code:Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00800AF0 95 43 6F 6D 70 6F 6E 65 6E 74 73 53 74 61 74 65 •ComponentsState 00800B00 53 79 73 74 65 6D FF FF FF FF 2E 03 00 00 F9 70 Systemÿÿÿÿ....ùp 00800B10 A4 01 13 01 00 00 8E 43 6F 6D 70 6F 6E 65 74 73 ¤.....ŽComponets 00800B20 53 74 61 74 65 2F 03 00 00 FF FF FF FF FD 70 A4 State/...ÿÿÿÿýp¤ 00800B30 01 D1 00 00 00 9A 43 61 6D 65 72 61 43 6F 6D 70 .Ñ...šCameraComp 00800B40 6F 6E 65 6E 74 52 65 6E 64 65 72 4C 61 79 65 72 onentRenderLayer 00800B50 FF FF FF FF FF FF FF FF CE 71 A4 01 3E 00 00 00 ÿÿÿÿÿÿÿÿÎq¤.>... 00800B60 21 83 7F 00 45 4E 4F 44 !ƒ..ENOD
That said there is absolutely nothing you can do about the corrupted saves, they are gone because the end of the file actually contains a lot of critical shit (which is kind of a bad design tbh) so there will be no way to recover these saves.