Skip to content

"Not Enough Free Space to Save Game" -- Unable to quick save in BG2EE

semiticgoddesssemiticgoddess Member Posts: 14,903
I cannot use quick saves in my modded BG2EE game.

I recently lost an install to a weird Ascension reinstall issue, so I copied over my clean install from the Steam folder (I keep an unmodded install there) and moved it outside Program Files, as usual. I installed Ascension->CDTweaks->SCS->Jimfix and experienced no problems, as usual. However, I can no longer quick save in the modded install, as it gives me the error message "Not Enough Free Space to Save Game."

I've looked up other problems with this error message and this one doesn't seem to be the same. Restarting the computer, renaming the BG2 folder in Documents so the game creates a new one on startup, deleting existing save games including quick saves, and freeing up room in OneDrive all fail to solve the problem. There is plenty of disc space on my computer.

I can still quick save in vanilla (using the same save files), but that doesn't help me play with mods, and my modded install can't really get any cleaner. My current modded install is identical to my previous modded install, which did not have this problem. The only difference is a slight update to Ascension, which should have had no impact. Also, regular saves and auto saves are unaffected, though I did get the same error message when making an area transition (leaving the Copper Coronet) that did not actually have an auto save attached to it.

Comments

  • sarevok57sarevok57 Member Posts: 5,975
    have you checked your savename.2DA? perhaps the quick save one got deleted or was set to 0

    for me, quick save is:
    SLOTNAME: 103050
    START: 7
    COUNT: 1
  • semiticgoddesssemiticgoddess Member Posts: 14,903
    @sarevok57: I never thought to check that! I just got around the issue by deleting the savename.2da from the override folder. I can now quick save normally.

    This is what I had before in that .2da file. I think the problem is that the SLOTNAME string references were all outside the boundaries of the dialog.tlk file, as the last string reference in my install is 103240, and all of the SLOTNAMES are much higher.
    2DA V1.0
    103049
               SLOTNAME   START      COUNT      
    0          103839      0          1          
    1          103840      7          4          
    2          103841      2          1          
    3          103842      3          1          
    4          103843      11         4
    5          103844      5          1          
    6          103845      6          1          
    7          103840      7          1          
    8          103846      8          1          
    9          103847      9          1          
    10         103848      10         1          
    11         103843      11         1
    12         103849      12         1
    13         103850      13         1
    14         103851      14         1
    15         103852      15         1
    16         103853      16         1
    17         103854      17         1
    18         103855      18         1
    19         103856      19         1
    20         103857      20         1
    21         103858      21         1
    22         103859      22         1
    23         103860      23         1
    24         103861      24         1
    
    I think the root cause might have been a CDTweaks component which offered to rename save games. I'm guessing it put in those out-of-bounds string references and prevented the game from reaching them properly.
  • sarevok57sarevok57 Member Posts: 5,975
    ah mods, gotta love the bugs they cause :)
  • KatsukiKatsuki Member Posts: 1
    @sarevok57: I never thought to check that! I just got around the issue by deleting the savename.2da from the override folder. I can now quick save normally.

    This is what I had before in that .2da file. I think the problem is that the SLOTNAME string references were all outside the boundaries of the dialog.tlk file, as the last string reference in my install is 103240, and all of the SLOTNAMES are much higher.
    2DA V1.0
    103049
               SLOTNAME   START      COUNT      
    0          103839      0          1          
    1          103840      7          4          
    2          103841      2          1          
    3          103842      3          1          
    4          103843      11         4
    5          103844      5          1          
    6          103845      6          1          
    7          103840      7          1          
    8          103846      8          1          
    9          103847      9          1          
    10         103848      10         1          
    11         103843      11         1
    12         103849      12         1
    13         103850      13         1
    14         103851      14         1
    15         103852      15         1
    16         103853      16         1
    17         103854      17         1
    18         103855      18         1
    19         103856      19         1
    20         103857      20         1
    21         103858      21         1
    22         103859      22         1
    23         103860      23         1
    24         103861      24         1
    
    I think the root cause might have been a CDTweaks component which offered to rename save games. I'm guessing it put in those out-of-bounds string references and prevented the game from reaching them properly.

    Hello, I have the same problem, how did you fix it? which .2da file? please thank you
  • zeuszeus Member Posts: 3
    You just need to close the "OneDrive”.
  • zeuszeus Member Posts: 3

    Katsuki wrote: »
    @sarevok57: I never thought to check that! I just got around the issue by deleting the savename.2da from the override folder. I can now quick save normally.

    This is what I had before in that .2da file. I think the problem is that the SLOTNAME string references were all outside the boundaries of the dialog.tlk file, as the last string reference in my install is 103240, and all of the SLOTNAMES are much higher.
    2DA V1.0
    103049
               SLOTNAME   START      COUNT      
    0          103839      0          1          
    1          103840      7          4          
    2          103841      2          1          
    3          103842      3          1          
    4          103843      11         4
    5          103844      5          1          
    6          103845      6          1          
    7          103840      7          1          
    8          103846      8          1          
    9          103847      9          1          
    10         103848      10         1          
    11         103843      11         1
    12         103849      12         1
    13         103850      13         1
    14         103851      14         1
    15         103852      15         1
    16         103853      16         1
    17         103854      17         1
    18         103855      18         1
    19         103856      19         1
    20         103857      20         1
    21         103858      21         1
    22         103859      22         1
    23         103860      23         1
    24         103861      24         1
    
    I think the root cause might have been a CDTweaks component which offered to rename save games. I'm guessing it put in those out-of-bounds string references and prevented the game from reaching them properly.

    Hello, I have the same problem, how did you fix it? which .2da file? please thank you


    Just close the "OneDrive"
Sign In or Register to comment.