 |
same problem. 1-4-LT1.save (336,593 bytes) 1-2-LT1.save (330,198 bytes) |
|
|
JackalMech, please provide your save. |
|
|
I apologize, I almost thought I removed the save, but alas hopefully it uploads. 1-1-LT1.save (329,798 bytes) |
|
|
i am having the same issue but my game version 0.20.9, i dont know if that makes a difference or not but imma post my save here if thats ok. ok apparently my actual saves are too big to upload. so im putting my quick save quick-1-LT1.save (502,741 bytes) |
|
|
Same error for me. Hope you guys can fix it. 2-3-LT1.save (442,125 bytes) |
|
|
yep, same problem 3-1-LT1.save (456,922 bytes) |
|
|
Same problem here 1-3-LT1.save (419,448 bytes) |
|
|
I have the same issue but am in retain how to provide my save |
|
|
Same here. This needs to be fixed for the next release. I can't progress with the main story quick-6-LT1.save (483,684 bytes) |
|
|
Part of the issue seem s to be that in case of Maria, after loading the affected save, M_maria and store.machines['maria'] do not refer to the same object. This can be verified by this expression: M_maria is store.machines['maria'] which is True normally when there is no bug (like for any other state machine as well) but false in this case. As a consequence, all triggers applied to store.machines['maria'] do not affect M_maria, leading to the situation that the state of the latter does not advance further. I did not find out what exactly leads to the save creating a separate instance of StateMachine for M_maria that is different from the one in the store, nor how this situation could occur in the first place, however. The bug can be temporarily solved with a command like M_maria = store.machines['maria'] after an affected save is loaded, letting the story progress normally. However, the bug is not permanently solved as this has to be done each time an affected game is saved and re-loaded. |
|
|
same problem |
|
|
4-2-LT1.save (492,549 bytes) |
- Anonymous