Scratch

Did you avoid compressing images? High-quality images can disrupt project speed. What player are you talking about? The Java Player? It's much less efficient than the Flash Player and that dying-before-playing part is probably because:

1. it's accidentally set to 0 somewhere;
2. it's not resetting when the green flag is clicked, or, more likely;
3. the Java Player is not efficient enough to maintain variables' proper value.

Are you using Java or Flash? If it's Flash, you may need to make it wait before the sensing is done. There was a bug in that player: Some color combinations used in [color = #0494dc] <color !! is touching !!?>[/color] don't work. Are you using the current version? On the other hand, the Java player is not efficient enough to execute it correctly. That's what I think is the problem with the online players.

14darkcats wrote:

3sal2 wrote:

Did you avoid compressing images? High-quality images can disrupt project speed. What player are you talking about? The Java Player? It's much less efficient than the Flash Player and that dying-before-playing part is probably because:

1. it's accidentally set to 0 somewhere;
2. it's not resetting when the green flag is clicked, or, more likely;
3. the Java Player is not efficient enough to maintain variables' proper value.

by player i meant character, user, call it whatever. I don't think the image is compressed. And what I'm saying is that the game will run fine on the program, but not here on the site. And the "player" is supposed to fall from the middle of the screen, I did that on purpose.

I knew that this was online, due to the context of the post you started this topic with. Which player do you use? What's the version? From the title context, I'm assuming the Java player, which is slower than Scratch 1.4.