RPG Developer Bakin

RPG Developer Bakin

1773320143 25 Sep, 2023 @ 1:43am
Fatal Error Report after 1.4.0
Hi!bakin group! here is my newest bug report!
1.When an event detects collision with the character, the character's raycast also becomes a part of the character's collision. Although the raycast area of the character does not trigger a successful collision detection, when the event moves, its collision body obstructs the character's raycast area and pushes or pulls the character along with it. (Please note that throughout this entire process, the character never actually makes contact with the event, but the raycast portion of the character comes into contact with the moving event and gets pushed away by it).
2.If you save the game and exit during Free Layout in reality, the Free Layout will disappear when you load the save, which will affect game features like the quest hint system.
3. When using the feature to increase or decrease a character's ability values, the game engine modifies not the character's inherent ability values but rather the combined values of the character and their equipment. Due to this flawed logic, the gameplay of freely adjusting ability values cannot be utilized, as equipment becomes completely ineffective when the decreased ability value surpasses the value provided by the equipment.
4.Occasionally, characters do not land on the flat plane of the map, causing their Y-coordinate to be slightly lower than the walkable surface of the map, making it impossible for them to move properly. Using the "start player falling" command before entering the map can resolve this bug, but it remains a concerning issue.
5. It appears that the engine still suffers from uncleaned cache issues. When I run large maps after exporting the game, severe frame drops and resolution reduction occur. However, these problems do not persist when I save and restart the game. Therefore, I suspect it might be a caching problem.

Several essential features are strongly needed:
1.Improved efficiency in scanning the minimap. When using the minimap in large maps, players can only uncover three map tiles with each step, making it difficult to reveal the entire minimap, especially since map borders remain undiscovered.

2.The ability to identify a player's equipment name or ID in advanced variables. Bakin already has the capability to switch a player's equipment at any time, but the lack of equipment identification significantly hinders the use of other features and innovative gameplay.

3.The player's physical collisions are too intense, particularly when creating 3D action games. The drastic camera collisions resulting from player-terrain collisions greatly affect the game's quality.

Best wishes for Bakin's continued improvement,
from Dracul Aurion, an independent developer using Bakin to develop an ARPG.
Last edited by 1773320143; 25 Sep, 2023 @ 1:49am
< >
Showing 1-3 of 3 comments
sylardean 25 Sep, 2023 @ 5:36am 
LMAO!
SANA  [developer] 26 Sep, 2023 @ 1:34am 
Hi, 1773320143-san

Thank you for your report and suggestions.

For 1 and 5, if possible, could you please give us the actual data to reproduce the problem?

3 is that the lower limit of ability value reduction should be the amount excluding the increase in ability value with equipment.

For 2, if you check the "Save Display State" checkbox in the free layout, it seems to save the data.
If there is a case where this does not work, it would be appreciated if you could provide a setting example or data if possible.

---

If you could share your project file, please upload the data to a file sharing service such as Google Drive, and contact us using this form with the link along with the link and steam name of this thread.
https://smilegamebuilder.com/en/contact/

Thank you for your cooperation. :-D
1773320143 26 Sep, 2023 @ 6:18pm 
Hi, Sana! Sorry I cannot provide the project for it is already a commercial demo to the publisher. But i could show you more details for you guys to reproduce the bug!
For bug no.1, I prepared you a gif to show the problem in DISCORD.
For bug no.3, you could create an armour(HP+300), then reduce the player's MAX HP to 1, than you could find that the armour is disabled(HP+0), even though you restore the player's HP, the problem still persists. Besides,if you restore player's MAX HP to 500, the inherent MAX HP value is 200. For bug5, I have used some 2K resolution texture 3d model in the map. After i changed the texture into lower ones, the problem solved.Hope these details are useful!
< >
Showing 1-3 of 3 comments
Per page: 1530 50