Reply to Re: New D-Mod: Cursed Blades Part 1: Charlie's Legacy
If you don't have an account, just leave the password field blank.
"@Robj can you check if this is a dmod issue? Otherwise it may be another bug in the freedink source."
I tested your save on windows FreeDink 109.6 and Dink Smallwood HD 1.97 - everything works fine.
Weird thing too, the north barrier was indeed down for both FreeDink 109.6(windows) and DinkHD (as it should be since puzzle is solved). When I loaded the save file on FreeDink 109.6(Linux), it was not down, and the puzzle reset itself. Also yeh, when I tested on the FreeDink Linux build the oasis entrance screen lagged really bad, and hitting the pole crashed the game.
The lag tells me that the FreeDink engine somehow bugged out and maxed out all the scripts and variables again, it was the same thing that happened when it did it on the tile puzzle screen. Maybe you didn't notice the lag, because you were using your patched version, and you fixed that issue, the puzzle resetting could also be a symptom of the unpatched version(I didn't update the Freedink version I was using on my Linux VM with your patched one yet).
I did find a typo in one script on that screen where sp_brain(16) instead of sp_brain(¤t_sprite, 16) was used, and my first instinct was maybe for some reason FreeDink Linux had a problem with this typo, instead of ignoring it like the other engines do - but no, I fixed it, and still experienced the lag and crashing when hitting the pole. Anyway, I've flagged that typo to fix if I do another update(it's not worth it's own update, since it doesn't even affect anything in game)
There's only 2 scripts on that screen, both basic. So, that one is an even bigger mystery to me.
So yes, this crash seems to be another issue in the FreeDink Linux source.
I tested your save on windows FreeDink 109.6 and Dink Smallwood HD 1.97 - everything works fine.
Weird thing too, the north barrier was indeed down for both FreeDink 109.6(windows) and DinkHD (as it should be since puzzle is solved). When I loaded the save file on FreeDink 109.6(Linux), it was not down, and the puzzle reset itself. Also yeh, when I tested on the FreeDink Linux build the oasis entrance screen lagged really bad, and hitting the pole crashed the game.
The lag tells me that the FreeDink engine somehow bugged out and maxed out all the scripts and variables again, it was the same thing that happened when it did it on the tile puzzle screen. Maybe you didn't notice the lag, because you were using your patched version, and you fixed that issue, the puzzle resetting could also be a symptom of the unpatched version(I didn't update the Freedink version I was using on my Linux VM with your patched one yet).
I did find a typo in one script on that screen where sp_brain(16) instead of sp_brain(¤t_sprite, 16) was used, and my first instinct was maybe for some reason FreeDink Linux had a problem with this typo, instead of ignoring it like the other engines do - but no, I fixed it, and still experienced the lag and crashing when hitting the pole. Anyway, I've flagged that typo to fix if I do another update(it's not worth it's own update, since it doesn't even affect anything in game)
There's only 2 scripts on that screen, both basic. So, that one is an even bigger mystery to me.
So yes, this crash seems to be another issue in the FreeDink Linux source.
