It's very glitchy, if you see what I mean- upload it in here (new project) and then

a) hover your mouse over the outside, what should be there isn't
b) add something else and now what should be there is there, but-
c) try some other things i haven't found yet

it appears to have a lot of glitches in it and i was wondering why.

Oops nevermind hover your mouse over the rays-

Yeah so if you move it it goes from square-cut to normal, and it's just so confusing… if you change anything in the backdrop it also does that but in the editor.

You're right, that is strange. I counted 72 rays, all of which escape the stage boundary; perhaps the number of objects has something to do with it?

Up until sometime last year, the paint editor didn't show anything outside of the 480x360 stage boundary. This glitch could be a side effect of the update; the paint editor wasn't originally designed with these boundaries in mind.

Scratch137 wrote:

You're right, that is strange. I counted 72 rays, all of which escape the stage boundary; perhaps the number of objects has something to do with it?

Up until sometime last year, the paint editor didn't show anything outside of the 480x360 stage boundary. This glitch could be a side effect of the update; the paint editor wasn't originally designed with these boundaries in mind.

Hmm… perhaps, I do remember getting annoyed when the paint editor was no longer lined up, but I don't remember if you could zoom out (I think you could) and I also don't remember if things went outside the boundaries after that.

My guess is the backdrop might have had some extra properties that Scratch's paint editor doesn't support, and maybe for that reason the rays extend when you update the costume, kind of like how some custom SVGs don't render until you add something to the costume.

D-ScratchNinja wrote:

My guess is the backdrop might have had some extra properties that Scratch's paint editor doesn't support, and maybe for that reason the rays extend when you update the costume, kind of like how some custom SVGs don't render until you add something to the costume.

But- the doesn't make sense if it's compatible with the vector editor, I noticed that some backdrops that used to be in bitmap are now in vector (the circles backdrop is one) so wouldn't the have just traced or used a program to draw it into vector in order to do that?

Please share a screenshot.

D-ScratchNinja wrote:

My guess is the backdrop might have had some extra properties that Scratch's paint editor doesn't support, and maybe for that reason the rays extend when you update the costume, kind of like how some custom SVGs don't render until you add something to the costume.

This probably isn't the case. I played around with the backdrop a bit, and the edges continued glitching out. If it was caused by the SVG format, it would've only happened once.

Xolay wrote:

Please share a screenshot.

The glitch:


What it's supposed to look like:

I just noticed that there's an invisible rectangle that fills the entire 480x360 stage area.



I don't know why it's there, but deleting it seemed to stop the glitch completely.

I exported it and looked at the SVG.

So this wasn't made in the paint editor.

O_O what's this?
It's a clipping path!
For some reason the SVG has a clip path that is a rectangle that is 480.24x360px. The paint editor doesn't export clip paths since the SVG space isn't supposed to be limited there.
It's probably an Adobe Illustrator SVG Export Plugin thing…
And the path for the clipping path is a <rect>. That may explain the weird rectangle Scratch137 found: The paint editor doesn't recognize the <defs> tag (it was never designed to export with it so why bother supporting it?) so it treats it like any other invalid element and it displays the stuff inside it, in this case a rectangle with no other display attributes like color so it's transparent..

Can replicate!

Check out what happens when you convert it to Bitmap, then back to Vector.

NikolaProGamer2010 wrote:

Check out what happens when you convert it to Bitmap, then back to Vector.

It crashes, I tested it.

-Da_Bean- wrote:

NikolaProGamer2010 wrote:

Check out what happens when you convert it to Bitmap, then back to Vector.

It crashes, I tested it.

I did find a way to prevent that crash
here's how

• first, convert it to bitmap

• then, copy the whole costume into another (vector) empty costume

• delete the bitmapped one

• and you're done!

When did it start doing this??
it does only in 3.0 and for some reason icicle's solution works