search

TheSchnappi / articy2renpy

A converter for artify:draft JSON to Ren'Py *.rpy script files.
https://lemmasoft.renai.us/forums/viewtopic.php?f=51&t=59921
MIT License
16 stars 2 forks source link

Script executes with exit code 0, but not all files are created #3

Open yuniyhimik opened 11 months ago

yuniyhimik commented 11 months ago

Hello! I'm testing the script, with a very simple articy project of just few dialogue fragments, few choices, 1 variable and 2 entities for speakers. I'm executing the script, and it looks like it's going through the stages well. It creates game_variables and end_labels files, but it never creates the actual dialogue files. And it doesn't give an error.

INFO:root:Combining label finished INFO:root:Create dialogue file for end_node INFO:root:Step 6: Create File with End Labels INFO:root:Step 7: Create global variable definition file

Process finished with exit code 0

I can't understand the reason why the dialogue files are not created. Would appreciate help.

SageGC commented 11 months ago

I am also running into this and a bit stumped. Was really excited and would love to get it to work.

SageGC commented 11 months ago

Found the culprit (I assume). Line 524 and 526 in main.py were missing a slash. Once added, the dialogues appeared. And then, to my suprise, I guess they had been generating one folder up the whole time. Unfortunately Parsing the Script still failed on launch and has a bunch of other different errors, but at least everything is generated now and I can hopefully clean up manually from here.

yuniyhimik commented 10 months ago

Thanks for replying mate. Though I'm confused) This is what I see in those lines, can't see the need for slash image Did you figure out the other issues by now?

SageGC commented 10 months ago

Should be part of the filename, so `"{}{}.rpy"should be"/{}_{}.rpy"` on both lines. At least, that did it for me. I am not really a programmer fyi. Your config.ini paths should also not have quotes.

There were numerous other issues that I had to address. Particularly with variables. I have two other scripts that I run after this one, but now have a pipeline that generally works. If I can get around to forking/posting it on here soon I will.

yuniyhimik commented 10 months ago

Should be part of the filename, so `"{}{}.rpy"should be"/{}_{}.rpy"` on both lines. At least, that did it for me. I am not really a programmer fyi. Your config.ini paths should also not have quotes.

There were numerous other issues that I had to address. Particularly with variables. I have two other scripts that I run after this one, but now have a pipeline that generally works. If I can get around to forking/posting it on here soon I will.

That would be awesome and much appreciated) I have just started Python tutorials, so will take me a long time to get to something working. And you have that already)

yuniyhimik commented 10 months ago

@SageGC just don't disappear, buddy) You are my hope

SageGC commented 10 months ago

Gonna need a bit more time. I tried recreating the whole process in a vacuum but ran into new problems. Or, more so, old problems I thought I solved have reappeared. I don't want to waste anyone's time with new headaches so I will fork only once I get the whole package working and the instructions are clear.

yuniyhimik commented 10 months ago

Gonna need a bit more time. I tried recreating the whole process in a vacuum but ran into new problems. Or, more so, old problems I thought I solved have reappeared. I don't want to waste anyone's time with new headaches so I will fork only once I get the whole package working and the instructions are clear.

@SageGC - How is it going, man? Got some good news for us?)