Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
H3D.org Feeds

Forum Index


Board index » All Posts




Re: glew error when starting H3DViewer (compiled trunk version)
#1
Quite a regular
Quite a regular


Well, it is not in a rush, but it would be nice

I use the PhysX3.4 release from their GitHub page.

Sign up at this page to gain access: https://developer.nvidia.com/physx-source-github
Sign up for game development and then you should have access via the GitHub account u link in ~20 min, was a while ago I did this so there might be a few extra steps, but straight forward.

I have used the vc14win64 solution files to compile the physx libs, added the documented changed above to findphysx3 cmake file (both adding search paths to libs and include dir).



Posted on: 4/21 11:04
Top


Re: glew error when starting H3DViewer (compiled trunk version)
#2
Webmaster
Webmaster


Crappit. I have to test then.

I probably won't have time until next week though. It would help if you could point out the link to the physx3 version you use.

Posted on: 4/21 10:06
Top


Re: Packaging H3DAPI application
#3
Quite a regular
Quite a regular


Thank you for the information!

Posted on: 4/20 15:18
Top


Re: glew error when starting H3DViewer (compiled trunk version)
#4
Quite a regular
Quite a regular


I reset the environment variables to point to trunk version, same problem when compiling, did not affect the outcome

Posted on: 4/20 15:14
Top


Re: glew error when starting H3DViewer (compiled trunk version)
#5
Webmaster
Webmaster


H3D_EXTERNAL_ROOT might affect where it finds externals that are in the External directory (i.e not physx).
Ok, then I need to find some time to setup tests for compiling against that version of physX3.

Posted on: 4/20 14:44
Top


Re: Packaging H3DAPI application
#6
Webmaster
Webmaster


No it does not affect which packaging program you can use, you can do whatever you like.

And yes you can just use .pyc-files. However the main file started from H3DLoad/H3DViewer probably have to be a .py file.

Apart from that you can modify H3DLoad to your hearts content to add encryption of x3d files and such.
Note also, that if you use stock H3DLoad/H3DViewer to start your application then the H3D_ROOT that is set on the system will decide the settings for your program, if that is what you want it is fine, but otherwise you might get conflicts that you do not want.

There are no special versions of H3D compiled for commercial use. Note that the GPL release of H3D is exactly that, a GPL release. You can not link against the prebuilt (PREBUILT) binaries that come with that one and be GPL free because it links against libraries not included in a commercial license from SenseGraphics (i.e Chai3d).
You have to build your own version of H3DAPI for use with your application.
If this is something you need help with then contact SenseGraphics directly.

Posted on: 4/20 14:41
Top


Re: glew error when starting H3DViewer (compiled trunk version)
#7
Quite a regular
Quite a regular


In this matter the latest trunk version, at least from yesterday or maybe the day before, to have a fresh version to test problems that occurs if they are already solved in the latest version of H3D before posting in this forum to get the answer that it is already solved


the #ifdefs does not seem to be existing in trunk.

If not the environment variables(set to old 2.3 version, $H3D_ROOT, $H3D_EXTERNAL and bin folders in $PATH) break things in the compilation, which I don't believe...?

Posted on: 4/20 13:42
Top


Re: Packaging H3DAPI application
#8
Quite a regular
Quite a regular


Yes, we have a commercial license, does that affect which packaging program we can use?

Are there special releases of H3D for commercial use?

Is it possible to hide away the python/x3d code to greater extent than compiled python files (.pyc)? Since our application only uses these to 99%

Posted on: 4/20 13:35
Top


Re: glew error when starting H3DViewer (compiled trunk version)
#9
Webmaster
Webmaster


You were using release 2.3 right?

Could be that the version of PhysX that existed when that was implemented always had these. Trunk might have #ifdefs" to handle these cases.

Posted on: 4/20 13:27
Top


Re: Weird behavior of Particle systems with Bounded- and GravityPysicsModel
#10
Webmaster
Webmaster


If they started with a 0 speed then yes that should happen otherwise they might reach higher the first time.
There is something buggy about it indeed.

Posted on: 4/20 13:26
Top



TopTop
(1) 2 3 4 ... 956 »






(C) 2012 SenseGraphics AB    ---    Powered by XOOPS