NewtonHeightFieldCollisionCallback

[Julio Jerez]

Yes, you can raycast from anywhere in your code.
all collsion funtion, includeing raycastion are renetrant in Newton, threfore they can be call from anywhere.

and yes ther are new debug libraries in newton, it will be coll if soem one update Ogrenewt.
I made a patch a while back but is was being ignored completlly. Therefore I can not make any progress with Ogrenewt.

[Lax]

Ok thanks for the info with the thread!

I made a patch a while back but is was being ignored completlly.

What was that for a patch? The problem is, that I'm not the maintainer of Ogrenewt. And as I see in the ogre forum, the progress with ogrenewt is nearly stopped at the moment.

I compiled the project in the debug mode with the newton_d.lib, newton_d.dll from the folder: "...\NewtonWin-2.29\sdk\x32\dll_vs9". The problem is, when I start the application, I get an error, that the file newton.dll is not installed on the computer. I do not know why he wants the newton.dll instead of the newton_d.dll.
I'm wondering, that in the "...\NewtonWin-2.29\sdk\x32\lib_vs9_md" folder (md stands for dynamic lib?) are the dJointLibrary, dMath Libraries with the corresponding dll's but for newton there is only the lib file?

[Julio Jerez]

In forder newtonSDk/sdk/x32/dll_vs9
you will find the pairs:
newton.lib, newton.dll and
newton_d.lib, newton_d.dll

the other forders are for people using static libraries which now also has pairs: newton.lib and newton_d.lib

you should make your debug build link to newton_d.lib and your release build link to newton.lib
then using the newton_d.pdb will show the function that causes any crash in newton,
It will also show memory leaks, and degenerated floats inconsistencies.

that is how the demos in the SDK in 2.29 are using it and it seems to work.
make sure you have SDK 2.29 there was a bug before that crosses linked the libraries.


about the patch, it is here
http://www.newtondynamics.com/downloads/UpdateToNewton25_VS9.patch

It may be old now since I made it for 2.26 I beleive, but I can re-export it again if anyone want to integrated ot the SVN database.
It adds some good things to OgreNewt like Parallel asyncronous execution with smooth interpolation, and serialization to the New Netwon alchemedia format
which simplify debugging problems by a great deal..

but I do not want to spend more time in OgreNewt, because it seems the people using ogrenewt only care when they have a problem with others engine and they come back
to old reliable physics solution OgreNewt, but as soon as the solution is found they move on, and then other user come back for the same problem again, and again, and again.
That makes me waste time in a vicios circle that I could use on anything else.

[Lax]

In forder newtonSDk/sdk/x32/dll_vs9
you will find the pairs:
newton.lib, newton.dll and
newton_d.lib, newton_d.dll

I did like you said. But now things are getting strange: When I start the application in the debug folder, a msgbox appears with the message, that the file "newton.dll" is not installed on the pc. But I configured, to take the newton_d.lib in the visual studio.
Furthermore I need to take the files (dJointLibrary.lib and the dMath.lib) from the static folder: "...\NewtonWin-2.29\sdk\x32\lib_vs9_mt" to compile OgreNewt, too.

I'm not that kind of people, that goes on with other physics libraries. I'm using OgreNewt for several years in my projects for college. But I used in the past older versions of Ogrenewt and newton like version 1.*. Now I'm trying to update everything to newest versions. The problem is, I have not the time to maintain OgreNewt, because the college takes all my nerves and time^^.

[Julio Jerez]

maybe you have and older versions

all of the libraries have the _d version, I verified and it is working, try download the SDK again.

[Julio Jerez]

No, not matter how hard I try, it is a Real Mess, when fiddling wi the teh PDB path and name.

Maybe usin C7 compatible is and option, because is add the debug to teh libraty itself,
do you think tah can be and option?

[Lax]

The hole programming thing is a mess^^. One error solved, another one comes...

all of the libraries have the _d version, I verified and it is working, try download the SDK again.

Ok I will download It and try again.

Maybe usin C7 compatible is and option, because is add the debug to teh libraty itself,
do you think tah can be and option?

Hm my time is running out, I have to finish my project in the near future. And I see many advantages in using vs2010.

Like I said, when I transfer the raycast-function in a separate thread. Then the raycast works (until now). I haven't tested every possible scenario yet.

[Julio Jerez]

Lax, you do not have to get the _d libraries, it was just a sujestion. try the normal libraries and see if the error is still there,
if it is let me know and I debug it.

The Ray cast works, I do no undertand why you has so many problems, in teh demo you send me whe I run the EXE I codul no reproduce twhat you say it was doing.

all I asked was for you to link to the newer SDK so that I can step in debug and verify that in fact the ray cast is working as it should.

[Lax]

I'm using the newest version of newton (version 2.29). The version you tried was 2.29 too, but I linked against the newton.lib, newton.dll (for release). How could that ever work? because all other libraries I linked were debug-libs.
I downloaded the 2.29 version today again.
Now I try to link against the newton_d.lib. I can compile everything (including OgreNewt, my app), but when I start the application, I get an error msgbox, that newton.dll isn't installed on the pc. But in my debugfolder, I have the newton_d.lib and newton_d.dll. But he wants the newton. In VS-Studio I link against the newton_d.

[Julio Jerez]

I do not knwo why by you are teh only person with this problem.
The demo you send I can not run because it crash when I try to use the current DLL.
you must be using an older one. I even forget what was the original problem

can you take the newton.dll and rename it to newton_d.dll?
maybe that will work,

[Lax]

The original problem was: that the raycast with the terrain worked only under certain circumstances. But since I transfered the raycast function into a thread, everything works.

Like I said, I'm using newton2.29.

can you take the newton.dll and rename it to newton_d.dll?

When I renamed the file in newton_d.dll then the errormessage was that newton.dll isn't installed. When I renamed it into newton.dll then the errormessage was that newton_d.dll isn't installed^^.
I took the newton_d.dll and the newton_d.lib into the debugfolder of my app. Then I had to copy this files and rename it into newton.lib and newton.dll and I get no crash anymore. I think this has something to do with vs10. It is really strange, now I have the files: newton.lib, newton.dll, newton_d.lib and newton_d.dll in the debug folder.


I will test everything the next weeks.

[Julio Jerez]

How was it working before? the plibraies are all build with VS 2008
can you just use: newton.h, newton.lib and newton.dll.
Get SDK 2.30 to make sure there are not confusion, I tested all libraries, static and dynamics with and without debug info.