I have a question about a possible bug

[Daggett]

I have this one bg image in my game that shows up in one place, but the next time I type out "scene bg back pt1" it comes up as an "Undefined Image". I have it with the rest of the images, IE, image bg back pt1 = "back pt1.png". And it's in my "Game Directory" too. Has this happened to anyone else?

I am also using this* code before it and it even starts fading into the image and then stops with the "Undefined Image" screen.

If anyone could help me, it would be greatly appreciated.

*
init:
$ dissolve = Dissolve(0.5)

with None
scene bg black
with dissolve

init:
$ dissolve = Dissolve(0.5)

with None
scene bg back pt1
with dissolve

[Daggett]

It's been a while... This post is just to get this topic back on page 1. Because I would really like to know what is happening.

[vociferocity]

can you post your code? like, your init block and the label where everything's going wrong, preferably in a [ code ][ / code ] block, so that I can have a good look at what's happening?

[Daggett]

can you post your code? like, your init block and the label where everything's going wrong, preferably in a [ code ][ / code ] block, so that I can have a good look at what's happening?

Sure thing. This is how the par that is acting weird looks exactly, minus the "[ code ][ / code ]" things. The entire label is 547 words. Do you want that too?


[ code ]
y "Thank you."

init:
$ dissolve = Dissolve(0.5)

with None
scene bg back pt1
with dissolve

y "Guess who's back."

scene bg back pt5

ukc "What are you doing here?"
[ / code ]

[sciencewarrior]

Remove the spaces inside the "[ code ][ / code ]" tags before posting. The purpose is having a block like this

Code: Select all

where
  we
    can see your
  code
identation

[Daggett]

Remove the spaces inside the "[ code ][ / code ]" tags before posting. The purpose is having a block like this

Code: Select all

where
  we
    can see your
  code
identation

Sorry about that. I'm new to forums. This is how it looks. I have been using this for all the indentation on this label. Just flat on the side of the script. I thought I'd have to go back over it, but it worked. The text and pictures before show up and everything. All that is happening is the picture doesn't show up.

Code: Select all

y "Thank you."

init:
$ dissolve = Dissolve(0.5)

with None
scene bg back pt1
with dissolve

y "Guess who's back."

scene bg back pt5

ukc "What are you doing here?"

[backansi]

Code: Select all

init:
    $ dissolve = Dissolve(0.5)

label start:
    # ....
    y "Thank you."

    scene bg back pt1
    with dissolve

    y "Guess who's back."

    scene bg back pt5

    ukc "What are you doing here?"

If you defined something in a init block, you don't need to insert the init block in the middle of label block to use them in your game.

[Daggett]

Code: Select all

init:
    $ dissolve = Dissolve(0.5)

label start:
    # ....
    y "Thank you."

    scene bg back pt1
    with dissolve

    y "Guess who's back."

    scene bg back pt5

    ukc "What are you doing here?"

If you defined something in a init block, you don't need to insert the init block in the middle of label block to use them in your game.

Why is that? The first game I made I didn't do that. And what is the " # ...." for? Will that fix the image malfunction?
Should I also put the init before the label?

[vociferocity]

a "#" is a comment marking, in ren'py. you use them to comment out a line - if a line is commented out, it won't be read as a line of programming. it can either be at the start of a line (to comment out the whole line), or during it, to comment out whatever is after it so you can comment your code with it, eg:

Code: Select all

# this is a comment
# ren'py won't think these lines are part of the script, they're just for me to look at! it's good to comment stuff
# so you can look at it later and remember exactly what everything means

#kitchen scene: this is the dramatic finale!!
label kitchen:
    scene whatever
    show loveinterest happy

    bf "I...I love you" #ugh! note to self, come up with better dialogue!!

so the "#..." in the code backansi posted is just a "...", like, "the rest of your script goes here", basically. and yeah, your init should go above the label. you could even put your initialisation stuff in another file, to keep everything all neat

[Daggett]

a "#" is a comment marking, in ren'py. you use them to comment out a line - if a line is commented out, it won't be read as a line of programming. it can either be at the start of a line (to comment out the whole line), or during it, to comment out whatever is after it so you can comment your code with it, eg:

Code: Select all

# this is a comment
# ren'py won't think these lines are part of the script, they're just for me to look at! it's good to comment stuff
# so you can look at it later and remember exactly what everything means

#kitchen scene: this is the dramatic finale!!
label kitchen:
    scene whatever
    show loveinterest happy

    bf "I...I love you" #ugh! note to self, come up with better dialogue!!

so the "#..." in the code backansi posted is just a "...", like, "the rest of your script goes here", basically. and yeah, your init should go above the label. you could even put your initialisation stuff in another file, to keep everything all neat

I like to have the pov make the choice then have the fade to show that the scene is changing into the future and just next scene, but as a time lapse. Won't putting it before the label fade before the choice is made? And what about that image issue? The fade works but after the fade thing finishes, it won't show up. It works in a previous part too! And I can't move on my checking or writing until I find out what's going on.

Thank you for all your help, everybody.

[Daggett]

I got it. I just used a similar background image. The other times in the code that scene bg worked, so I don't know. Thanks for all the suggestion.