I followed a YouTube tutorial made by @griffpatch. But, something's not right. Will you please help me find the bug and fix it? https://scratch.mit.edu/projects/617609711

You have the script designed to delete when it touches the level maybe change to edge of screen? It will help to know what your objective is.

Gilstylin wrote:

You have the script designed to delete when it touches the level maybe change to edge of screen? It will help to know what your objective is.

Read the full description of the project.

EDawg2011 wrote:

Gilstylin wrote:

You have the script designed to delete when it touches the level maybe change to edge of screen? It will help to know what your objective is.

Read the full description of the project.

The project says

1. When a ball touches the level, it disappears for some reason. - That is not an error the code deletes the clone when it touches.

2. if the ball doesn't disappear when it touches the wall, the project will lag horribly. - change all

<touching [ Level] ?>

to

<touching [ edge] ?>

Gilstylin wrote:

EDawg2011 wrote:

Gilstylin wrote:

You have the script designed to delete when it touches the level maybe change to edge of screen? It will help to know what your objective is.

Read the full description of the project.

The project says

1. When a ball touches the level, it disappears for some reason. - That is not an error the code deletes the clone when it touches.

2. if the ball doesn't disappear when it touches the wall, the project will lag horribly. - change all

<touching [ Level] ?>

to

<touching [ edge] ?>

I and @griffpatch, I'm pretty sure, put those touching Level blocks to check for collisions.

i might suggest just rebuilding everything following the tutorial - i'm very sorry but i'm uncertain if many people have the time to sift through a project with a tutorial

by the way the script that seems to be actually deleting the clones is the dir > 720 script that's there to prevent infinite loops that lag out the run without screen refresh scripts

The script says that if the “Ball” Touches Level,It disapears, thats not correct.

Read the comment twice up higher how to fix it!

I mean twice up lol

Gilstylin wrote:

EDawg2011 wrote:

Gilstylin wrote:

You have the script designed to delete when it touches the level maybe change to edge of screen? It will help to know what your objective is.

Read the full description of the project.

The project says

1. When a ball touches the level, it disappears for some reason. - That is not an error the code deletes the clone when it touches.

2. if the ball doesn't disappear when it touches the wall, the project will lag horribly. - change all

<touching [ Level] ?>

to

<touching [ edge] ?>

I and @griffpatch, I'm pretty sure, put those touching Level blocks to check for collisions.

cIoudyness wrote:

i might suggest just rebuilding everything following the tutorial - i'm very sorry but i'm uncertain if many people have the time to sift through a project with a tutorial

by the way the script that seems to be actually deleting the clones is the dir > 720 script that's there to prevent infinite loops that lag out the run without screen refresh scripts

Good idea. But, the fact that I have to sit through the tutorial again…

cIoudyness wrote:

i might suggest just rebuilding everything following the tutorial - i'm very sorry but i'm uncertain if many people have the time to sift through a project with a tutorial

by the way the script that seems to be actually deleting the clones is the dir > 720 script that's there to prevent infinite loops that lag out the run without screen refresh scripts

(Read The Post Above First) Also, without that script that deletes the clones, the project will lag horribly when the ball collides with a wall.

the normal costume is not in the right enough, move it to the right until it work
yeah that's it, you're expecting some crazy math thing, but it's just basic costume stuff, no need to edit anything except the normal costume

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

ventoaurum wrote:

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

It's there so that the project does not lag when a ball touches a wall.

EDawg2011 wrote:

ventoaurum wrote:

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

It's there so that the project does not lag when a ball touches a wall.

See the tutorial I followed to make that project. https://www.youtube.com/watch?v=Ge1DbXkyMKo Please watch the full video.

EDawg2011 wrote:

EDawg2011 wrote:

ventoaurum wrote:

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

It's there so that the project does not lag when a ball touches a wall.

See the tutorial I followed to make that project. https://www.youtube.com/watch?v=Ge1DbXkyMKo Please watch the full video.

Or, watch the video from the part where his project lags.

so, did my method work? the “move the normal costume a bit right” method i mean

ventoaurum wrote:

so, did my method work? the “move the normal costume a bit right” method i mean

I don't think moving it just 1-pixel works, but, I think I tried a lot larger amount to the right and it worked. https://scratch.mit.edu/projects/617609711/

EDawg2011 wrote:

ventoaurum wrote:

so, did my method work? the “move the normal costume a bit right” method i mean

I don't think moving it just 1-pixel works, but, I think I tried a lot larger amount to the right and it worked. https://scratch.mit.edu/projects/617609711/

you're welcome

ventoaurum wrote:

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

by the way you definitely shouldn't delete this block

it's there to prevent an infinite loop within a run without screen refresh block which would be terrible

cIoudyness wrote:

ventoaurum wrote:

also just to be safe remove the

if <(dir) > [720]> then
delete this clone
end

from the rotate custom block definition
if you dont, there is this specific angle of plane(ground/wall) and aim that can delete the ball

by the way you definitely shouldn't delete this block

it's there to prevent an infinite loop within a run without screen refresh block which would be terrible

cool