Hi again
Yeh, I can understand your worries :) but i'm still here :)
I took a look at your code, seems to be the 0.7 version. I think you
should check out the geometry_rework branch and use that instead. (the
newest version of jinngine) It might fix your problem, and it would
only require smaller adjustments in your code. Let me know how it
works out for you.
Morten
On Sun, Jul 10, 2011 at 12:05 AM, Abhishek Verma
<toabhis...@gmail.com> wrote:
> Hi Morten,
> Thanks for your mail.
> As there was no activity , I was just windering weather jinngine is still on
> or dead.
> Will wait for your responce.
>
> Thanks and Regards
> Abhishek Verma
>
>
> On Fri, Jul 8, 2011 at 6:04 PM, Morten Silcowitz <mor...@silcowitz.dk>
> wrote:
>>
>> hi Abhishek
>> I'll take a look as soon as I can. Its just that I just moved to
>> Dublin, and still don't have internet connection in my apartment. Hang
>> in there.
>>
>> Morten
>>
>>
>> On Wed, Jul 6, 2011 at 8:32 PM, Abhishek Verma
>> <toabhis...@gmail.com> wrote:
>> > Dear friends,
>> > I just joined community and I was trying to understand jinngine physics.
>> > I picked up RagdollExample and tidy up code littlebit and changed few
>> > boxes
>> > to Capsule.
>> >
>> > But output I didnt expect. After falling down, ragdoll capsules keep
>> > jumping
>> > and go out or scene.
>> >
>> > Please advice me what to change to make it work.
>> >
>> > Source Attached..
>> >
>> > Regards,
>> > Abhishek
>> >
>
>
You can always do things as fast as you want to. Every time you call
Scene.tick() all object motions are computed and positions are
integrated forward in time. In the demos the framerate is locked to
around 60hz (vsync) to match the refresh rate of the display device.
But you can just compute all the frames you want (as fast as possible)
and the only display some of them, or record positions/velocities onto
the disk for later analysis.
You most likely want the time-step size to be lower than the size used
in the demos, to increase accuracy.
Morten