PhysX (v2.7.3) & Irrlicht (v1.4)
-
- Posts: 153
- Joined: Mon Mar 03, 2008 8:42 am
- Location: Suceava - Romania
- Contact:
-
- Posts: 83
- Joined: Fri Apr 11, 2008 3:06 am
- Location: Beaverton, Oregon, US
-
- Posts: 153
- Joined: Mon Mar 03, 2008 8:42 am
- Location: Suceava - Romania
- Contact:
-
- Posts: 83
- Joined: Fri Apr 11, 2008 3:06 am
- Location: Beaverton, Oregon, US
Well, that sort of explains it
I had been able to run physX examples from the control panel, and run the precompiled example from here, so my mind never went to consider that it was a problem with the software runtime! However, I still cannot justify my stupidity.
I downloaded the new version and it seems that everything works now.
Thanks night_hawk, Problem solved.
I had been able to run physX examples from the control panel, and run the precompiled example from here, so my mind never went to consider that it was a problem with the software runtime! However, I still cannot justify my stupidity.
I downloaded the new version and it seems that everything works now.
Thanks night_hawk, Problem solved.
-
- Posts: 368
- Joined: Tue Aug 21, 2007 1:43 am
- Location: The Middle of Nowhere
-
- Posts: 12
- Joined: Thu Jun 12, 2008 12:34 am
-
- Posts: 83
- Joined: Fri Apr 11, 2008 3:06 am
- Location: Beaverton, Oregon, US
Atbruno.arruda wrote:Nice examples.
Could you please let me know if there are any documentation(guide, tutorials) about physX(not counting the samples that come with the SDK) cause I can´t find any theory about it, and I would like to study it.
Thanks very much
there is a lot of documentation that is very helpful. Your filepath may be a little different depending on how you chose to install the sdk.C:\Program Files\NVIDIA Corporation\NVIDIA PhysX SDK\v2.8.1\SDKs\Docs
-
- Posts: 12
- Joined: Thu Jun 12, 2008 12:34 am
Thanks, those are a little introduction and the API.
I´ve found here: http://developer.nvidia.com/forums/inde ... topic=1640
that there were learning lessons, and they are remaking them, they were distibuted since 2.72, so u can get them here:
http://developer.nvidia.com/object/physx_downloads.html
If you want to check out the topics, check here:
http://www.hardforum.com/archive/index. ... 78262.html
Hope that it helps the ones in the same situation. Happy learning
I´ve found here: http://developer.nvidia.com/forums/inde ... topic=1640
that there were learning lessons, and they are remaking them, they were distibuted since 2.72, so u can get them here:
http://developer.nvidia.com/object/physx_downloads.html
If you want to check out the topics, check here:
http://www.hardforum.com/archive/index. ... 78262.html
Hope that it helps the ones in the same situation. Happy learning
hi,
I was able to successfully compile the code but when I click any mouse buttons the program crashes to desktop in the following line:
>> actor->addForce(forceVec);
I am using irrlicht 1.4 and Physx 2.81 with the latest system software drivers installed (8.04.25).
Any help would be appreciated.
Regards
I was able to successfully compile the code but when I click any mouse buttons the program crashes to desktop in the following line:
>> actor->addForce(forceVec);
I am using irrlicht 1.4 and Physx 2.81 with the latest system software drivers installed (8.04.25).
Any help would be appreciated.
Regards
-
- Posts: 83
- Joined: Fri Apr 11, 2008 3:06 am
- Location: Beaverton, Oregon, US
I was going to make a post on this bug earlier....
There are two problems I am having.
1.) after a number of boxes are stacked on top of each other, certain boxes start to flicker and disappear. Some disappear completely and re-appear when struck by another box/sphere.
2.) The same error m506 says. I investigated into this, and with the doc example of a NxUserOutputStream implementation, it brought up this:
This was the code for the NxUserOutputStream implementation:
then when you call NxCreatePhysicsSDK...
Any expert around on PhysX?
There are two problems I am having.
1.) after a number of boxes are stacked on top of each other, certain boxes start to flicker and disappear. Some disappear completely and re-appear when struck by another box/sphere.
2.) The same error m506 says. I investigated into this, and with the doc example of a NxUserOutputStream implementation, it brought up this:
This was the code for the NxUserOutputStream implementation:
Code: Select all
class MyOutputStream : public NxUserOutputStream
{
void reportError (NxErrorCode code, const char *message, const char* file, int line)
{
//this should be routed to the application
//specific error handling. If this gets hit
//then you are in most cases using the SDK
//wrong and you need to debug your code!
//however, code may just be a warning or
//information.
if (code < NXE_DB_INFO)
{
MessageBox(NULL, message, "SDK Error", MB_OK)/*,
exit(1)*/;
}
}
NxAssertResponse reportAssertViolation (const char *message, const char *file,int line)
{
//this should not get hit by
// a properly debugged SDK!
assert(0);
return NX_AR_CONTINUE;
}
void print (const char *message)
{
printf("SDK says: %s\n", message);
}
} myOutputStream;
Code: Select all
MyOutputStream* ptr = &myOutputStream;
gPhysicsSDK = NxCreatePhysicsSDK(NX_PHYSICS_SDK_VERSION, 0, ptr);
-
- Posts: 1029
- Joined: Thu Apr 06, 2006 12:45 am
- Location: Tennesee, USA
- Contact:
-
- Posts: 83
- Joined: Fri Apr 11, 2008 3:06 am
- Location: Beaverton, Oregon, US
Physix is now the property of NVidia
I build it with the latest Versions 1.4x and 2.8x
And after spawn 100 or up spheres i got a crash with similar results >> actor->addForce(forceVec)
looks like the actors are out of predefined memory.
Has some fixes for a stable implementation?
looks like the actors are out of predefined memory.
Has some fixes for a stable implementation?