Feedback collection for version 0.25.2
Added 2024-06-08 04:50:23 +0000 UTCHello patrons!
We just released version 0.25.2;
Yesterday we made a post to collect your feedback and learn about any issues you may have found. It helped us a lot to make things more stable.
So I opened this new one to collect more of your input and I would love to hear your thoughts on this new version.
Thank you very much!
Comments
General note : the game is still a bit laggy. It does not meet the performance of earlier versions ... Now my results with the new version. A lot of crashes. Not later than three minutes the next crash happens. Some examples: LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 000001F784A30000 canary == 0x1c != 0xe3 Crash in runnable thread Foreground Worker #1 LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 000001E2F5D40000 canary == 0x1c != 0xe3 Fatal error! LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 000001A56EA50000 canary == 0x1c != 0xe3 LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 000001A84C760000 canary == 0x1c != 0xe3 Fatal error! LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 0000018119640000 canary == 0x1c != 0xe3 LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Core\Private\HAL\MallocBinned2.cpp] [Line: 1438] FMallocBinned2 Attempt to realloc an unrecognized block 0000025604720000 canary == 0x1c != 0xe3 And sometimes the game simply freezes. New problems wih "Controls" Now I see three columns for the settings. But some of the colums include free positions. I do not really understand it. I tried three different game controllers. None of them did anything ... Specific questions: Section "General" "Alternate Mode". What is this ??? What is the meaning of this ??? Section "Movement" "Float Down" "Float Up". What is this ??? Is there any detailed explanation for this ? Some proposals/wishes The Game shows "Move Right", "Move Left" and "Move Backwards". But this is not what the game does. It really uses "Turn to Right and Move", "Turn to Left and Move", "Turn 180° and Move". For my use I would pefer to have "Step to Right", "Step to Left" and "Step Back" (i.e. no change in direction orientation) Up to now I am using a Gamecontroller together with progam JoyToKey. JoyToKey is mapping the Gamecontroller to Mouse- and/or Keyboard-Events. With this setup the game was working satisfactorily. Using the current program version I was not able to find settings to have the previous state (???!!!).
Tantarex
2024-06-10 23:15:05 +0000 UTCThe saves from version 0.25.1 are not compatible with version 0.25.2 because the problem we had was that when you kill an enemy, this enemy wasn't being added to the file saying that their new state was now "dead". I also improved the way the location of enemies is loaded and how consistently Merishya will follow you, so so all the issues you listed, except for the last two, might be happening because you played from an incompatible save file. The weapons floating until you get close to enemies is unfortunately a compromise we had to do until we redo the combat and fix the AI so it's not as heavy on the CPU as it was before. We had to make that the enemies are only processed when they are 15 meters away from Kalyskah. For the crashes, we have collected a good number of logs and now we are going through them and investigating what's causing the issue. Thank you very much for the thoroughly feedback, really really appreciated!
Kalyskah Team
2024-06-08 15:33:11 +0000 UTCSome new bugs that I have encountered in Version 0.25.2 • NPCs are floating in mid-air around the bridge area before you meet Nemesis. • Map markers would be helpful for the Nemesis quest. • I have not freed Merishya yet, but she still appears in cutscenes. She is not following me, just popping in during cutscenes. This could be because I beat Gremnoch in 0.25.1 • Some of Nemesis's dialogue is skipping, and the camera can be a bit janky during that cutscene. • The enemy respawning glitch seems to be fixed, but only on saves where enemies were killed in version 0.25.2. Saves from version 0.25.1 still have enemies respawning when loaded. • Gremnoch still spawned after I completed the boss fight. Note that I beat him in version 0.25.1. • Enemies seem to be invisible with only their floating weapons being visible, and then once you get closer to them, they spawn in. • I still experienced some crashes, it still usually happens when I load a 0.25.1 save or run into a new area or room.
ALDER628
2024-06-08 09:19:25 +0000 UTC
