Re: [osg-users] OSGPL - Legal questions on version and compatibility

On Wed, 6 Mar 2019 at 10:42, Matthias Schütze wrote: > Currently, I am checking the possibilities to update my company's proprietary > application from using OSG 3.0.1 to use a newer version. On GitHub, I could > see that with OSG 3.4 the license document changed from OSGPLv0.0 to > OSGPLv1.0.

Re: [osg-users] updatecallback deprecation proposal

Hi Julien, The complexity is about retaining backwards compatibility. Changing it would break end users code and likely silently for us as only a small percentage of end users test releases prior to them be released so we don't find out we've broken their code until it's too late, so we need to

[osg-users] OSGPL - Legal questions on version and compatibility

Hi, Currently, I am checking the possibilities to update my company's proprietary application from using OSG 3.0.1 to use a newer version. On GitHub, I could see that with OSG 3.4 the license document changed from OSGPLv0.0 to OSGPLv1.0. There are only minor differences and I understand that

[osg-users] Values of osg_FrameTime?

Hi, I translate a specific OSG shader program to one without OSG. I think, I have a problem to calculate the values of osg_FrameTime. I know it is the frame time in seconds, but in which value limits? Is it just going up from 0.0 to FLOAT.MAX? Thank you! Cheers, Arvid -- Read

[osg-users] [build] unresolved external symbol in daeReader.obj

Hi, I am trying to build osg3,6 with collada lib taken from 3rd_party_x64_Vs2017_v141 with vs2017. I am facing following error unresolved symbol char const colladaDOM141 ..in plugins dae (daeReader,obj) like this i am getting 159 link error all with dae*.obj . please suggest Thank you!