Circular Movement Limitations

[Brandon]

I'm working on a scrolling game that scrolls from bottom to top infinitely. Since I am trying to create the effect of a bottomless pit, the player starts at a Y of 100000. I have another object which requires circular motion to travel around the player and I tried to set the center Y to 100000 in the movement properties but it immediately sets it to 16000. Setting the center Y in the event editor doesn't seem to work either. The difference is that if I set it in the event editor it seems to center around a Y of about 32500 even if I set it to 100000. Anyone have any ideas?

---EDIT---
Actually, depending on what I change around it either centers around 32500 or -32500. I purposely unchecked Destroy object if too far from frame to see where the object was actually going instead of being immediately destroyed.

[Dynasoft]

MMF still uses 16-bit coordinates, ~32000 is the highest you'll get.

The easiest way to do a bottomless pit is to have the player continuously wrap around the same section of level:
(say your background image is 480 high, put it 3x vertically and do
Player.Y > 480x2
- Set Player.Y to Player.Y-480

Then a normal "Always centre display on player"

[Brandon]

I'm actually having no trouble with the player, I have all that set up with a virtual frame height of -1 and setting the player's coordinates to 1000000. That part works fine. What I am having trouble with is an object to circle around the player, and using the built-in movement circular motion isn't working.

[Dynasoft]

If you retrieve the player's coordinates in to a counter, what do you get?

If MMF2 HAS been updated to work with >16bit coordinates, then the fault is with the movement. If not, then your player isn't really at 1000000 :P.

[Benicle]

You could use the circular movement formula? (Though this seems to be an issue with interger limits though it might not work still)

Always: Add 3 to counter // This is rotating speed
Always Set X Object To: X("Player")-#radius#*Sin(Counter Value)
Always Set Y Object To: Y("Player")-#radius#*Cos(Counter Value)

So unless that works, it's number limits fault :P.

[Brandon]

If you retrieve the player's coordinates in to a counter, what do you get?

If MMF2 HAS been updated to work with >16bit coordinates, then the fault is with the movement. If not, then your player isn't really at 1000000 :P.

My object is indeed at 100000, that is not the problem. I tried Benicle's method, but I think he wrote something wrong, because it spirals off the screen using those equations.

[Benicle]

Bah... I'll make an example then shall I? I probably did do something wrong :P.

EDIT: here it is: http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=60353#Post60353