Scratch

Any options for the moment? 

If it comes down to it I'll have to export a masked image of the level for collisions. It would take up more disk space and time - but would work.

Hmmm... I think this belongs in Advanced Topics, RHY3756547. 

If the great Scratch master (that's you, of course) can't think of a solution, how could I? 
I don't have a solution, sorry. 

Paddle2See wrote:

Jonathanpb wrote:

Hmmm... I think this belongs in Advanced Topics, RHY3756547. 

If the great Scratch master (that's you, of course) can't think of a solution, how could I? 
I don't have a solution, sorry. 

I think what RHY3756547 is saying is that it is a bug that it isn't faster.  It seems to make sense that it could be faster as the sprite doesn't actually have to be rendered - only the collision and color sensing still needs to be performed.   But I have no idea if that actually is how the code works.

Maybe this topic belongs in Suggestions since RHY3756547 may be recommending that such a mode be developed?

However, on second thought, let's try it in Advanced Topics as Jonathanpb suggests and see if anybody has any alternate techniques.  Maybe move it elsewhere later.

I got it by Paddle2see's post RHY as scratch is fast enough at presentation mode instead of using ghost 100% you can use show hide blocks
like
|forever
|||show
|||hide

Belive me its faster then Ghost and for very simple objects Mathematics is the best solution    .

What you could do, is make a a 2nd costume that's just a little black dot.

Though, it might be a bit of a pain, if your using a set of variables already to set the sprites costume to a certain amount...

hmmm....

fanofcena wrote:

Paddle2See wrote:

Jonathanpb wrote:

Hmmm... I think this belongs in Advanced Topics, RHY3756547. 

If the great Scratch master (that's you, of course) can't think of a solution, how could I? 
I don't have a solution, sorry. 

I think what RHY3756547 is saying is that it is a bug that it isn't faster.  It seems to make sense that it could be faster as the sprite doesn't actually have to be rendered - only the collision and color sensing still needs to be performed.   But I have no idea if that actually is how the code works.

Maybe this topic belongs in Suggestions since RHY3756547 may be recommending that such a mode be developed?

However, on second thought, let's try it in Advanced Topics as Jonathanpb suggests and see if anybody has any alternate techniques.  Maybe move it elsewhere later.

I got it by Paddle2see's post RHY as scratch is fast enough at presentation mode instead of using ghost 100% you can use show hide blocks
like
|forever
|||show
|||hide

Belive me its faster then Ghost and for very simple objects Mathematics is the best solution    .

That gets me a 1 frame delay. I don't want that.

adriangl wrote:

RHY3756547 wrote:

fanofcena wrote:

I got it by Paddle2see's post RHY as scratch is fast enough at presentation mode instead of using ghost 100% you can use show hide blocks
like
|forever
|||show
|||hide

Belive me its faster then Ghost and for very simple objects Mathematics is the best solution    .

That gets me a 1 frame delay. I don't want that.

1 frame? Really?

Yes. Didn't I just say that?

When I have things colide I don't want the user to see it stuck half way in it. If you do, that's fine by me.

Lucario621 wrote:

adriangl wrote:

RHY3756547 wrote:

That gets me a 1 frame delay. I don't want that.

1 frame? Really?

Yup. RHY spazzes out over every frame he loses in a scratch project.

I really hate you.

I've decided to lose the one frame on everything but the wall collision sprites.

Paddle2See wrote:

Jonathanpb wrote:

Hmmm... I think this belongs in Advanced Topics, RHY3756547. 

If the great Scratch master (that's you, of course) can't think of a solution, how could I? 
I don't have a solution, sorry. 

I think what RHY3756547 is saying is that it is a bug that it isn't faster.  It seems to make sense that it could be faster as the sprite doesn't actually have to be rendered - only the collision and color sensing still needs to be performed.   But I have no idea if that actually is how the code works.

Maybe this topic belongs in Suggestions since RHY3756547 may be recommending that such a mode be developed?

However, on second thought, let's try it in Advanced Topics as Jonathanpb suggests and see if anybody has any alternate techniques.  Maybe move it elsewhere later.

WOW. Paddle2See called Rhy3756547 by his real name. 

RHY3756547 wrote:

Lucario621 wrote:

adriangl wrote:

1 frame? Really?

Yup. RHY spazzes out over every frame he loses in a scratch project.

I really hate you.

I've decided to lose the one frame on everything but the wall collision sprites.

I think you just hurt Lucario621's feelings, considering he pretty much loves you.

RHY3756547 wrote:

Lucario621 wrote:

adriangl wrote:

1 frame? Really?

Yup. RHY spazzes out over every frame he loses in a scratch project.

I really hate you.

I've decided to lose the one frame on everything but the wall collision sprites.

*deeply offended*

jk 

RHY3756547 wrote:

Lucario621 wrote:

RHY3756547 wrote:

Lucario621 wrote:

Yup. RHY spazzes out over every frame he loses in a scratch project.

I really hate you.

I've decided to lose the one frame on everything but the wall collision sprites.

*deeply offended*

jk 

You are actually crying in a corner right now. 

Why are you deeply offended about losing one frame on everything but walls, anyway?

I'm not offended about that. I was (jokingly) offended about how you said "I hate you" 

If you only  need to test whether it is touching periodically, you can make a broadcast every time you need to, and have that show it, test whether it is touching, and then hide. If, however, you need to have a constant feedback, then ghost=100 is the best option.

All of that aside, what exactly does ghost effect do?
And if anyone wants to tell me what the motor functions in the stage are for then go ahead.