screen wrap and accelerometer

Games
#1

when first using a d-pad to move the game character everything looks good when it hits the borders of the screen (then border of screen +/- 1 pixel).
when using accelerometer to do so, there is a strong jitter I guess corresponding to maybe more than 20 pixels.

What is a good way to avoid that/make it look smooth, i.e, character rests at screen border until moved to other position?

Currently I cannot set the accelerometer readout frequency since the respective system call gives an error.
(http://developer.anscamobile.com/forum/2012/03/01/systemsetaccelerometerinterval-gives-error)

But I guess there should be some sort of time delay until new data are read for position update? Not sure. It actually looks much worse in simulator (ultimote) than it does on device. But are there any known solutions? [import]uid: 109677 topic_id: 22725 reply_id: 322725[/import]

#2

What version of Corona are you using? (Would like to see if I can reproduce the error.) [import]uid: 52491 topic_id: 22725 reply_id: 90889[/import]

#3

Hi, the about dialog says

Version 2012.755 (2012.12.8)

(Maybe I am doing something wrong, I just put this line in the beginning section of the .lua file that contains the gameplay were I also have the listener for accelerometer at some ppint. As soon as I comment the line out, accelerometer works and there is no error.) [import]uid: 109677 topic_id: 22725 reply_id: 90922[/import]

#4

Do you get the error is in build 704? Please let me know and will look into it. I haven’t used that API in a long while but believe at the start of code should be fine. [import]uid: 52491 topic_id: 22725 reply_id: 91049[/import]

#5

Initially I had 704 and then downloaded the newest release at that time and both would give this error, which now is gone!

I just tested again and there is no error. In the meantime, I actually just worked with unrelated things (bitmaps) and I am really unsure why it now would work.

I also had an issue the same day with the config where it would not compile with build settings examples from the ANSCA samples and give an error that } was expected (it was of course there). I sometimes wonder if there are any issues with encoding format when using copy/paste in the text editor I am using.

Sorry to bring that up in the first place.

I actually now use the gyroscope as I like that better for the gameplay and there is no jitter with the gyroscope data either.
Are there any known facts what users like better, d-pad, accelerometer or gyroscope? [import]uid: 109677 topic_id: 22725 reply_id: 91058[/import]

#6

Copy and paste CAN be a problem, yes. I have seen this with users before - hidden characters, etc. (I have worked with someone over Skype where this issue appeared recently.)

RE users - I have had several say they prefer a d-pad, although others experience/feedback may vary. (Personally I like the d-pad, too.) [import]uid: 52491 topic_id: 22725 reply_id: 91067[/import]

#7

thanks for your input on the gameplay.

I now saw what the “problem” is with this system. - error, it comes with gyroscope as well:
It is when having the device connected with ultimote that this error comes up. So when testing with ultimote, one just has to comment it out and everything is fine. (will check their documentation at some point, maybe they even mention it there…) [import]uid: 109677 topic_id: 22725 reply_id: 91073[/import]