I started with a new game.It's just a bug In the quest tracker. Some of my older saves have those tho.
If you finished the event till the end (Ends with May masturbating) then you've finished the event.
Did you use an older save or started a new game?
I can confirm that when loading a save prior to triggering the bugged script, and having replaced the map file as indicated, that this worked for me too.Did you try using the save where the bug is triggered or a save from before?
Unfortunately It won't work with save games that are saved in this map while the bug is triggered.
So in order to see if it fixed the problem you need a save from before and then enter the map again.
If you don't have a save from before see the next post below.
Yeah, I kind of theorized it was making a literal copy of the event context in the save file. Couldn't leave store during work event, but did visit to changing room, resaved, and reloaded. Didn't help. Only fix was loading the prior save, before entering store map.Yeah I noticed that sometimes stuff is saved inside save games and it will execute the code saved in the save file instead of the updated map file.
Sorry, no joy. Unless I'm missing something in your directions, on a quick test, it did nothing.I think I already fixed it. (I hope) Try the attached comment events file. Enable and then disabled autosave in setting then autosave should be disabled (for real) and should no longer jump to the autosave slot.
See this post:i have a huge roblem with the 2nd event with the nurse.. when i try to leave the PE-Class, the exact same 2 lines of dialogue just keep repeating and repeating, i can't move and also can't get into the settings, i run it on normal text speed too (Version 2.6 btw). i'd appreciate any help
Thanks for the reply its fixed now, it is a latest version im using UI improvement mod thats why its showing 1.8Download the latest version from the op? You're using version 1.8 it seems. I remember there being a bug in a previous version because I replaced some CG but forget to rename the files properly. There should be a bug fix somewhere in this topic, but the sane thing to do is to just download the latest version.
All saves are available in the original download, just move it from the saves folder to the main directory. Move the newest one and you can go to the gallery and watch what ever you want.hey guys
any save game with brother and sister sex?
please
Hate to be a PITA, but:release 2.6.1 update only fixes some bugs and has some other small additions/changes:
- Disabling Auto save should now work properly.
(If auto save in you game is set to disabled already, but it still auto saves.
You'll first need to enable auto save and then disable it again inside the settings menu.)
where is the galleryAll saves are available in the original download, just move it from the saves folder to the main directory. Move the newest one and you can go to the gallery and watch what ever you want.
next to the computer in Mays bedroom.where is the gallery
all the scenes will be unlocked?next to the computer in Mays bedroom.
Is seems to be a bug/glitch persistent in that particular save file. I have no idea how to fix that tho, since I have no clue what's going on and I simple don't have in depth knowledge of the code (Ruby) to attempt messing with it. Could only make things worse.Hate to be a PITA, but:
This may also be something saved in the saved files.
When the game first opens, you only have the option to load a save.
After trying different tactics, the "Autosave" fix wouldn't take until I saved a save with the fix ("Autosave Disabled"), shutdown the game, and restarted, loading that save. That seems to have worked. It still names slot #1 (#0?) "Autosave" instead of "File 1".
Crazybat, you may need to be a little more specific in the instructions for the fix. (Or find a away around saving that setting in a saved file.)
See my previous post. It seems to act buggy at some times while working perfectly fine at other times.I know, I know! I said "Take your break."
So take your break - this can wait - it is just FYI:
"Autosave" still acting funky:
Load previous night before sleeping (New "Autosave" function - "Autosave disabled")
Sleep
Next morning - save in slot #1 (0?) labeled "Autosave" - Location = May's Bedroom
Move May outside house - Neighborhood, College (doesn't matter)
Activate save function -
Slot #1 (0?) - still labeled "Autosave", now shows Location = Current Location (Neighborhood, College, etc.)
Loading that save file loads Current Location, not May's Bedroom
Checking "Autosave" setting in Items still shows "Disabled"
My speculation - It is saving Current Location in "Autosave" slot before allowing choice of "Load", "Save", or "Delete"
It is apparently overwriting the previous save, without warning. This is why I duplicate my saves, avoiding such confusion.
Only workaround available to me is avoid using slot #1 (0?) in my preferred save structure, i.e.:
Let "Autosave" file (first slot) continue to do its thing.
File 11 = Monday morning
File 12 = Tuesday morning
File 13 = Wednesday morning
File 14 = Thursday morning
File 15 = Friday morning
File 16 = Saturday morning
File 17 = Sunday morning
File 21 = Current morning
File 22 = Current afternoon
File 23 = Current everning
File 24 = Current night
Fortunately, one can change savefile names in Explorer while the game is running, without hiccups, unlike some other games. Still, through habit, I shut down game before renaming. So, "Save01.rvdata2" became "Save11.rvdata2".
Restarting game, loading "File 11", moving May outside the house, then choosing save function, and "Autosave" slot is magiclly filled with an "Autosave" (Save01.rvdata2) of the Current Location, leaving my "File 11" alone.
This may be useful to some, as long as they are aware anything saved in that "Autosave" slot will be overwritten.
Take your break.
EDIT:
"Autosave Disabled" should prevent any save action -
Pseudocode:
If
"Autosave" = 0
Then
Return
Else
do "Save", slot 0, "Autosave"
Return
Perhaps some settings, "Cars Enable/Disable", "Night Effect", "Fetishes", "Autosave Enable/Disable", etc should be considered system-wide with "Colors", "BGM", etc. and saved in a separate config file, instead of per savefile.
I won't argue with you, as I know far, far less than you do about it, but I'm not sure it was that particular save file. Any v2.6 save when loaded in v2.6.1 behaves the same way, unless the "Autosave" is enabled and disabled in v2.6.1, saved, shutdown and restarted. (Though I'm not sure the restart is necessary, its just habit to do so in these kinds of situations, and I didn't test it.)Is seems to be a bug/glitch persistent in that particular save file. ....