[ODE] ODE freezes, can you help?

Phil Teschner philt at microsoft.com
Thu Dec 19 03:29:02 2002


You will want to enable multi-monitor debugging.

Make sure to install the debug DirectX 8.1 runtime then open the DX
Properties application in the Control Panel.  Go to the DirectDraw pane,
click on the Advanced Settings button and toggle the last check box
which is called "Enable Multi-Monitor debugging".

Now the Window will not loose Focus when you are debugging.

Phil

-----Original Message-----
From: Ivan Bolcina [mailto:ivan.bolcina@volja.net] 
Sent: Thursday, December 19, 2002 12:59 AM
To: ode@q12.org
Subject: Re: [ODE] ODE freezes, can you help?

Hi.
I have multi monitor support for my notebook. The only problem is that
device gets lost when I focus visual studio. This is also problem for
other
directx apps, including samples which come with sdk. How to solve it?

But, I dont understand what could I have written that freezes ode. Where
is
the problem? Have I initialized something wrong? What, what? Sometimes
it
works, sometimes it doesnt! I am almost sure there arent any memory
leaks,
since I checked application with fluidstudio memory checker.
But, I game I am doing this:

I initialize : world,space, joint group
I add bodies and geoms, masses to them, I put them in position
for each frame:
    I apply forces and torques to them and they move around
    When collision occures, everything gets f... up.(sometimes) why oh
why



----- Original Message -----
From: "John Savage" <JSavage@data-mate.com>
To: <ode@q12.org>
Sent: Wednesday, December 18, 2002 9:25 PM
Subject: RE: [ODE] ODE freezes, can you help?


> I've one phrase for debugging full screen apps. MultiMonitor.
>
> If you have 98, 2K or Xp Pro then all you need is a crappy PCI
graphics
card
> for 40 bucks and a 15inch monitor for about 100. Plug it all in and
run.
> When you go to debug your program, put the MSVC++ IDE onto the 15" and
> debug. You can step trhough your code line by line and everything on
the
> second monitor while the program is running full screen on your
primary
> monitor. Plus its a cheaper setup than the next best thing, which is
remote
> debugging (requires a second PC!). I've been running multi monitor now
for
> about 4 years and I will never go back to a single monitor desktop!
>
> John
>
>
>
>   _____
>
> John Savage <mailto:jsavage@data-mate.com>
> Software Engineer DataMate Global Communications
> Tel: +1 818 487 3900 ext105
>   _____
>
>
>
> -----Original Message-----
> From: ode-admin@q12.org [mailto:ode-admin@q12.org]On Behalf Of Ivan
> Bolcina
> Sent: Wednesday, December 18, 2002 9:48 AM
> To: ode@q12.org
> Subject: Re: [ODE] ODE freezes, can you help?
>
>
> Hi Martin.
>
> I think I found the bug. I looked test_chain1.cpp in examples and
found
this
> dWorldSetGravity (world,0,0,-0.5);
>
> I didnt have this line in my code. Everything else was completly
identical.
> So, after adding this line in my code, it miracely worked. It also
tried
to
> set
>
> dWorldSetGravity (world,0,0,0);
>
>
>
> but then, it froze again. Could it be ode bug? I think it spent all
this 5
> or even more seconds in steeping the world. Some math stuff, I think.
>
> so I finally did
>
> dWorldSetGravity (world,0.0001f,0.0001f,0.0001f);
>
> Now it woks fine.
>
> One more question. I am having big trouble debuging. You, on the other
hand,
> seem to master this stuff. Can you please describe, which tools you
use
and
> how.I am working with MS VS7, developing full screen directx
game.Currently
> I fprintf all debug messages to file and examine it lately.
>
> thanks for help,
>
> ivan
>
>
> ----- Original Message -----
> From: "Martin C. Martin" <martin@metahuman.org>
> To: "Ivan Bolcina" <ivan.bolcina@volja.net>
> Cc: <ode@q12.org>
> Sent: Wednesday, December 18, 2002 7:39 PM
> Subject: Re: [ODE] ODE freezes, can you help?
>
>
> > > Actually, it doesn't freeze. It takes a 5 seconds to calculate
next
> frame, and then > object colliding are thrown somewhere out of sigth.
In
> next frame, this
> > > repeats. How to debug it?
> >
> > Profile it.  Where is the time being spent?  In graphics?  In the
near
> > callback?  Stepping the world?  Is the hard drive going during those
5
> > seconds?  That might mean you're running out of memory, or loading
> > textures from disk, or something like that.  How much of the 5
seconds
is
> > spent in your process?  Maybe some other task is grabbing the CPU
for a
> > long time, again involving swapping.
> >
> > At 5 seconds, you could probably use clock() for timing.
> >
> > Good luck,
> > Martin
> > _______________________________________________
> > ODE mailing list
> > ODE@q12.org
> > http://q12.org/mailman/listinfo/ode
>
> _______________________________________________
> ODE mailing list
> ODE@q12.org
> http://q12.org/mailman/listinfo/ode
>
> _______________________________________________
> ODE mailing list
> ODE@q12.org
> http://q12.org/mailman/listinfo/ode

_______________________________________________
ODE mailing list
ODE@q12.org
http://q12.org/mailman/listinfo/ode