forum

[Archived] Storyboard glitch? "MX" and "MY" work improperly...

posted
Total Posts
8
Topic Starter
Gomo Psivarh
A test storyboard:
Sprite,Foreground,Centre,"test.png",0,150
M,0,10000,11000,100,150,200,150
M,0,11000,13000,200,150,300,150
F,0,15000,20000,1,0

It works well, the picture will move from (100,150) to (300,150) then stay at (300,150) until 0:20:000.


If I write it as
Sprite,Foreground,Centre,"test.png",0,150
MX,0,10000,11000,100,200
MX,0,11000,13000,200,300
F,0,15000,20000,1,0

The picture will move from (100,150) to (300,150), but it will stay at (200,150) from 0:13:000 to 0:20:000.

"MY" has the problem too...

m980's opinion
It seems that after all MX/MY transformations are done (ie. there are none left), the X/Y position (depending on whether MX/MY is used) is immediately shifted to the end value of the very first MX/MY transformation.
ie...
_MX,0,10000,11000,100,200
_MX,0,11500,13000,200,300
_MX,0,13500,15000,300,400
Would make the image go back to X value 200 after the last MX is done. Or, if the first line was not there, it would go to X value 300.

Also...

Sprite,Foreground,TopRight,"test.png",100,150
_MX,0,10000,11000,100,200
_MX,0,11500,13000,200,300
_MX,0,13500,15000,300,400
_MX,0,15500,17000,400,500
_MX,0,17500,19000,500,600
_MX,0,19500,21000,600,500

If I had that for my code, inbetween each of the transformations (there is a break of 500ms), the image would shift to the X/Y end value of the second last line. In this case, it would move to x value 600. If that last line wasn't there, it would go to x value 500.
 
 
 
Lilac
If I write it as
Sprite,Foreground,Centre,"test.png",0,150
MX,0,10000,11000,100,200
MX,0,11000,13000,200,300
F,0,15000,20000,1,0

The picture will move from (100,150) to (300,150), but it will stay at (200,150) from 0:13:000 to 0:20:000.

"MY" has the problem too...
Why does this occur? :(
I'm going to have a short stab and say it's because of the first line.
0,150

But I dunno.
m980
I think it's a bug. However, you really shouldn't need those two lines anyway.
_MX,1,10000,13000,100,300
That line alone achieves the same "slowing down" effect that I think you are looking for.

Anyway, MX and MY are relatively new transformations, so they're probably just a bit buggy. I'll mess around with it a bit.........

And after a bit of experimentation... it appears that there are bugs if you use more than one MX or more than one MY transformation
SPOILER
It seems that after all MX/MY transformations are done (ie. there are none left), the X/Y position (depending on whether MX/MY is used) is immediately shifted to the end value of the very first MX/MY transformation.
ie...
_MX,0,10000,11000,100,200
_MX,0,11500,13000,200,300
_MX,0,13500,15000,300,400
Would make the image go back to X value 200 after the last MX is done. Or, if the first line was not there, it would go to X value 300.

Also...

Sprite,Foreground,TopRight,"test.png",100,150
_MX,0,10000,11000,100,200
_MX,0,11500,13000,200,300
_MX,0,13500,15000,300,400
_MX,0,15500,17000,400,500
_MX,0,17500,19000,500,600
_MX,0,19500,21000,600,500

If I had that for my code, inbetween each of the transformations (there is a break of 500ms), the image would shift to the X/Y end value of the second last line. In this case, it would move to x value 600. If that last line wasn't there, it would go to x value 500.
But yeah. I guess for now you should just limit yourself to one MX/MY thing per object (until it's fixed). The stuff in the spoilerbox is mainly for the people who are going (or hopefully going) to fix this bug.




@Lilac, don't respond in topics about things you obviously have no idea about. The things that you mentioned are the coordinates of an image/object if there is no M transformation. (0,150) is not a part of the problem.
Topic Starter
Gomo Psivarh
bump

almost forget this topic :(
ziin
Luckily this is just a small bug which if you know about it has an easy fix.
Topic Starter
Gomo Psivarh
bump :(
Topic Starter
Gomo Psivarh
bump again :o
peppy
Should be fixed in the next public release.
Please sign in to reply.

New reply