Game Crash: Character Node Bug In Engine 1.0.1 Rc2

Hey guys,

I've encountered a critical bug in version 1.0.1 rc2 of the engine that's causing the game to crash whenever I try to add or edit a custom character node position. This is a huge issue for me because most of my stages heavily rely on the character nodes feature. I've made sure to check if this issue has already been reported, and I couldn't find anything similar, so I wanted to bring it to your attention.

What version of the engine are you using?

I'm currently using version 1.0.1 rc2. Unfortunately, I didn't compile the engine myself, so I don't have a commit hash to provide. But I'm hoping the version number will be enough to help you guys track down the issue. I understand that providing a commit hash is ideal for those who compile the engine, as it allows for pinpointing the exact state of the codebase, but in this case, I'm relying on the official release version.

Which target are you using?

I'm experiencing this crash on Windows. I've indicated this by marking the checkbox next to "Windows" with an "X" in the original report. I haven't tested the engine on Linux or Mac, so I'm not sure if the issue is specific to the Windows target or if it affects other platforms as well. It's important to specify the target platform when reporting bugs, as issues can sometimes be platform-specific due to differences in operating systems, drivers, or hardware. By clearly stating that I'm on Windows, the developers can focus their efforts on investigating the issue within the Windows environment.

Explain your issue

The core problem: Whenever I try to interact with character nodes – whether it's adding a new node or editing an existing one – the game just crashes. This happens in any stage, making the issue incredibly disruptive to my workflow. As I mentioned earlier, character nodes are a crucial part of my stage design, so this bug effectively prevents me from working on my projects.

I've tried various things to see if I could narrow down the cause, but the crash seems to occur consistently whenever character node positions are involved. This leads me to believe there might be a fundamental issue within the character node system itself, specifically in how the engine handles the addition or modification of these nodes. It's possible that there's a memory access violation, a null pointer dereference, or some other type of error that's triggered when the engine attempts to manipulate the character node data.

To reproduce the bug: It's pretty straightforward, guys. Just try to add a new character node in any stage, or try to edit the position of an existing one. The game should crash pretty quickly. I've included a screenshot of the crash handler in my original report, which might provide some additional clues. Crash handlers often provide valuable information such as the call stack, which shows the sequence of function calls that led to the crash. This information can be incredibly helpful for developers in pinpointing the exact location in the code where the error occurred.

Impact: This is a critical error for me because it completely blocks my progress. I can't work on my stages without being able to adjust character nodes. I really hope you guys can look into this soon!

Additional Information:

I've attached a screenshot of the crash handler to this report. Hopefully, this will give you guys some more insight into what's going on. The screenshot shows the error message and the call stack at the time of the crash. The call stack can be particularly useful because it shows the sequence of function calls that led to the error, allowing the developers to trace the execution path and identify the source of the problem. In addition to the screenshot, I'm happy to provide any further information or assistance that might be helpful in resolving this issue.

I'm really looking forward to hearing back from you guys and getting this issue resolved. Thanks for your hard work and dedication to the engine!

I appreciate you taking the time to read my bug report, and I hope the information I've provided is helpful in tracking down the cause of the crash. I'm eager to see this issue resolved so I can get back to working on my stages. If there's anything else I can do to assist in the debugging process, please don't hesitate to ask. I'm committed to helping make the engine as stable and reliable as possible.

I'm also wondering if anyone else has experienced this issue. If you have, please chime in and let us know! It's always helpful to have more data points to work with. The more information we can gather about the circumstances under which the crash occurs, the easier it will be to identify the root cause and implement a fix. Sharing your experiences can also help to prioritize the bug fix, as it provides a clearer picture of how widespread the issue is and how many users are being affected. So, if you've encountered this character node crash, please don't hesitate to share your details!

In the meantime, I'll keep experimenting with the engine to see if I can uncover any other patterns or triggers for the crash. I'll also keep an eye out for any updates or fixes that might address this issue. I'm confident that the developers will be able to resolve this problem, and I'm grateful for their ongoing efforts to improve the engine. I'm excited to see what the future holds for this project, and I'm committed to doing my part to help make it the best it can be.

Please check first if your issue haven't already been reported yet.

I did my best to search for similar issues before posting, but it's always possible I missed something. If anyone knows of a similar report, please let me know. It's important to avoid duplicate reports, as they can clutter the issue tracker and make it harder for developers to find the information they need. However, even if there is a similar report, it's still helpful to add your own details and observations, as they may provide additional context or insights that can help in resolving the issue.

I understand that bug reporting is a crucial part of the software development process, and I'm committed to providing as much information as possible to help the developers fix this issue. I believe that clear and detailed bug reports are essential for ensuring the quality and stability of the engine, and I'm happy to contribute my time and effort to this process. I'm also grateful for the developers' responsiveness to bug reports and their commitment to addressing issues promptly and effectively.

I'm confident that by working together, we can make the engine even better! Thanks again for your help and support.