Point size #1315
-
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
You'll need to explain where you are coming from as the question is perplexing. What are you trying to do, why and how? |
Beta Was this translation helpful? Give feedback.
-
I am using osg in my application and I get warning "Warning: Point::apply(State&)" when trying to use osg::Point->setSize. This is my CmakeLists:
I think the problem is because of OSG_GL_FIXED_FUNCTION_AVAILABLE but I don't want to change my CMakeLists. How can I set size on points without using osg::Point->setSize? |
Beta Was this translation helpful? Give feedback.
-
Thankyou for providing further information which is crucial. When you select to build with OpenGL fixed function switched off you can't use the GL fixed function state. Do you actually need to compile without OpenGL fixed function backwards compatibility? You loose a great deal of OSG functionality by disabling compatibility. If you are running without fixed function pipeline compatibility then you'll need to provide your own uniforms to the shaders you write. If you are knew to the OSG then I would recommend just moving the VulkanSceneGraph. The VSG is the OSG successor, it supports modern hardware and full shader usage far batter than OSG/OpenGL can ever do and will likely save you time as well as leave you with a better performing and easy to maintain software. The OSG is a legacy API built upon a OpenGL which is a legacy graphics API, it's best kept for maintaining existing applications. |
Beta Was this translation helpful? Give feedback.
Thankyou for providing further information which is crucial. When you select to build with OpenGL fixed function switched off you can't use the GL fixed function state.
Do you actually need to compile without OpenGL fixed function backwards compatibility? You loose a great deal of OSG functionality by disabling compatibility.
If you are running without fixed function pipeline compatibility then you'll need to provide your own uniforms to the shaders you write.
If you are knew to the OSG then I would recommend just moving the VulkanSceneGraph. The VSG is the OSG successor, it supports modern hardware and full shader usage far batter than OSG/OpenGL can ever do and will likely save you time…