Torque 2D v 1.7.5 Scroller sprite bug - image/scroller is invisible or greatly increased during Run game test compared to what You see when designing the level - RESOLVED

#1 I have also noticed the problems with scroller objects. It seems to be that the sourceRect of the object gets modified by the editor sometimes. By opening the level file and changing the sourceRect for the object to
sourceRect = "0 0 0 0";
the problem goes away.

A real fix for this is needed, since it's quite bothersome to have to go and correct the sourceRect every now and then.

#2 I am using single files for scrolling clouds, and still I get the same error now and then. *sighs* It looked promising, but right now it seems this software is really bugridden, I just lost an entire scene after saving it and reloading Torque 2D + the scene I had just saved, had to build everything from scratch.

#3 I would really love to know if all these problems with the software is only win OS related or if it happens on both mac OS and win OS. I've been struggling to rig a scene now for hours, finally throwing in the towel. I'm doing an uninstall and reinstall of the software, shouldn't need to do it but I can't figure out what's wrong since I haven't modified any of the files.

#4 I also use single files, but it seems to be the sourceRect bug that causes the error anyway. Open the levelfile.t2d in a texteditor and located the scroller object. It should look something like this...
new t2dScroller() {
imageMap = "rollingFloorPart1ImageMap";
repeatX = "5";
scrollX = "2";
scrollPositionX = "0.391623";
useSourceRect = "0";
sourceRect = "0 0 0 0";
canSaveDynamicFields = "1";
Position = "1.809 7.408";
size = "46.497 8.246";
Layer = "7";
GraphGroup = "7";
mountID = "49";
};

Make sure that the sourceRect line reads
sourceRect = "0 0 0 0";
This is what solves the scroller problem for me, at least temporary until I modify the scroller object in TGB.

Another strange thing is that useSourceRect = "0"; doesn't seem to work properly, because if sourceRect is changed the object is affected regardless of whether useSourceRect = "0" or not.

#5 Changing the sourceRect doesn't seem to help this problem for me the temp fix doesn't last if you edit the scroller object and you have to redo it.

Could it be because it's on top of other layers or below other layers that it's causing this problem?

Is there going to be a fix to this problem

It's really annoying, I never had this problem in the previous versions.

#6 Hm.. I'm pretty sure there was a thread with a fix to this not so long ago, but I can't just find it now.

I've just edited that more than useless field out of the engine, and here is another similar hack. Both require pro license though. One non-pro workaround I can think of is a sprites with animated sourceRect instead of scrollers, if it is possible at all to update this field on the fly.

#7 Hi,

could this be related to these bugs :

http://www.garagegames.com/community/forums/viewthread/126360

if it is, then the nicely packaged .patch that is provided in this thread is very easy to apply/merge :)

#8 Ran into this thread today searching for this very issue... Once it was related to the source rects in my head, I figured I'd try to sort it out in script.

If you're feeling hacky, don't use source rects AT ALL, and don't want to mess with the source code, try this for a script fix:

look for t2dSceneWindow::loadLevel(%sceneWindow, %levelFile) in levelManagement.cs (not .ed.cs, mind you...)

I think it'll be in your game's "common" folder... mines all shifted around because I got rid of the common folder entirely, but it's in there somewhere.

toward the bottom of that function you'll see a loop going through the objects loaded in... Add the line shown below:

for (%i = 0; %i < %sceneObjectCount; %i++)
      {
         %sceneObject = getWord(%sceneObjectList, %i);
         %sceneObject.sourcerect = "0 0 0 0"; // WERE NOT USING THESE AND THIS FIXES THE SCROLLER BUG IN-GAME
         //if( %sceneObject.isMethod( "onLevelLoaded" ) )
            %sceneObject.onLevelLoaded(%scenegraph);

      }

I know not everyone is comfortable with such hackery, but then some folks aren't comfortable with editing the source, so I figured I'd throw this out there.

I did a test with a .t2d file that had the crazy "1.4013e-045 0 2.8026e-045 1.4013e-045" sourcerect and it IS broken without this line, and looks fine with it added.

I'm sure given how prevalent the sourcerect screwiness is, it'll be fixed in the next version via proper source changes -- but who knows when that'll be!

#9 I've been having this for a while now, really really annoying.
I hope the guys at GG can issue a minor update ASAP to fix these issues.

#10 logged as TGB-517

#11 Any updates guys?

#12 @Ameen
No update to give, Jon logged it so that we made sure that we had the full list of reported issues to build out the work for 1.7.6.

#13 Fixed in 1.7.6