This is one that's been bugging me for a LONG time, and you can REALLY notice it in pen projects, and even some normal ones. Outside of presentation mode, but still online rendering is done before all of the code is executed, resulting in the user seeing an unfinished frame in pen projects and sensors etc in non-pen projects. Also, velocity movement looks stair-steppy because of this and because of the increasing number of games that use the pen this is becoming more of a problem.
I think you should just port the rendering system from Presentation mode into normal mode, as that seems to work fine in comparison (but for some reason works at half frame-rate)
Offline
*reads title* Welcome to Scratch!
Wait, so this happens online, and in normal mode, but not presentation mode. Is that correct?
Offline
Lucario621 wrote:
*reads title* Welcome to Scratch!
![]()
NICE.
Last edited by ThePCKid (2010-01-17 10:38:07)
Offline
Lucario621 wrote:
*reads title* Welcome to Scratch!
![]()
Wait, so this happens online, and in normal mode, but not presentation mode. Is that correct?
This does not happen online. It's what makes One-S One-S projects flicker in normal mode.
Offline
RHY3756547 wrote:
Lucario621 wrote:
*reads title* Welcome to Scratch!
![]()
Wait, so this happens online, and in normal mode, but not presentation mode. Is that correct?This does not happen online. It's what makes One-S One-S projects flicker in normal mode.
Oh ok.
Well who cares about normal mode!
Offline
With The-Whiz's 10-point mesh, I thought it so brilliant because I was viewing it online, where there isn't the 'flicker'. But when I downloaded it I saw my mistake.
Offline
RHY3756547 wrote:
This does not happen online.
It happens to me...
Offline
Well i m toooo technical so here are my technical words
thecauseofproblem wrote:
Um RHY the thing u r seeing is very certain to happen .The code of both the presentationa nd normal renderer are the same but in the normal mode thier are scratch IDE display functions constantly running which slows scratch down so it dosent matter with programming.So i dont think it can be reduced untill They remove the programming which slows down scratch to make it equispeed on all computer systems(which it never does).
well now the solution RENDER in end well it will make programming even tougher do all calculations first then render like
set x 1to
set y1 to
set x3to
set x2 to
set y2 to
set y3 to
then for rendering
goto x1 y1
pendown
goto x2y2
goto x3 y3
penup.
AND OMG UR DONE WITH FAST PROCESSING BUT * SLOW PROGRAMMING
Jonathanpb wrote:
RHY3756547 wrote:
This does not happen online.
It happens to me...
![]()
well the problem is due to scratchs speed difference it doesnt happens ol to me either and on my friends i7 extreme the half rendered image is shown for very less time literally 1/100th time from on my CPU but still HUMAN Brain can get it
Last edited by fanofcena (2010-01-18 05:43:11)
Offline
fanofcena wrote:
Well i m toooo technical so here are my technical words
thecauseofproblem wrote:
Um RHY the thing u r seeing is very certain to happen .The code of both the presentationa nd normal renderer are the same but in the normal mode thier are scratch IDE display functions constantly running which slows scratch down so it dosent matter with programming.So i dont think it can be reduced untill They remove the programming which slows down scratch to make it equispeed on all computer systems(which it never does).
well now the solution RENDER in end well it will make programming even tougher do all calculations first then render like
set x 1to
set y1 to
set x3to
set x2 to
set y2 to
set y3 to
then for rendering
goto x1 y1
pendown
goto x2y2
goto x3 y3
penup.
AND OMG UR DONE WITH FAST PROCESSING BUT * SLOW PROGRAMMINGJonathanpb wrote:
RHY3756547 wrote:
This does not happen online.
It happens to me...
![]()
well the problem is due to scratchs speed difference it doesnt happens ol to me either and on my friends i7 extreme the half rendered image is shown for very less time literally 1/100th time from on my CPU but still HUMAN Brain can get it
Noooooooooooooooooooooooooooooooooooooooooooo
I think the problem is that the renderer is out of sync with the debug application executer and instead runs synced with the code editor. I think it should unsync with the code editor when the game is running.
Also, Online NOTHING flickers because it doesn't have this problem. Even if you have a slow CPU it won't flicker online.
You can see this in LINE Tennis and when you download my Perfect platformer base (the sensing code makes mario jitter about)
Offline