PhysX 3.4

Expanding and utilizing the engine via C++.
7 posts Page 1 of 1
Timmy
Posts: 363
Joined: Thu Feb 05, 2015 3:20 am
by Timmy » Sat Feb 03, 2018 10:53 am
Hey everyone,

I recently updated the physx code to handle physx 3.4, there is a pull request here . Unfortunately due to licensing restrictions we can't ship binaries with T3D for physx :cry: , so here is how to make it work with the above PR.

*Grab a copy of the PhysX source code: https://github.com/NVIDIAGameWorks/PhysX-3.4 . If you don't have access you must sign up here (it's totally free)
* Now we must compile PhysX (do note due to a bug with VS 2017, NVidia does not currently support it with physx, you must use VS 2015 (either 32 or 64bit)):
Navigate to /where_you_cloned_physx_repo/PhysX_3.4/Source/compiler and choose which compiler. Build both a debug and release build.
* Now we can build T3D with physx support,fire up cmake and select TORQUE_PHYSICS_PHYSX3. This will than need you to select the directory above where you cloned the physx source. You must select the root folder (not the PhysX_3.4 sub folder!)
* When you run the cmake install project it will copy the required files to your game directory.
* Happy physxing :mrgreen:

*Linux note: You must select a cmake build type(by default it is blank!), this is important as the file copy process will fail if you do not

I have tested it on Windows, Linux and MacOS. Obviously if there are any dramas just post it in here and i'll try and fix it. If my instructions above are not very good, just say so and i can make a youtube vid or something showing the process
Bloodknight
Posts: 138
Joined: Tue Feb 03, 2015 8:58 pm
by Bloodknight » Sat Feb 03, 2018 10:58 pm
In VS2017 there is a way to install the VS2015 toolset, however, i'm not sure how to access this directly. I'm assuming there's VS 2015 developer command prompt to build manually. Maybe somebody with better command and knowledge of the VS toolset will be able to chip in with more details, this should at least save having to fully install VS2015.
noemen
Posts: 19
Joined: Tue May 29, 2018 3:46 pm
 
by noemen » Tue Jun 12, 2018 1:05 pm
working?
Timmy
Posts: 363
Joined: Thu Feb 05, 2015 3:20 am
by Timmy » Tue Jun 12, 2018 2:23 pm
working?
Afaik yes, @ JeffR has reported he couldn't get this PR working but after multiple attempts i have never been able to replicate the errors he was getting and it worked ok. If anyone else would like to give it a try that would certainly help.
noemen
Posts: 19
Joined: Tue May 29, 2018 3:46 pm
 
by noemen » Wed Jun 13, 2018 2:26 am
working?
Afaik yes, @ JeffR has reported he couldn't get this PR working but after multiple attempts i have never been able to replicate the errors he was getting and it worked ok. If anyone else would like to give it a try that would certainly help.
I spent the morning researching, I realized that both Nvidia and Visual Studio 2017 fixed some problems. I'm going to do some tests ... Remembering that it's good to use the latest version of VS 2017 and PhysX 3.4 SDK updated.
Timmy
Posts: 363
Joined: Thu Feb 05, 2015 3:20 am
by Timmy » Wed Jun 13, 2018 12:48 pm
working?
Afaik yes, @ JeffR has reported he couldn't get this PR working but after multiple attempts i have never been able to replicate the errors he was getting and it worked ok. If anyone else would like to give it a try that would certainly help.
I spent the morning researching, I realized that both Nvidia and Visual Studio 2017 fixed some problems. I'm going to do some tests ... Remembering that it's good to use the latest version of VS 2017 and PhysX 3.4 SDK updated.
I will say VS 2017 is untested as at the time of me doing the PR for this, physx 3.4 didn't support vs 2017 due to some compiler bugs.
noemen
Posts: 19
Joined: Tue May 29, 2018 3:46 pm
 
by noemen » Wed Jun 13, 2018 7:37 pm

I will say VS 2017 is untested as at the time of me doing the PR for this, physx 3.4 didn't support vs 2017 due to some compiler bugs.
True, I did some testing and they did not work very well. I am a beginner in C ++ language. I can interpret a script, but I can not fix any errors. I still have a lot to learn. I'll get your tip and use the VS2015, thank you very much.

Excuse my English, I'm not native. :D
7 posts Page 1 of 1

Who is online

Users browsing this forum: No registered users and 4 guests