I am currently getting this error message when trying to load a save on this map. It softlocks the game and I cannot progress this save. Let me know if you guys have a solution thanks.
OS: Windows 10
An RPG adventure with an added twist, Body Modification! Manipulate these pure maidens to fulfill your darkest desires. · By
I'm also getting this crash. For me it happens on map E after interacting with the devils which show up (after talking to the nun, after placing all 4 binding circles on the map).
Crash log has this in it
12:20:08 ==== An exception occured at conductor.tjs(81)[(function) timerCallback], VM ip = 111 ====
12:20:08 -- Disassembled VM code --
12:20:08 #(81) obj = getNextTag(); // 次のタグを得る
12:20:08 00000111 calld %1, %-2.*12() // *12 = (string)"getNextTag"
12:20:08 -- Register dump --
12:20:08 %-5=(void) %-4=(int)0 %-3=(object)(object 0x041DA51C:0x041DA51C)
12:20:08 %-2=(object)(object 0x00E1F994:0x00000000) %-1=(object)(object 0x041D9E90:0x041D9E90)
12:20:08 %0=(void) %1=(void) %2=(int)0 %3=(int)0 %4=(int)1786758 %5=(void) %6=(int)1
12:20:08 %7=(object)(object 0x013E2408:0x041DB820) %8=(object)(object 0x041DB820:0x041DB820)
12:20:08 %9=(void)
12:20:08 ------------------------------------------------------------------------------------------
12:20:08 trace :
12:20:08 エラーが発生しました
ファイル : questE-battleEVEBTL-6-E.ks 行 : 34
タグ : return ( ← エラーの発生した前後のタグを示している場合もあります )
シナリオファイルに変更があったため return の戻り先位置を特定できません
Now when I try and load the save it crashes as well, so I can't progress past this point :(Hey, we have been working on this issue, it's not forgotten, just a little tricky. Quick question, when you downloaded the newest build, did you transfer in old save data from a previous build that you are trying to now load? Or are you loading from a fresh save?
Unfortunately we've found there is some incompatibility with using old save data in specific areas of the game that we have not yet found a solution for. This map was working as intended from fresh saves in previous builds though, so this info will help us figure out when the error may have started.