PhysX - Visual Studio 2013

Gaming and Visualization Technologies APIs Physics Modeling (closed)
41

Seconding the need for /MD and /MDd PVD libraries (namely PhysXVisualDebuggerSDKDEBUG). Isn’t DLL runtime library preferred practice for visual studio applications? I would change all of my code to use /MT but I’d like to adhere to standard practice.

42

I have the same problem. Could you put another link for the vc12 built?

43

I would also need acces to the FTP server for the libraries for Visual Studio 2013. Thank you very much.

44

PhysX3Extensions.lib(ExtDefaultSimulationFilterShader.obj) : error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’
LNK2038: mismatch detected for ‘RuntimeLibrary’: value ‘MT_StaticRelease’ doesn’t match value 'MD_DynamicRelease

Need a build for physx binary’s for vs++ 2013 please.
Thank you in advance for your help.

45

PhysX3Extensions.lib can be rebuilt using the source and project files in “\Source\compiler.” Pick the directory of the newest visual studio version and let visual studio upgrade the project files to vs 2013.

I am having a problem trying to rebuild the PhysXProfileSDK.lib files. The source exists but I’m not finding any project files for it and I haven’t been able to setup a project to build the source correctly.

46

Same problem here, I managed to compile a working version of my application using the VS2013 configuration in combination with the PhysX v90 libs and dll’s.

Everything works except that there is no CudaContextManager created, ie my application is not using the GPU and it falls back to CPU.

Using the right lib files (v120) in combination with the VS2013 compiler could solve the problem, but I can only test it if I can download the libs.

creacon

47

The CudaContextManager problem wasn’t related to the libs. I forgot to copy the PhysX3Gpu_x64.dll to the application directory.

So I guess I found some kind of bug or maybe it is intented that way.
If the PhysX3Gpu_x64.dll is missing there is no warning, but you wont be able to create the CudaContextManager and will fall back to CPU.

Still would like those libs though ;-)

creacon

48

I am having a problem with PhysXProfileSDK.lib and my 2013 VS.
Can anyone have solution for that problem?

49

Hi Mike,

While compile the sample of WIN8ARM with VS2013 express, I got the following error.
2>PhysXProfileSDKDEBUG.lib(PxProfileEventImpl.obj) : error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’ in SampleBridges.obj
2>PhysXVisualDebuggerSDKDEBUG.lib(PvdNetworkStreams.obj) : error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’ in SampleBridges.obj

can be rebuild
PhysX3CharacterKinematic*.lib
PhysX3Extensions*.lib
PhysX3Vehicle*.lib

but can’t rebuild those
PhysXProfileSDK*.lib
PhysXVisualDebuggerSDK*.lib

and the above link expires. Can you upload again the version vs2013? or new version of 3.3.2?

50

this is a duplicated post
forum return internal error 500 when post

51

I am also using Visual Studio 2013 Update 4 and PhysX 3.3.2, could I get access to the FTP server to download the libraries?

Thank you very much!

52

Hi Mike,

Can I also have a download link to physx 3.3.2 libs rebuilt for VS2013 please ?

Many thanks.

53

I came to this thread also looking for VS2013 libs, after seeing the login expired I decide to build them myself, which is actually pretty easy. Below is the process for anyone looking to do that same thing.

  1. Download to latest build from the github website (PhysX SDK: Latest Features & Libraries | NVIDIA Developer) this has a VS2013 project within it.
  2. Open \Source\compiler\vc12win32\PhysX.vcxproj project or 64 for (x64).
  3. For all the projects in the solution change the Runtime Library to match your own project- Project Proprieties → C/C++ → Code Generation → Runtime Library
  4. Build
  5. New libs can be found in \Lib
54

Hi…
Could help me … i have the next console error.

error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’ in fire.obj C:\engine\PxTaskDEBUG.lib(CudaWrapper.obj) engine
error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’ in main.obj C:\engine\PxTaskDEBUG.lib(CudaWrapperWindows.obj) engine
error LNK2038: mismatch detected for ‘_MSC_VER’: value ‘1700’ doesn’t match value ‘1800’ in main.obj C:\engine\PhysXProfileSDKDEBUG.lib(PxProfileEventImpl.obj) engine

im working with the last Physx version (3 3 2)… and im using the VS2013.

55

I also have some issues with the PhysX 3.3.3 SDK getting to compile in DEBUG properly with my application:

Fehler 2 error LNK2038: Konflikt ermittelt für “_MSC_VER”: Der Wert “1700” stimmt nicht mit dem Wert “1800” in FBO.obj überein. E:\Development\Fluid Simulation\PhysX_Test\Test1\PxTaskDEBUG.lib(CudaWrapper.obj) FluidSandbox
Fehler 3 error LNK2038: Konflikt ermittelt für “_MSC_VER”: Der Wert “1700” stimmt nicht mit dem Wert “1800” in FBO.obj überein. E:\Development\Fluid Simulation\PhysX_Test\Test1\PxTaskDEBUG.lib(CudaWrapperWindows.obj) FluidSandbox

I already have compiled the entire PhysX SDK 3.3.3 source from GITHUB in RELEASE and DEBUG mode - so everything should be compiled with _MSC_VER 1800… but for some reason i dont know “PxTaskDEBUG.lib” does not work this way…

Altough compiling in RELEASE mode does work!

56

I have the same problem for VS 2015:

PhysX3ExtensionsCHECKED.lib(ExtDefaultErrorCallback.obj) : error LNK2038: mismatch detected for '_MSC_VER': value '1700' doesn't match value '1900' in cameraclass.obj
1>PhysX3ExtensionsCHECKED.lib(ExtDefaultErrorCallback.obj) : error LNK2001: unresolved external symbol sprintf

I have repeatedly requested access to the PhysX github so I could compile it for myself, however I have never received an invite code over email.

Would I be able to jump onto the ftp and grab the 3.3.3 sdk + the latest libraries?