Game Development Community

weird scrolling/movement glitch, please help!

by Jack Rothwell · in Torque Game Builder · 02/14/2009 (6:07 am) · 6 replies

hi.
whenever i use a scroller or i get the camera to scroll, every second or so it sort of just stops for a moment, then carries on, like a little jitter. its really annoying as torque is such a good product. i had the same problem with blitzmax until i changed the graphics "flip" command to "flip(1)", is there something similar im not doing in torque? ive tried both smoothing modes on my graphics and i get the same problem.
HEEELLLPPP!!!
thanks-
jack.x
NextNext Thread
PrevPrevious Thread
More from Torque Game Builder


Torque Owner Jack Rothwell
#1
02/14/2009 (6:54 am)
in fact, it seems as if my fps is really, really low, but the debug overlay says 300+.
is this behaviour normal when you're debugging a game?
jack.x

Torque Owner Jack Rothwell
#2
02/25/2009 (7:29 am)
please help...

Torque Owner Dustin Sims
#3
02/25/2009 (2:49 pm)
I also have issues with TGB being "jerky" alot even if FPS is high.

Sometimes having lots of echo statements in your scripts will impact performance it seems. I assume it's because it is continually writing directly to file "console.log" which is very slow..

Torque 3D Owner Gavin Beard
Byte Logic
#4
02/27/2009 (3:30 am)
when you move the camera are you setting its position directly or setting the velocity (x or y)? if you directly set the position it will appear to jump about, as i found out, but using %obj.setLinearVelocity() will produce a much smoother move.

Torque Owner Jack Rothwell
#5
02/27/2009 (5:34 am)
i dont think its that, i only have one object moving on the stage and the camera isnt even mounted to it.

Torque 3D Owner Gavin Beard
Byte Logic
#6
02/27/2009 (6:10 am)
point being, if you just set the position of the camera it will just jump from one spot to another, which will not work out the inbetween frames resulting in a jerky, instance movemonet, mounting the camera to another object and setting the linear velocity will work out inbetween frames, and rendering those each update until velocity is set back to 0 resulting in a much smoother movement. I had exact same problem some time ago as this was only resolve i could find, so worth trying?