Just thought that, although there is a well known post already, this should probably be in the show stopper forum as it pretty much is for a lot of game ideas.
Original thread: https://developer.anscamobile.com/forum/2010/10/30/pivot-joints-and-apparent-elasticity
Issue entry #3264: http://developer.anscamobile.com/issues/5949
m [import]uid: 8271 topic_id: 6082 reply_id: 306082[/import]
Yeah, good luck horacebury. Although they did respond to my initial email about my piston joint problem, I sent them a code sample and have heard nothing back.
Did you see my post on the 60fps making joints better? Give that a shot. It certainly tightens up all the joints on my game, but read the post to see why most of us can’t use it.
I am honestly thinking about offering up a bounty to anyone on these forums that could help me. I will pay for help. Maybe ansca should offer direct support for additional fees, although with the price of corona some might suggest it should be included.
My problem is finding information. I’m not being lazy, I just can’t find any information to help me with my issues. I’ve read the complete Box2d manual and have even started learning flash so I can see why its not working in Corona but is working in flash. I’m also reading books on Lua, but that still doesnt help me with this Corona specific issue. [import]uid: 10243 topic_id: 6082 reply_id: 21183[/import]
Ok, thanks, I’ll read that as I had missed it.
One thing I’m confused/concerned (a little) about (though I do suspect it’s my issue and not the SDK’s) is that I have a seesaw in my game with things landing on it. After a while, the things on the seesaw tend to sink into the seesaw.
I suspect this is due to the density or friction values, both of which I’m loathed to change due to the side effects they would have. However, I haven’t actually seen any benefit when I have tried messing with them.
m [import]uid: 8271 topic_id: 6082 reply_id: 21189[/import]
They actually said the piston issue was a bug and they are fixing it in the next release. I guess we weren’t doing it wrong after all.
Try switching to 60fps for your seesaw issue and see what that does. I had some objects sinking through other objects mainly because their density was probably too high, but when I switched to 60fps it instantly stopped. I think it’s clear box2d is designed to run at 60hz and while this is possible with Corona its hard to get your game to run at 60fps on all devices because the timestep appears to be tied with the framerate.
For example gamesalad is not tied to the framerate. Meaning if I have a game that is supposed to run at 60fps and it is loaded down and slows the gameplay to 30fps, everything will still be at proper speed and appear pretty smooth. With Corona if my game it set to run at 60fps but can only muster 30fps, it will actually run at half the speed it is supposed too. So this means you’ll have to use 30fps if you want your game to run on older devices, unless of course you have a very simple game that can run at 60fps on all devices. [import]uid: 10243 topic_id: 6082 reply_id: 21318[/import]