Ah! Makes sense now ! The image's resolution was set at 95.961 ppi, so came in at a weird size (height 83.2847) hence the 35.5 in my equation, but yes, if you resize it to 110 pixels tall (it's actually 111) then the number would be nearer 55 like you say (minus a little for the white dot being not quite at the end).
Sorry Bruno that I can't seem to communicate in a way that is helpful to you. I do know what you want and I do know where things went wrong in your file. But I can't seem to communicate to you how to fix it.
I am not sure how to help much more here. So.. @Socks, I'll back off so that you can explain the relationships between the numbers within the behaviors (in your demo).
@Socks -- here is a picture of situation. 1) He changed graphics. So now the actor has a different actor height. But he didn't modify the offset in the expression. 2) He modified the rotate speed. But he didn't make a corresponding change in the game.time multiplier (um... speed). 3) He made it run counter-clockwise. But he didn't make a corresponding change in the game.time multiplier. (It needs to be negative to make it counter-clockwise.)
Perhaps you will have better luck in explaining it!
1) He changed graphics. So now the actor has a different actor height. But he didn't modify the offset in the expression.
Ah, I see ! Yes, he needs to adjust the offset ! I've not got access to his new image so can't really help out here.
2) He modified the rotate speed. But he didn't make a corresponding change in the game.time multiplier (um... speed).
Yep, he's going to need to keep them the same.
3) He made it run counter-clockwise. But he didn't make a corresponding change in the game.time multiplier. (It needs to be negative to make it counter-clockwise.)
. . . or just change 'sin' to 'cos' and 'cos' to 'sin'.
I can see how it might be tempting (to the uninitiated) to think changing rotation speed in rotate would be how to control the speed of the circular path.
Someone like GShelper should post a simple sin / cos tutorial, these questions come up a fair bit.
Perhaps you will have better luck in explaining it!
I'm not so sure, it might be easier to just do it for him, but past efforts have not worked, it would be useful to even get a 'yes I opened that project and it worked' so you get a few clues, but the language barrier is not helping and the more this thread goes on the more I'm not sure what's going on but your explanation helped somewhat.
Comments
Ah! Makes sense now ! The image's resolution was set at 95.961 ppi, so came in at a weird size (height 83.2847) hence the 35.5 in my equation, but yes, if you resize it to 110 pixels tall (it's actually 111) then the number would be nearer 55 like you say (minus a little for the white dot being not quite at the end).
I am not sure how to help much more here. So.. @Socks, I'll back off so that you can explain the relationships between the numbers within the behaviors (in your demo).
Now, @Socks, do you explain for me the code? and share??
It is on the first page of this thread, have a look at the demo I made for you.
Or just use:
Constrain X to 36.5*sin( game.Time *150)+200
Constrain Y to 36.5*cos( game.Time *150)+150
Rotate / clockwise /speed 150
@socks you are being very unclear in your video - could you bend it in NEON aswell
1) He changed graphics. So now the actor has a different actor height. But he didn't modify the offset in the expression.
2) He modified the rotate speed. But he didn't make a corresponding change in the game.time multiplier (um... speed).
3) He made it run counter-clockwise. But he didn't make a corresponding change in the game.time multiplier. (It needs to be negative to make it counter-clockwise.)
Perhaps you will have better luck in explaining it!
I can see how it might be tempting (to the uninitiated) to think changing rotation speed in rotate would be how to control the speed of the circular path.
Someone like GShelper should post a simple sin / cos tutorial, these questions come up a fair bit. I'm not so sure, it might be easier to just do it for him, but past efforts have not worked, it would be useful to even get a 'yes I opened that project and it worked' so you get a few clues, but the language barrier is not helping and the more this thread goes on the more I'm not sure what's going on
Can you post your latest / new image ?
I don't know what an ODT file is, and when I click on the link I just get a loading wheel that never stops.
A JPEG or a BMP or a PSD or any common image file format would have done the trick, but let's be honest this is all going nowhere slowly !
I give up ! I'll let someone else have a go. Best of luck.
this is o correct
https://www.box.com/s/1l18a81la5te323dlf4o