Re: [osg-users] Float vs double in BOUNDINGSPHERE and BOUNDINGBOX

Hi Maxim, The default to BoundingBoxf and BoundingSphref is partly a historical reason. Scene graphs traversals are memory bandwidth limited so you only want to pay for the extra memory size if there is specific value in doing so. Robert. On Fri, 29 Jun 2018 at 05:00, Maxim Stere wrote: > >

Re: [osg-users] OpenSceneGraph-3.6.2 release candidate 3

Made a Windows GL3 profile PR #570. It should fix some GL3 CMake problems on windows... Thank you, --Maxim -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=74220#74220 ___

[osg-users] Float vs double in BOUNDINGSPHERE and BOUNDINGBOX

Hi, Is there a reason why OSG_USE_FLOAT_BOUNDINGBOX and OSG_USE_FLOAT_BOUNDINGSPHERE are set to YES in cmake by default? Since most CPUs now use doubles natively and emulate floats, making float calculations a little slower, would it not be better for OSG speed and performance to have these

Re: [osg-users] GL3 Profile

Made a PR #570 I will investigate windows GL libraries further, and see if I can make the Kronos GL headers work on windows without much modifications. If I succeed I'll make another PR with fixes that will give users full GL functionality on Windows. Thank you,

[osg-users] [forum] Android can't build osgdb_png

Hi, I'm building Android libs on Windows, other 3rdparty libs like osgdb_jpeg can all be build, except osgdb_png , is there something special and i missed? Thank you! Cheers, lin -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=74217#74217

Re: [osg-users] The naming of VulkanSceneGraph

On Thu, 28 Jun 2018 at 14:53, Eric Sokolowsky wrote: > Trademark holders *must* defend their trademarks, or they lose them. Indeed this is true. It's only part of the story though. Khronos mission is to develop and promote open APIs, as part of this they trademark projects they undertake, they

Re: [osg-users] Conan C++ dependency manager

Hi, I forgot to add the plugin path to PATH in the script You can contribute to add something like this and make a PR... it would be something like it osgPlongins="release dependant plugin path" self.env_info.PATH.append(os.path.join(self.package_folder, osgPlongins)) Cheers cfjob wrote: >

Re: [osg-users] Open to updates to the Doxygen configuration files?

Hi Robert, Thank you for your response. Laurens just coincidentally answered a similar question in the thread "[osg-users] OSG API Guides" earlier. I didn't realize we needed to set BUILD_DOCUMENTATION:BOOL=ON when running CMake, and I didn't know the make target existed, either. With his

Re: [osg-users] OSG API Guides

Ah, got it! It looks like the instructions on http://www.openscenegraph.org/index.php/documentation/guides/user-guides/106-create-doxygen-documentation Are wrong. You first need to run cmake on the solution with BUILD_DOCUMENTATION:BOOL=ON Then if you are in Windows you need to manually tell

Re: [osg-users] The naming of VulkanSceneGraph

Trademark holders *must* defend their trademarks, or they lose them. On Mon, Jun 25, 2018 at 6:43 PM, Chris Hanson wrote: > I think the Vulkan compliance tests (and name usage) only applies to > implementations OF the Vulkan API. I don't think it applies to software > USING Vulkan. > > I think

Re: [osg-users] Constructor parameters of osg::Uniform

Am 28.06.2018 um 15:03 schrieb Robert Osfield: > On Thu, 28 Jun 2018 at 13:57, Robert Osfield wrote: >> The original osg::Uniform class is a bit of unwieldy mess. In >> hindsight we shouldn't have gone for this particular implementation as >> it's a bit too open ended. > As a bit of background,

Re: [osg-users] Constructor parameters of osg::Uniform

It would be the easiest putting an "explicit " in front of the constructor but I guess there would be far to many reclaims then :) - Werner - Am 28.06.2018 um 15:03 schrieb Robert Osfield: > On Thu, 28 Jun 2018 at 13:57, Robert Osfield wrote: >> The original osg::Uniform class is a bit of

Re: [osg-users] Constructor parameters of osg::Uniform

On Thu, 28 Jun 2018 at 13:57, Robert Osfield wrote: > The original osg::Uniform class is a bit of unwieldy mess. In > hindsight we shouldn't have gone for this particular implementation as > it's a bit too open ended. As a bit of background, Mike Weiblen with a bit of input from myself created

Re: [osg-users] Constructor parameters of osg::Uniform

On Thu, 28 Jun 2018 at 13:06, Sebastian Messerschmidt wrote: > @Robert: > Any insights? The original osg::Uniform class is a bit of unwieldy mess. In hindsight we shouldn't have gone for this particular implementation as it's a bit too open ended. In master I have written a osg::UniformBase

Re: [osg-users] Constructor parameters of osg::Uniform

Hi Werner, Hi all, I recently discovered a strange case in creation of a Uniform: farRadiusRescaleUniform=newosg::Uniform("farRadiusRescale",2.0f); The only constructor I could find is like that: Uniform(Typetype,conststd::string,intnumElements=1); The wrong construction sometimes

[osg-users] Constructor parameters of osg::Uniform

Hi all, I recently discovered a strange case in creation of a Uniform: farRadiusRescaleUniform=newosg::Uniform("farRadiusRescale",2.0f); The only constructor I could find is like that: Uniform(Typetype,conststd::string,intnumElements=1); The wrong construction sometimes leads to unexpected

Re: [osg-users] Exporting OpenFlight Models

Hi Robert, Thanks for the merge! It helps. A little explanation, if you have any interest. It's a little long, but I hope to explain why we're looking at Core Profile. I'd like to think it's for good reason. I'm with you on the OSX issues. I think it's a shame about what's going on over

Re: [osg-users] Conan C++ dependency manager

Hi, I encounter a problem that the osgDB::readImageFile can not read the image files. I know that the osgDB need related plugins to read files, and I uploaded the osgPlugins folder with other osg libs. It seems conan didn't let osg find the plugins, did anyone encounter similar problem? How to

Re: [osg-users] Open to updates to the Doxygen configuration files?

Hi Orphen, On Thu, 28 Jun 2018 at 07:52, Orphen wrote: > I tried to build the Doxygen documentation on master today using Doxygen > 1.8. The Doxyfiles are a bit dated, and some parts are malformed (ex: > environment variable expansion). This causes Doxygen to report some > errors and then give

Re: [osg-users] OSG API Guides

The working doxyfiles are generated by cmake in the build folder. (if BUILD_DOCUMENTATION:BOOL=ON) Those will have these variables expanded. Laurens. On Tue, Jun 26, 2018 at 3:21 PM Maxim Stere wrote: > Just got a chance to sit down and try to build the documentation. > > Is the Doxy file

[osg-users] Open to updates to the Doxygen configuration files?

Hi Robert, I tried to build the Doxygen documentation on master today using Doxygen 1.8. The Doxyfiles are a bit dated, and some parts are malformed (ex: environment variable expansion). This causes Doxygen to report some errors and then give up. Are you open to me updating the Doxyfiles?

[osg-users] OpenSceneGraph-3.6.2 release candidate 3

Hi All, My plan is to tag 3.6.2 tomorrow, as there were two fixes yesterday that I merged with the 3.6 branch I have made release candidate 3: https://github.com/openscenegraph/OpenSceneGraph/tree/OpenSceneGraph-3.6.2-rc3 Thanks for testing and feedback :-) Robert. -- ChangeLog since rc2