Scratch

bump. Please help, I can't figure out how to stop this from happening.

Wes64 wrote:

No you cant fix it, thats not a glitch either. It just happens when a script is super long, the way to avoid it to split the script up when you edit it and only put the pieces together at the end.

It is a bug.
I'm not able to find it, but try searching for a thread by nXIII about this. It has an official answer from Lightnin.

I'd recommend just using repeats there instead of doing that, if possible. That way it would take up less space. The cut-off in 1.x Scratch is unavoidable, though.

Wes64 wrote:

veggieman001 wrote:

I'd recommend just using repeats there instead of doing that, if possible. That way it would take up less space. The cut-off in 1.x Scratch is unavoidable, though.

Actually his project is a 3D render, so it is necessary to use single-framing instead of repeats. (if you want it to rotate smoothly)

Ah, okay. Apologies for my ignorance. ^^

777w wrote:

Wes64 wrote:

veggieman001 wrote:

I'd recommend just using repeats there instead of doing that, if possible. That way it would take up less space. The cut-off in 1.x Scratch is unavoidable, though.

Actually his project is a 3D render, so it is necessary to use single-framing instead of repeats. (if you want it to rotate smoothly)

which is why that idea about disabling delay in repeats should be implemented 

yes, that's the problem. The 3D rendering is such a long script, and I need a way to shorten it and make it more efficient, or I need a way around the bug.

zubblewu wrote:

They need a check for "atomic" like in byob.

I don't use BYOB.

I thought of a nice (but sprite consuming) workaround for 2.0. You just divide it into nice sized portions, and make them into procedures. Then, to avoid lag stick them in seperate sprites. It should only have to be a few blocks then.

zubblewu wrote:

I thought of a nice (but sprite consuming) workaround for 2.0. You just divide it into nice sized portions, and make them into procedures. Then, to avoid lag stick them in seperate sprites. It should only have to be a few blocks then.

that's a good idea, but I'd need 2.0.

zubblewu wrote:

I have 2.0, but it wouldn't matter if you did. No saving or anything. But that should work when 2.0 fully comes out 

...you have 2.0? WHERE!? >

AgentRoop wrote:

zubblewu wrote:

I have 2.0, but it wouldn't matter if you did. No saving or anything. But that should work when 2.0 fully comes out 

...you have 2.0? WHERE!? >

I have it too put paddle told us not to acces it.

2.0's saving function is working (I have access but use it very rarely.)

Another thing you might want to know is that, as mentioned before, procedures will make this possible; 3D rendering scripts will work much better. I can verify by sending a video, though.

You might want to edit the scripts as separate pieces and then join them together, bottom to top, in your forever loop. The cutting only happens if a single script is too long, and it only happens for that piece, so try breaking it into smaller pieces and assembling it later. 

BirdByte wrote:

2.0's saving function is working (I have access but use it very rarely.)

Another thing you might want to know is that, as mentioned before, procedures will make this possible; 3D rendering scripts will work much better. I can verify by sending a video, though.

You might want to edit the scripts as separate pieces and then join them together, bottom to top, in your forever loop. The cutting only happens if a single script is too long, and it only happens for that piece, so try breaking it into smaller pieces and assembling it later. 

thank you.