-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempting to create a story results in error spam due to null state #34
Comments
Confirmed, I tried to use inkgd on Godot 3.3.3 stable, standard, and it refuses to work. inkgd/addons/inkgd/runtime/call_stack.gd Line 397 in 3127d99
The reason of error was self.current_thread being null |
I'm having near-identical issues. Is the inkgd project inactive? |
Sorry for taking so long to reply folks, yeah, it's a bit inactive. I should probably update the README (and remove the trailing star in the ink library). I haven't had time to work on it in almost a year now. I'll try to find some time to investigate soon. |
Is this happening only in Windows? I'm not seeing this issue in Linux (Debian 11). Here's my example for reference:
Can you confirm you have |
sorry for the late response- I do indeed have the singleton set up, and yes it has been occurring on windows. I even tested it with the provided example project and ran into the same issue. I haven't tried it with the latest release, so when I get a chance, I'll do that and let you know if it works. |
I have the same issue using Godot v3.4.2, and I can't figure it out. It feels like the plugin refuses to create a story (fails happens once InkStory.new(json_story) is called, inside the InkPlayer), because _story (or sometimes _story._state) is null. InkPlayer nodes created in editor still work, but I can't change their Stories dynamically (or create new InkPlayer node), which is pretty inconvenient. :/ |
Which version of inkgd? Which OS? Does it happen after an export or while debugging? |
@ephread It happens while debugging, I did not try to export my project yet. |
I can get the example project to run, and you are loading new Stories in it from code, so there must be something I'm doing wrong. But I can't figure out what. |
I managed to solve my issue ! I was trying a stupid method to create the ink_file like
replacing that with a simpler
makes everything works as expected. Still no idea how this resulted in such a weird error though. :D |
Describe the bug
Attempting to create a new story via Story.new() repeatedly spams the error log with errors until the game is closed. The exact error differs every time but all of them stem from setgets being called while state is null
To Reproduce
Create a new story while running inkgd on godot 3.3 stable
Expected behavior
Creating a new story should work instead of crashing the game.
Ink files
N/A
Environment:
The text was updated successfully, but these errors were encountered: