from:"Sebastian Messerschmidt"

Hi. Sorry I don't on my computer right now, but it seems you are not providing vertex shaders. I'm not sure, but that might cause trouble. I'll get back to the issue tommorow or on Monday. 

Cheers
Sebastian
-- 
Sent from my Android phone with GMX Mail. Please excuse my brevity.On 9/2/17, 21:36 antiro black  wrote:
Hi Sebastian,
I'm compiling under debian jessie 64 bits and am running a NVIDIA GTX 970. The drivers have been updates recently and I am running version 384.69 now.
I included a compilable minimal example based on the osgmultiplerendertargets example. Without VertexAttributeAliasing it generates two texture using MRT, a red and a green one, it then combines these in a second pass to generate the final texture (yellow). (The red and green intermediate textures are shown in small quads to the side.)
When I enable the attribute aliasing (as in the included code), the two textures generated in the MRT pass turn into gradients, as if something has gone wrong with the mapping.
Screenshots:
The expected result (which I get without attribute aliasing): https://ibb.co/kHEogv
The result with aliasing: https://ibb.co/d9cfuF
Code:
/* OpenSceneGraph example, osgmultiplerendertargets.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
* THE SOFTWARE.
*/
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
//#include "RenderingUtility.h" //to easily view intermediate textures
//
// Below is relatively straight forward example of using the OpenGL multiple render targets (MRT) extension
// to FrameBufferObjects/GLSL shaders.
//
// Another, more sophisticated MRT example can be found in the osgstereomatch example.
//
osg::Geode *createScreenQuad(float width,
		 float height,
		 float scale,
		 osg::Vec3 corner)
{
		osg::Geometry* geom = osg::createTexturedQuadGeometry(
corner,
osg::Vec3(width, 0, 0),
osg::Vec3(0, height, 0),
0,
0,
scale,
scale);
		osg::ref_ptr quad = new osg::Geode;
		quad->addDrawable(geom);
		int values = osg::StateAttribute::OFF | osg::StateAttribute::PROTECTED;
		quad->getOrCreateStateSet()->setAttribute(
new osg::PolygonMode(osg::PolygonMode::FRONT_AND_BACK,
		 osg::PolygonMode::FILL),
values);
		quad->getOrCreateStateSet()->setMode(GL_LIGHTING, values);
		return quad.release();
}
osg::Camera *createHUDCamera(double left=0,
		 double right=1,
		 double bottom=0,
		 double top=1)
{
		osg::ref_ptr camera = new osg::Camera;
		camera->setReferenceFrame(osg::Transform::ABSOLUTE_RF);
		camera->setClearMask(GL_DEPTH_BUFFER_BIT);
		camera->setRenderOrder(osg::Camera::POST_RENDER);
		camera->setAllowEventFocus(false);
		camera->setProjectionMatrix(osg::Matrix::ortho2D(left, right, bottom, top));
		camera->getOrCreateStateSet()->setMode(GL_LIGHTING, osg::StateAttribute::OFF);
		return camera.release();
}
osg::ref_ptr createTextureDisplayQuad(
		const osg::Vec3 ,
		osg::StateAttribute *tex,
		float scale,
		float width=0.3,
		float height=0.2)
{
		osg::ref_ptr hc = createHUDCamera();
		hc->addChild(createScreenQuad(width, height, scale, pos));
		hc->getOrCreateStateSet()->setTextureAttributeAndModes(0, tex);
		return hc;
}
// The callback modifies an input image.
struct MyCameraPostDrawCallback : public osg::Camera::DrawCallback
{
MyCameraPostDrawCallback(osg::Image* image):
_image(image)
{
}
virtual void operator () (const osg::Camera& /*camera*/) const
{
if (_image && _image->getPixelFormat()==GL_RGBA && _image->getDataType()==GL_UNSIGNED_BYTE)
{
// we'll pick out the center 1/2 of the whole image,
int column_start = _image->s()/4;
int column_end = 3*column_start;
int row_start = _image->t()/4;
int row_end = 3*row_start;
// and then halve their contribution
for(int r=row_start; rdirty();
}
else if

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout



Hi,

Unfortunately your example doesn't compile. If you provide a minimal 
(i.e. compileable ) example showing the problem we could take a look 
into it.

Due to copyright reasons I cannot give you an example from my code base.

Cheers
Sebastian

Hi,

I'm still struggling with getting setUseVertexAttributeAliasing(true) to 
combine rendering to textures.

To this end, I made made a tiny change to the osgmultiplerendertargets example 
to see if I could adapt that example to work with 
setUseVertexAttributeAliasing(true).

Aside from adding some lines to view the intermediate textures, my only change 
was enabling VertexAttributeAliasing as follows:


Code:
viewer.realize();
viewer.getCamera()->getGraphicsContext()->getState()->setUseVertexAttributeAliasing(true);




Given that the code only uses some fragment shaders, which use fixed colors and 
don't rely on things like gl_Vertex or gl_Normal I assumed no changes to them 
would be needed. Yet enabling VertexAttribute shaders breaks rendering, 
disabling it again fixes it.

Maybe I'm completely misunderstanding the idea behind VertexAttributeAliasing, 
all I want is to reuse the shaders from my other project, which requires 
control over the vertex attribute layout...
If anyone can tell me what I'm doing wrong or has a working example of MRT with 
setUseVertexAttributeAliasing(true), that would be highly appreciated.

For reference, here is the entire modified code:

Code:

/* OpenSceneGraph example, osgmultiplerendertargets.
*
*  Permission is hereby granted, free of charge, to any person obtaining a copy
*  of this software and associated documentation files (the "Software"), to deal
*  in the Software without restriction, including without limitation the rights
*  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
*  copies of the Software, and to permit persons to whom the Software is
*  furnished to do so, subject to the following conditions:
*
*  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
*  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
*  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
*  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
*  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
*  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
*  THE SOFTWARE.
*/

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 

#include 

#include 
#include 

#include "RenderingUtility.h" //to easily view intermediate textures
//
// Below is relatively straight forward example of using the OpenGL multiple 
render targets (MRT) extension
// to FrameBufferObjects/GLSL shaders.
//
// Another, more sophisticated MRT example can be found in the osgstereomatch 
example.
//


// The callback modifies an input image.
struct MyCameraPostDrawCallback : public osg::Camera::DrawCallback
{
 MyCameraPostDrawCallback(osg::Image* image):
 _image(image)
 {
 }

 virtual void operator () (const osg::Camera& /*camera*/) const
 {
 if (_image && _image->getPixelFormat()==GL_RGBA && 
_image->getDataType()==GL_UNSIGNED_BYTE)
 {
 // we'll pick out the center 1/2 of the whole image,
 int column_start = _image->s()/4;
 int column_end = 3*column_start;

 int row_start = _image->t()/4;
 int row_end = 3*row_start;

 // and then halve their contribution
 for(int r=row_start; rdata(column_start, r);
 for(int c=column_start; cdirty();
 }
 else if (_image && _image->getPixelFormat()==GL_RGBA && 
_image->getDataType()==GL_FLOAT)
 {
 // we'll pick out the center 1/2 of the whole image,
 int column_start = _image->s()/4;
 int column_end = 3*column_start;

 int row_start = _image->t()/4;
 int row_end = 3*row_start;

 // and then halve their contribution
 for(int r=row_start; rdata(column_start, r);
 for(int c=column_start; cdirty();

 //print

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout

Hi Chris,

I'm also transitioning a legacy GL OSG project with a mix of custom shaders to
modern GL bit by bit. And I've also had lots of trouble and headache with the
built-in modern GL vertex attrib aliasing setting.

It seems crazy that the official advice is to write shaders and use OSG just like legacy GL, and
OSG will then change your shader code and reinterpret deprecated calls to make it work via
"modern" GL: Obviously in years to come when GL newcomers want to use OSG the official
line can't be "learn how GL was 20 years ago, write your OSG code like that, and the system
will make it work".

So I'm afraid this isn't as simple as it could be, but of course it's still
easier than converting raw GL calls..
Who told you something like this? OSG is totally capable of using modern
GLSL. For some legacy support you might need to write appropriate
visitors, but there is nothing stopping you using modern approaches.

Here is my only advice since I'm not yet finished myself:
My recommendation is just leave that attrib aliasing setting alone; you can use
modern GL anyway. Just make sure that you use the setVertexAttribute() calls
instead of setTextureCoords() / setNormals() / etc, and use the same attrib
location numbering convention as OSG (I believe NVidia's drivers enforce those
conventions, so you can get the vertex positions at loc=0).
Basically you're duplicating the vertexAttributeAliasing mechanism.
There might be problems with non-conforming drivers, but in general the
mapping is fixed on all conforming OpenGL drivers I've used (And the
mechanism works on a lot of heterogeneous machines)

Then you'll want to get a copy of the ShaderGen class so you can customize
because you'll likely want to modify it yourself. You can use this code to hook
into osgDB::readNode()'s behavior to setup your shaders/attribs/etc the way you
want.
I don't see how this is related to ShaderGen (I suppose you're talking
about the old class). I strongly suggest to write your own shaders and
use the setDefine (#pragmatic shader composition) mechanism to create
shader variations.

Cheers
Sebastian

You then need to set useModelViewUniforms, which seems to be less harmful than
useVertexAttribAliasing and will make sure osg_ModelViewMatrix is set.

Interested to compare notes on how you go anyway

http://www.hrwallingford.com/facilities/ship-simulation-centre
(http://www.hrwallingford.com/facilities/ship-simulation-centre)

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71598#71598

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout



Hi Antiro,

Hi,

I'm still struggling with getting setUseVertexAttributeAliasing(true) to 
combine rendering to textures.

To this end, I made made a tiny change to the osgmultiplerendertargets example 
to see if I could adapt that example to work with 
setUseVertexAttributeAliasing(true).

Aside from adding some lines to view the intermediate textures, my only change 
was enabling VertexAttributeAliasing as follows:


Code:
viewer.realize();
viewer.getCamera()->getGraphicsContext()->getState()->setUseVertexAttributeAliasing(true);
That's interesting. I've just checked my code-base and I definitively 
set up the aliasing very early before adding anything to the scene graph.




Given that the code only uses some fragment shaders, which use fixed colors and 
don't rely on things like gl_Vertex or gl_Normal I assumed no changes to them 
would be needed. Yet enabling VertexAttribute shaders breaks rendering, 
disabling it again fixes it.

Maybe I'm completely misunderstanding the idea behind VertexAttributeAliasing, 
all I want is to reuse the shaders from my other project, which requires 
control over the vertex attribute layout...
If anyone can tell me what I'm doing wrong or has a working example of MRT with 
setUseVertexAttributeAliasing(true), that would be highly appreciated.
Enabling the aliasing will also replace all gl_ things in the shaders 
you pass to the scene graph and it will simple add vertex attributes for 
all default attributes. See the State.cpp resetVertexAttributeAlias for 
reference.
There is no magic involved. Unfortunately I don't have any spare time to 
check your code sample, but I can promise that this definitively working 
without trouble. I've been using MRT with modern shaders for years in my 
deferred pipeline, and I don't recall having any problems at all. If 
you're using NVidia under windows you might consider using NSight to 
check your bindings.

What kind of GPU are you using? I experienced a lot of trouble using Intel.

Cheers
Sebastian


For reference, here is the entire modified code:

Code:

/* OpenSceneGraph example, osgmultiplerendertargets.
*
*  Permission is hereby granted, free of charge, to any person obtaining a copy
*  of this software and associated documentation files (the "Software"), to deal
*  in the Software without restriction, including without limitation the rights
*  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
*  copies of the Software, and to permit persons to whom the Software is
*  furnished to do so, subject to the following conditions:
*
*  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
*  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
*  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
*  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
*  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
*  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
*  THE SOFTWARE.
*/

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 

#include 

#include 
#include 

#include "RenderingUtility.h" //to easily view intermediate textures
//
// Below is relatively straight forward example of using the OpenGL multiple 
render targets (MRT) extension
// to FrameBufferObjects/GLSL shaders.
//
// Another, more sophisticated MRT example can be found in the osgstereomatch 
example.
//


// The callback modifies an input image.
struct MyCameraPostDrawCallback : public osg::Camera::DrawCallback
{
 MyCameraPostDrawCallback(osg::Image* image):
 _image(image)
 {
 }

 virtual void operator () (const osg::Camera& /*camera*/) const
 {
 if (_image && _image->getPixelFormat()==GL_RGBA && 
_image->getDataType()==GL_UNSIGNED_BYTE)
 {
 // we'll pick out the center 1/2 of the whole image,
 int column_start = _image->s()/4;
 int column_end = 3*column_start;

 int row_start = _image->t()/4;
 int row_end = 3*row_start;

 // and then halve their contribution
 for(int r=row_start; rdata(column_start, r);
 for(int c=column_start; cdirty();
 }
 else if (_image && _image->getPixelFormat()==GL_RGBA && 
_image->getDataType()==GL_FLOAT)
 {
 // we'll pick out the center 1/2 of the whole image,
 int column_start = _image->s()/4;
 int column_end = 3*column_start;

 int

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout

2017-09-01 Thread Sebastian Messerschmidt


Hi Antiro,

I don't have an idea why it is not working.
For which camera's state set did you enable it?
Have you tried to check this with a simplistic non-MRT/FBO setup?
Which OSG-Version do you use (its working with 3.4.x definitively)

I've been using this for years, so there must be some error somewhere else.

Cheers
Sebastian

Hi Sebastian,

I was under the impression that the "layout(...) in ..." command was 
essentially a variable declaration and that hence only the location and type needed to 
match. I now also changed the name, this does not seem to have any effect though..

new vertex shader code:

Code:
#version 330 core
layout(location = 0) in vec4 osg_Vertex;
layout(location = 1) in vec3 osg_Normal;
layout(location = 2) in vec4 osg_Color;
layout(location = 3)in vec4 osg_MultiTexCoord0;
layout(location = 4)in vec4 osg_MultiTexCoord1;
layout(location = 5)in vec4 osg_MultiTexCoord2;
layout(location = 6)in vec4 osg_MultiTexCoord3;
layout(location = 7)in vec4 osg_MultiTexCoord4;
layout(location = 8)in vec4 osg_MultiTexCoord5;
layout(location = 9)in vec4 osg_MultiTexCoord6;
layout(location = 10)in vec4 osg_MultiTexCoord7;

out vec3 Normal;
out vec2 TexCoords;
out vec3 WorldPos;

uniform mat4 osg_ModelViewMatrix;
uniform mat3 osg_NormalMatrix;
uniform mat4 osg_ProjectionMatrix;


void main()
{
 gl_Position = osg_ProjectionMatrix * osg_ModelViewMatrix * osg_Vertex;
 WorldPos = (osg_ModelViewMatrix * osg_Vertex).xyz;
 Normal = osg_NormalMatrix * osg_Normal;
 TexCoords = osg_MultiTexCoord0.xy;

}



If I use the shader without the UseVertexAttributeAliasing enabled I see red 
silhouettes for the different models, when looking at the normals texture output (as 
if all normals are <1,0,0> ), which I expect is caused by the shader reading 
wrong  on unitialized attributes.

with UseVertexAttributeAliasing enabled I get no output.



Thank you!

Cheers,
antiro

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71588#71588





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout

2017-09-01 Thread Sebastian Messerschmidt


Hi Antiro,> Hi Sebastian,


Thanks for the quick response. The osg_XXX matrices work perfectly. The 
setUseVertexAttributeAliasing() however does not seem to work. Where I had some 
output before, now don't get anything with it enabled

Does osg always give the exact layout which you posted? or is this dependent on 
the data that is loaded?

for refence, here is a stripped down version of a geometry pass which I'm 
currently testing with (all 3 outputs are black with the attributeAliasing 
turned on):




Your code doesn't use the osg_ prefixed aliases at all. You really need 
to make the name and slot match...


Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] using modern shaders with osg - setting vertex attribute layout

2017-09-01 Thread Sebastian Messerschmidt



Hi Antiro,


Hi,

I am converting a project written in pure opengl to use OSG to improve 
compatibility and reduce maintenance.  The original project used a deferred 
rendering pipeline with a pretty big set of custom shaders. I would like to 
reuse these shaders with minimum adjustments.

In order to do this I want to use the same uniform names and the same layout 
for the VAO. I figured out that I can add callbacks to set the ModelView / 
Projection / etc matrices to uniforms with the same names as used in in the 
shaders, so that is taken care of.

I do however not know how to specify the vertex attribute layout. My shaders 
all start with the following:
#version 330 core //so can't use gl_Normal etc
layout(location = 0) in vec3 position
layout(location = 1) in vec3 normal
layout(location = 2) in vec2 texCoords
layout(location = 

I'm currently just using osgDB::readNodeFile() to read in the geometry and I'm 
assuming I need to do something more sophisticated to control how the vertex 
attributes are organized, but have been unable to figure out what.

If anyone could point me in the right direction, that would be most helpful!


The easiest way is to convert the shaders to use the osg_ -prefix and to 
turn on the vertex attribute aliasing (basically all OSG will provide 
all gl_ inputs)


A list:

//OSG inputs
layout(location = 0) in vec4 osg_Vertex;
layout(location = 1) in vec3 osg_Normal;
layout(location = 2) in vec4 osg_Color;
layout(location = 3)in vec4 osg_MultiTexCoord0;
layout(location = 4)in vec4 osg_MultiTexCoord1;
layout(location = 5)in vec4 osg_MultiTexCoord2;
layout(location = 6)in vec4 osg_MultiTexCoord3;
layout(location = 7)in vec4 osg_MultiTexCoord4;
layout(location = 8)in vec4 osg_MultiTexCoord5;
layout(location = 9)in vec4 osg_MultiTexCoord6;
layout(location = 10)in vec4 osg_MultiTexCoord7;


In order to turn on aliasing:

viewer->getCamera()->getGraphicsContext()->getState()->setUseModelViewAndProjectionUniforms(true);
viewer->getCamera()->getGraphicsContext()->getState()->setUseVertexAttributeAliasing(true);

Note, that the first line will set up the gl_XYZMatrix aliases, so no 
need for a custom callback for this (at least for the std-matrices)


So you get these:
uniform mat4 osg_ModelViewProjectionMatrix;
uniform mat4 osg_ModelViewMatrix;
uniform mat4 osg_ViewMatrixInverse;
uniform mat3 osg_NormalMatrix;
uniform mat4 osg_ViewMatrix;
etc.

Cheers
Sebastian





Thank you!

Cheers,
antiro

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71584#71584





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Setting the transform matrices

2017-08-30 Thread Sebastian Messerschmidt


Hi Chris,> Hi Robert,


For now it'd be too time consuming to isolate a test case. Supporting modern 
OpenGL does seem like it would be more natural if you had some way of hooking 
into the setting of the model matrix and vertex attributes so that you could 
assign / name / alter them yourself.


You can use any matrix you like. Simply set it up as uniform and use it 
in the shader. Since there is underlying scenegraph you need to consider 
disabling culling for the node or set its matrix accordingly.


Your hooking can be done by simply adding a transform-group over your 
element and set the the desired matrix from there.
A minimal example explaining what you want to achieve might be very 
helpful.



Cheers
Sebastian



Cheers,
Chris


http://www.hrwallingford.com/facilities/ship-simulation-centre 
(http://www.hrwallingford.com/facilities/ship-simulation-centre)

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71557#71557





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Please test OpenSceneGraph-3.4 in prep for 3.4.1

2017-08-18 Thread Sebastian Messerschmidt


Hi Nickolai,

Robert wants something like this:

https://i.stack.imgur.com/SjnI9.png

It is called "Call stack" in VisualStudio.

Cheers
Sebastian


Do you mean this stack?



ntdll.dll!779315ee()

[Указанные ниже фреймы могут быть неверны и (или) отсутствовать, 
символы для ntdll.dll не загружены]
ntdll.dll!779315ee()
ntdll.dll!7792015e()
nvoglv32.dll!5e627fed() 
nvoglv32.dll!5dc2ea9d() 
osg.dll!54882912()  
osg.dll!5482aa94()  
osg.dll!5482fac2()  
osgViewer.dll!54bf6f3a()
kernel32.dll!755d14dd() 
osg.dll!547f3901()  
osgUtil.dll!54a3d27e()  
osgUtil.dll!54a399a5()  
osgUtil.dll!54a3d8a3()  
osgUtil.dll!54a3ab9f()  
osgUtil.dll!54a3dc76()  
osgUtil.dll!54a4112c()  
osg.dll!5483ec8b()  
OpenThreads.dll!5529218b()  
msvcr100.dll!7226c556() 
msvcr100.dll!7226c600() 
kernel32.dll!755d33ca() 
ntdll.dll!77949ed2()
ntdll.dll!77949ea5()




Did forcing the recreation of GL work?



I did not understand this question.

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71446#71446





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Dynamical loading of resources

2017-08-14 Thread Sebastian Messerschmidt



Hi Joachim,

Hi,

I was tasked with writing a visualizer for large 3D areas, the kind of areas 
that may not fit into RAM, either because they are too large, or because the 
RAM on the machine is not large enough ;).

I am new to OSG, this is my first post to the forum (hello, guys :)!). I was 
wondering how to perform out-of core handling of the 3D resources I intent to 
render. Its not possible for me to load everything and then start rendering, i 
need to constantly load new parts of the environment and unload geometry that 
is out of view.
That is where PagedLOD comes into play. It allows for background loading 
of tiles.


So I would like to know, is there any mechanism in OSG (or OSG Earth) which 
already supports this? Or would I have to implement it myself? Either way, I 
would be very happy if one of you could give me a rough explanation of how to 
approach this problem with OSG.


See the osgPagedLod example for reference.
If you need a resolution-pyramid approach, VPB(VirtualPlanetBuilder) can 
generate multiscale data for paging from various sources.
Sorry for just giving you pointers, but a short answer might be better 
than none ;-)


Thank you, I appreaciate yout help!

Cheers,
Jey

Cheers
Sebastian

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71409#71409





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Setting the transform matrices

2017-08-09 Thread Sebastian Messerschmidt


Hi Chris,


Why are you trying to override the default behavior in the first place?
Simply set the node's matrices by adding a transform node with absolute 
reference frame as parent/modify the camera's projection matrix. If you 
need it per graphics context you might consider using different scene 
graphs per camera(thus context).


Rather than asking for on obscure seeming approach, you might get more 
ideas by describing what you are after.


Cheers
Sebastian



Hi,

What is the proper way to set the view/projection matrix to a uniform yourself? 
I've found that trying to deal with the osg_ built-in uniforms which do all 
sorts of renaming etc is unreliable and would like to be able to just set 
everything myself manually.

At the moment I'm setting the view / projection matrix uniforms within the 
camera's initialdrawcallback, but I'm not sure if this is the right way to do 
it that will ensure the uniform value will only be used within that camera and 
not within other cameras (since it needs to work across multiple screens and 
render stages).

Is there some code within OSG that ensures that a uniform assigned to a camera 
will only apply to the graphics context for the thread that set it?


Thank you!

Cheers,
Chris


http://www.hrwallingford.com/facilities/ship-simulation-centre 
(http://www.hrwallingford.com/facilities/ship-simulation-centre)

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71391#71391





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] RenderBin vs. SlaveCamera

2017-08-07 Thread Sebastian Messerschmidt



Hi Werner,

I'm using slave cameras only for certain multi-channel setups where I 
need multiple viewports rendering the same content with different 
frusta. For multipass applications (and I simply consider HUD to be a 
separate pass) I always use normal cameras (with absolute reference 
frame for fullscreen passes and relative for composing passes).


You can assign an explicit number to the camera order by using.

camera->setRenderOrder(osg::Camera::PRE_RENDER, pass_number);

I use the PRE_RENDER scheme, since all passes of my offscreen rendering 
need to complete before the output is presented. Given your scenario you 
could of course simply set the render order of your HUD camera to 
something high.


Setting up rendering order with the Geometry RenderBin seems akward, 
since the HUD geometry is supposed to be rendered by the HUD-camera 
only. So a slave camera might not be the best option (apart from the 
fact, that the HUD is supposed to have its own projection and 
transform-matrix).


hth
Sebastian


Hi all,

I'm restructuring my project because I want to implement some multi pass 
effects.
I have some problems understanding the different approaches for example 
when

creating HUD displays.
The approach I used so far is attaching a SlaveCamera and puttung it in 
PostRender pass.
On the other hand I found an approach of just attaching the matrices to 
the root node and

assigning the HUD geometry to a RenderBin with high number.

I'd like to understand the difference of the approaches and the pros and 
cons.


Is there any one who can help me with that?

Thanks

- Werner -

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG-GLSL triangle adjacency

2017-07-21 Thread Sebastian Messerschmidt


Hi Nabil,


Thank you Sebastian. So If i set the DrawArrays mode of the 
PrimitiveSet, does it suffice?

Otherwise, is it easy to implement? Sorry but i'm newby in OSG.

Can you elaborate on this?

Usually you need to set the program-parameter for output: 
GL_GEOMETRY_INPUT_TYPE and simply pass you geometry.


So when using triangles for instance, you need to pass 3 additional 
vertices per triangle (the neighboring ones). You can get the 
appropriate order from the openGL spec or various examples.
I'd start with a minimal example with a fixed vertex set to see what 
needs to be set in the state and program.



The osggeometryshader example might help here to get started.

Cheers
Sebastian


On 21 July 2017 at 09:36, Sebastian Messerschmidt 
<sebastian.messerschm...@gmx.de <mailto:sebastian.messerschm...@gmx.de>> 
wrote:




Hi Nabil,

Hello,
I'm using geometry shader with OSG to do some operations on mesh
using GPU.
When i use /triangles_adjacency/  in the input layout, my shader
crashes.
I tried with /layout(triangles) in/  and it's running well.

Is there any configuration in OSG that i should use, or a
pre-processing on the mesh to understand triangle adjacency?

You need to pre-process the mesh to get the adjacency information.
There is no facility in OSG that I know of, wich does this for you.


Cheers
Sebastian


Regards,
Nabil


___
osg-users mailing list
osg-users@lists.openscenegraph.org
<mailto:osg-users@lists.openscenegraph.org>

http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

<http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org>




--
Nabil Khalifa

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG-GLSL triangle adjacency

2017-07-21 Thread Sebastian Messerschmidt




Hi Nabil,

Hello,
I'm using geometry shader with OSG to do some operations on mesh using GPU.
When i use /triangles_adjacency/  in the input layout, my shader crashes.
I tried with /layout(triangles) in/  and it's running well.

Is there any configuration in OSG that i should use, or a pre-processing 
on the mesh to understand triangle adjacency?
You need to pre-process the mesh to get the adjacency information. There 
is no facility in OSG that I know of, wich does this for you.



Cheers
Sebastian


Regards,
Nabil


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] GLBeginEndAdapter

2017-07-21 Thread Sebastian Messerschmidt




Hi John,



Hi,

I am compiling some code with the current git repository version of OSG and found that 
State's "getGLBeginEndAdapter" has been removed.  Looking through the history, 
I see this happened at: commit e11e45a2e36de91bbe956223c43e8c5a50f9b72b.

The comment is only "Removed GLBeginEndAdapter as it is no longer needed".  
Well, my code seems to need it.  What do I need to do to update my code to not need it?  
(I realize this is fixed pipeline code, but it's old code and it works.  So a complete 
re-write is not desirable.)
The glBegin/End stuff is deprecated since OpenGL 2.0, which was released 
almost 13 Years ago, so it is long due.


The modern way is to use drawarrays. In your case it might be as simple 
as putting all the vertices into a vertex buffer and render it via a 
PimitiveSet using QUAD.


Take a look at the osggeometry-example. It covers all you need.
If you have detailed questions, feel free to consult the 
forum/mailing-list again.



Cheers
Sebastian




Code:
osg::GLBeginEndAdapter& gl = (state.getGLBeginEndAdapter());

gl.Color4fv(_surfaceColor.ptr());

bool drawBackSide = true;
bool drawFrontSide = true;

// draw back side.
if(drawBackSide)
{
   for(int i = 0; i + 1 <= _density; i++)
   {
 const auto az1 = _azMin + (i*azIncr);
 const auto az2 = _azMin + ((i + 1)*azIncr);

 gl.Begin(GL_QUAD_STRIP);
 for(int j = 0; j <= _density; j++)
 {
   ...



Thank you!

Cheers,
John
Code:




--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71289#71289





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Escape Key

2017-07-19 Thread Sebastian Messerschmidt



Hi,

I've just checked. My osg-3.4.0 based code uses

"
else if (osgGA::GUIEventAdapter::KEY_Escape == ea.getKey())
"

so it obviously works ..
The Eventhandler is the first however (since it is a console), so maybe 
this might be worth a shot.


Cheers
Sebastian

Hello,

I am using an event handler for catching keyboard's escape key.

However, my osgGA::GUIEventAdapter::getKey() returns 0x1B, when it 
should be returning osgGA::GUIEventAdapter::KEY_Escape (which is 0xFF1B).


What's wrong here? the Osg's enum, or my code?


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] RTT + shaders example

2017-07-12 Thread Sebastian Messerschmidt



Hi Michael,


As a side note:
In order to get your matrices to your shaders simply use the osg_ 
equivalents to the gl_-Matrices and setup aliasing:


Viewer->getCamera()->getGraphicsContext()->getState()->setUseModelViewAndProjectionUniforms(true);
Viewer->getCamera()->getGraphicsContext()->getState()->setUseVertexAttributeAliasing(true);


In general you need to create the render-target textures and bind them 
to the FBO of your RTT-Camera. Basically there is the 
osgmultiplerendertargets example which shows you how to achieve this.


Once you have a working example rendering the gbuffer, you can simply 
add more absolute cameras to the graph to do the screenspace calculations.


Also take a look at osgPPU, which might offer some insight.

Cheers
Sebastian




Hi all,

I am trying to figure out RTT in combination with shaders for 
implementing a gbuffer but I can't get the different examples to work 
together.
This is a working example for using my shaders, but without RTT and also 
for setting the StateSet for the model and not the camera.


const char* vertSource =

 "#version 400\n"

 "uniform mat4 MV;\n"

 "uniform mat4 N;\n"

 "uniform mat4 P;\n"

 "layout(location = 0) in vec4 Vertex;\n"

 "layout(location = 1) in vec3 Normal;\n"

 "smooth out vec3 p;\n"

 "smooth out vec3 n;\n"

 "void main(void) {\n"

 "p = (MV * Vertex).xyz;\n"

 "n = normalize(N * vec4(Normal, 0)).xyz;\n"

 "gl_Position = P * vec4(p, 1);\n"

 "}\n";

const char* fragSource =

 "#version 400\n"

 "in vec3 p;\n"

 "in vec3 n;\n"

 "layout(location = 0) out vec4 position;\n"

 "layout(location = 1) out vec4 normal;\n"

 "layout(location = 2) out float depth;\n"

 "void main(void) {\n"

 "position = vec4(p,1);\n"

 "normal = vec4(n,0);\n"

 "depth = gl_FragCoord.z;\n"

 //"gl_FragColor = vec4(n,1);\n"

 "}\n";

#define Test1

struct ProjectionMatrixCallback: public osg::Uniform::Callback {

ProjectionMatrixCallback(osg::Camera* camera) :

_camera(camera) {

}

virtual void operator()(osg::Uniform* uniform, osg::NodeVisitor* nv) {

uniform->set(_camera->getProjectionMatrix());

}

osg::Camera* _camera;

};

struct NormalMatrixCallback: public osg::Uniform::Callback {

NormalMatrixCallback(osg::Camera* camera) :

_camera(camera) {

}

virtual void operator()(osg::Uniform* uniform, osg::NodeVisitor* nv) {

osg::Matrixd viewMatrix = _camera->getViewMatrix();

osg::Matrixd normalMatrix = osg::Matrix::inverse(viewMatrix);

uniform->set(normalMatrix);

}

osg::Camera* _camera;

};

struct ModelViewMatrixCallback: public osg::Uniform::Callback {

ModelViewMatrixCallback(osg::Camera* camera) :

_camera(camera) {

}

virtual void operator()(osg::Uniform* uniform, osg::NodeVisitor* nv) {

osg::Matrixd viewMatrix = _camera->getViewMatrix();

osg::Matrixd modelMatrix = 
osg::computeLocalToWorld(nv->getNodePath());

osg::Matrixd modelViewMatrix = modelMatrix * viewMatrix;

uniform->set(modelViewMatrix);

}

osg::Camera* _camera;

};

int main(int, char**) {

 osgViewer::Viewer viewer;

 osg::Node* model = osgDB::readNodeFile("cow.osgt");

 osg::ref_ptr root = new osg::Group();

 //create camera

 osg::Camera* camera = viewer.getCamera();

 // create shader

 osg::ref_ptr program = new osg::Program;

 program->setName("shader");

 program->addShader(new osg::Shader(osg::Shader::VERTEX, vertSource));

 program->addShader(new osg::Shader(osg::Shader::FRAGMENT, fragSource));

 osg::StateSet* state = model->getOrCreateStateSet();

 state->setAttributeAndModes(program.get(), osg::StateAttribute::ON);

 // add uniforms

 osg::Uniform* modelViewMatrix = new osg::Uniform(osg::Uniform::FLOAT_MAT4, 
"MV");

 modelViewMatrix->setUpdateCallback(new ModelViewMatrixCallback(camera));

 state->addUniform(modelViewMatrix);

 osg::Uniform* normalMatrix = new osg::Uniform(osg::Uniform::FLOAT_MAT4, 
"N");

 normalMatrix->setUpdateCallback(new NormalMatrixCallback(camera));

 state->addUniform(normalMatrix);

 osg::Uniform* projectionMatrix = new osg::Uniform(osg::Uniform::FLOAT_MAT4, 
"P");

 projectionMatrix->setUpdateCallback(new ProjectionMatrixCallback(camera));

 state->addUniform(projectionMatrix);

 // turn lights off

 state->setMode(GL_LIGHTING, osg::StateAttribute::OFF);

 // scene state run

 root->addChild(model);

 viewer.setSceneData(root.get());

 viewer.setUpViewOnSingleScreen(0);

 return viewer.run();

}

Another working example with RTT camera but without shaders can be found

Re: [osg-users] EXTERNAL: Forum

2017-07-12 Thread Sebastian Messerschmidt


Hi,

Could you point to a specific post? The ones I checked at glance seem to 
be mirrored correctly.


Cheers
Sebastian


I could be wrong, but I don't think the link between the mail list and forum is 
working any more. I see quite a few new posts on the forums, and have not 
gotten them through the mail list.

-Original Message-
From: osg-users [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf 
Of Sebastian Messerschmidt
Sent: Monday, July 10, 2017 4:10 AM
To: OpenSceneGraph Users
Subject: EXTERNAL: [osg-users] Forum

Hi folks,

The forum seems up and running again. My best guess is, that Art Tevs (who is 
hosting the forum) has fixed the issue.

Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Forum

2017-07-10 Thread Sebastian Messerschmidt


Hi folks,

The forum seems up and running again. My best guess is, that Art Tevs 
(who is hosting the forum) has fixed the issue.


Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG forum error: phpBB : Critical Error - Could not connect to the database

2017-06-30 Thread Sebastian Messerschmidt



Hi Chris,> If Art can't be found, AlphaPixel could take over hosting. 
But we'd
presumably need Art's assistance to get the web media and database 
copied to our server, which makes it sort of a chicken and egg problem. :(


Thank you for the offer.
If we take this step we should update the forum software anyways. I'm 
not terribly experienced with this kind of stuff, but I guess importing 
the posts should be possible. I'm not quite sure what to do about the 
accounts. There are literally 10.000 of them, 9000 not active 
postersMaybe we should discuss this with Robert.


Maybe someone in community has experiences setting up, up2date forums.


Cheers
Sebastian






On Thu, Jun 29, 2017 at 9:22 AM, Sebastian Messerschmidt 
<sebastian.messerschm...@gmx.de <mailto:sebastian.messerschm...@gmx.de>> 
wrote:


Hi Glenn,

We are aware the forum is down. We're still waiting for some contact
with Art Tevs.

Cheers
Sebastian > Greetings!

Subject OSG forum error:
Got message:

phpBB : Critical Error

Could not connect to the database

That is all!

David Glenn
Senior Graphics Software Engineer
TARIF Lab!
david.e.glenn@navy.mil <mailto:david.e.glenn@navy.mil>
760-939-3291 



___
osg-users mailing list
osg-users@lists.openscenegraph.org
<mailto:osg-users@lists.openscenegraph.org>

http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

<http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org>

___
osg-users mailing list
osg-users@lists.openscenegraph.org
<mailto:osg-users@lists.openscenegraph.org>
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
<http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org>




--
Chris 'Xenon' Hanson, omo sanza lettere. xe...@alphapixel.com 
http://www.alphapixel.com/

Training • Consulting • Contracting
3D • Scene Graphs (Open Scene Graph/OSG) • OpenGL 2 • OpenGL 3 • OpenGL 
4 • GLSL • OpenGL ES 1 • OpenGL ES 2 • OpenCL
Legal/IP •Code Forensics •Digital Imaging • GIS • GPS • 
osgEarth • Terrain • Telemetry • Cryptography • LIDAR • Embedded • 
Mobile • iPhone/iPad/iOS • Android
@alphapixel <https://twitter.com/alphapixel> facebook.com/alphapixel 
<http://facebook.com/alphapixel> (775) 623-PIXL [7495]



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG forum error: phpBB : Critical Error - Could not connect to the database

2017-06-29 Thread Sebastian Messerschmidt


Hi Glenn,

We are aware the forum is down. We're still waiting for some contact 
with Art Tevs.


Cheers
Sebastian > Greetings!

Subject OSG forum error:
Got message:

phpBB : Critical Error

Could not connect to the database

That is all!

David Glenn
Senior Graphics Software Engineer
TARIF Lab!
david.e.glenn@navy.mil
760-939-3291



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osg::Group Child Problem

2017-06-13 Thread Sebastian Messerschmidt


Hi Latha,

You're most likely measuring your framerate with a debug-build.
Always measure in release-mode! OSG can easily handle tens of thousand 
of quads if the scene graph is well balanced.


Cheers
Sebastian


Hi

  in my  application i am drawing a quad about 1 kilometer length and 0.1 
meters width.i am getting frame rate Around 45 FPS.

 Now i am drawing each quad about 1 meter length and .1 meters width,then i 
am adding all quads to one group node, in this case i am getting frame rate 
around 25 FPS.

  is there any alternative way for drawing all quads of about 1 meter 
length and 0.1 meters width and adding to scene, for maintaining frame rate 
about 45 FPS ?

Thank you!

Cheers,
Latha

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=71042#71042





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] How to use openscenegraph to realize approaching zero driver overhead

2017-05-23 Thread Sebastian Messerschmidt


Hi Qiaokun,

Hi,

Approaching Zero Driver Overhead (Presented by NVIDIA) can substantially 
improved efficiency  in OpenGL. But, I don't find any interface to call AZDO in 
the osg source code. Can we realize it in osg finally?
If you encountered this problem, please tell me how to combine osg and AZDO. If 
I need to write new interface in osg source code?
There is no single interface, as AZDO is a more a paradigm than a 
concrete implementation. OSG offers various elements to help you 
approach it (e.g. various buffer objects, support for draw-instanced, 
indirect drawing etc, image load/store, bindless textures). There are 
some extensions which are currently not part of the OSG-core such as 
sparse textures, and various other improvements.



So in the end you'll have to invest some work to add the missing 
extension. Using the graph to use AZDO-techniques usually boils down to 
create the appropriate visitors or custom drawables. A good starting 
point (although not minimal example)  is the osggpucull example - it 
shows how to use draw-indirect on a scene graph. I successfully use this 
technique to render millions of instances of simple trees and thousands 
of complex elements like houses.


Cheers
Sebastian




Thank you!

Cheers,
Qiaokun

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70956#70956





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] [osgPlugins] Osg to fbx

2017-05-09 Thread Sebastian Messerschmidt

It should work just fine with a newer FBX SDK. The API changed and it seems they changed the signature. If you need to use the old 2014 SDK simply change it to char *.

Cheers
Sebastian
-- 
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 09.05.17, 16:38, Joe Kindle  schrieb:
sorry. i mean the latest stable release (3.4.0)

Thank you!

Cheers,
Joe

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70893#70893





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Multiple render passes and multithreading

2017-05-03 Thread Sebastian Messerschmidt


Hi Glenn,



Sebastian,

Have you tried setting the data variance to DYNAMIC on the StateSet
containing the Uniform?

That's the first thing I would try -- not sure whether it works on
Uniforms though.


Thanks, that indeed did the trick :-)
Thinking twice makes it obvious; declaring it dynamic will prevent it 
from being written to while being read.


Cheers
Sebastian



Glenn Waldron

On Wed, May 3, 2017 at 11:49 AM, Sebastian Messerschmidt
<sebastian.messerschm...@gmx.de <mailto:sebastian.messerschm...@gmx.de>>
wrote:

Hi,

I've just stumbled upon something I find hard to understand.
My setup contains multiple cameras (using FBO and MRT) with a
specific render-order set to them. The first camera is essentially a
render-scene-to-MRT pass.
In the simplest case a second camera will pick up the textures
rendered to and use them to draw to the framebuffer.

A cull-callback is attached to the group containing the cameras. The
callback simply extracts the current ViewMatrix and passes it to the
stateset as a uniform. This uniform is used in one of later
cameras/passed to reconstruct worldspace from the depth buffer.

Now while this all works great when setting the viewer to
SingleThreaded, it seems that using multithreading in the viewer
causes the Uniform for the ViewMatrix to be from the previous frame
in some cases. From my understanding the cull-visitor runs
asynchronously to the drawing, causing the uniform to be either from
the correct or from another frame.

What would be the multithreaded-cull/draw alternative to get the
ViewMatrix (or any other camera-related values) used for rendering
in the first camera down the chain reliably?

Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
<mailto:osg-users@lists.openscenegraph.org>
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
<http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org>




___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Multiple render passes and multithreading

2017-05-03 Thread Sebastian Messerschmidt


Hi,

I've just stumbled upon something I find hard to understand.
My setup contains multiple cameras (using FBO and MRT) with a specific 
render-order set to them. The first camera is essentially a 
render-scene-to-MRT pass.
In the simplest case a second camera will pick up the textures rendered 
to and use them to draw to the framebuffer.


A cull-callback is attached to the group containing the cameras. The 
callback simply extracts the current ViewMatrix and passes it to the 
stateset as a uniform. This uniform is used in one of later 
cameras/passed to reconstruct worldspace from the depth buffer.


Now while this all works great when setting the viewer to 
SingleThreaded, it seems that using multithreading in the viewer causes 
the Uniform for the ViewMatrix to be from the previous frame in some 
cases. From my understanding the cull-visitor runs asynchronously to the 
drawing, causing the uniform to be either from the correct or from 
another frame.


What would be the multithreaded-cull/draw alternative to get the 
ViewMatrix (or any other camera-related values) used for rendering in 
the first camera down the chain reliably?


Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Test

2017-05-03 Thread Sebastian Messerschmidt




Works for me ;-)

HI All,

Just checking osg-users/forum is still up.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Limitation of Displaying buildings, roads and trees etc to increase frame rate

2017-04-21 Thread Sebastian Messerschmidt


Hi Rambabu,

Hi,Actually iam able to displaying the buildings,roads on the terrain using 
shape files in osgearth,How to display the buildings,roads etc on the desktop 
screen coordinates only and how can i limit the remaining part where 
buildings,roads are loading for the purpose of increase of frame rate ?


Do you mean frustum culling? This already done by OSG. You can limit the 
number of items in the scene by using LODs with appropriate distances. 
Again: try to put some more effort in describing your problem.


Cheers
Sebastian



Iam using osg 3.4.0,osg earth 2.8.0,windows 8.1
Any Help is appreciated.

...

Thank you!

Cheers,
Rambabu

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70793#70793





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Regarding Slowing loading of buildings in osg

2017-04-21 Thread Sebastian Messerschmidt


Hi Rambabu,
  > Hi,Iam Using polygons and drapping the buildings texture on that in 
the terrain using osgearth,Buildings are coming but my problem is 
loading slowly in the output scene,How to load the buildings immediately 
after launching the output scene and upon moving from one place to 
another place buildings are loading slowly how to solve this?


You're not supplying any information on what your buildings are and what 
mechanism you use for loading the buildings. If this a osgEarth specific 
question you might want to use the osgEarth-forum


Cheers
Sebastian



Iam using osgearth 2.8.0,osg 3.4.0,windows 8.1
Any Help is appreciated.

...

Thank you!

Cheers,
Rambabu

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70794#70794





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Selective ClipNode




Am 4/18/2017 um 2:17 PM schrieb Ale Maro:

Hi Sebastian,

I would like to avoid that becouse each node may have complex (dynamic) 
transformations so I should traverse the scene, calculate the global 
transformation for each node and update each transformation for the children of 
the sibling-group
Sorry I don't understand what you mean. If you simply put (at the top 
level) parts like this:


SCENE
|-CLIP
|-Childs
|-NON_CLIP  
|-Childs

the childs in this example can have arbitary transformations...
If you cannot place your nodes like this, you can take a look at the 
ClipNode-implementation and maybe inherit and change the parts that 
control the clipping state to set it effectively per child somehow.


The other option is to simply use a shader that implements the clipping 
and to switch it on/off via uniform.


Cheers
Sebastian




Ale

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70780#70780





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Selective ClipNode


Hi Ale,


in my scene graph I have a root node of type osg::ClipNode.
In this way I can add easily clipping planes to my scene. This works fine.

Now I would like to exclude some nodes from clipping. I wonder if ClipNode 
supports something like a visitor mask to selectively apply clipping to 
children.
You can always put the nodes to be excluded from clipping into a 
sibling-group of the ClipNode.


Cheers
Sebastian


Thank you in advance.

Best regards
Ale

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70778#70778





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Fast move a lot of nodes to another group




Am 4/15/2017 um 6:24 PM schrieb Yura Ivanov:

Hi,

I created stateset with bool uniform to indicate that node is selected and mat 
uniform with current mouse transform. To select nodes, I set this uniforms to 
nodes and all transformation preforms in shader. On mouse release, all 
transform applies to nodes by calling setMatrix and mat uniform sets to 
identity. Everything works fast and after all I don’t have extra nodes and 
statesets. Maybe my approach in this task is wrong, but many editors, for 
example 3dsMax, can work with big number of objects. And bad structure of scene 
in this case is user problem.
Thank you very much, especially for optimize.


This will disable "native" picking of the nodes however. Also I wonder 
why this should be more efficient than putting every node under a 
transform in the first place.
What you're doing is effectively a poor implementation of instancing. A 
better approach (if you want to use the uniform approach) is to setup a 
uniform buffer object (see [0]) containing the matrices and to use the 
draw-instanced version of your geometry to fetch it based on its 
gl_InstanceId. A version that scales better is to use a texture object 
to hold the matrices (see [1])



[0]
http://3dcgtutorials.blogspot.de/2013/09/instancing-with-openscenegraph-part-ii.html

[1]
http://3dcgtutorials.blogspot.de/2013/08/instancing-with-openscenegraph.html

Cheers
Sebastian



Cheers,
Yura

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70767#70767





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Scale problem while transforming object in vertex shader



Hi Yura

Hi,

I have a transform matrix and I want to apply it in shader. I pass it into 
uniform and set gl_Position = 
gl_ModelViewProjectionMatrix*my_transfrom_matrix*gl_Vertex.
If I set translate only, everything is ok. If I set translate and scale - 
translate multiplies by scale and transform is wrong (object is too far if 
scale>1.0). If I apply this transform not using shader (by SetMatrix) 
everything is ok. What I am doing wrong?

Matrix multiplication is not cummutative in every case.
Try
gl_Position = gl_ModelViewMatrix * matrix * gl_ProjectionMatrix * 
gl_Vertex.


Cheers
Sebastian



Thank you!

Cheers,
Yura

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70768#70768





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Lightning

2017-04-13 Thread Sebastian Messerschmidt


Hi Latha,



Hi,
I am working on 'Lighting' to blink lights on a sphere by making 
osg::StateAttribute ON and OFF ,its working fine.But i am
not able to make that sphere itself as light souce(means from sphere light is 
not diffusing,just it is blinking),how to apply different light properties.


If you need the Sphere to be a self-illuminated geometry you need to set 
the emissive-material properties (osg::Material. Alternatively you might 
want to check osgSim::LightPoint.


Cheers
Sebastian


Thank you!

Cheers,
Latha

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70758#70758





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Forum problems

2017-04-12 Thread Sebastian Messerschmidt


Hi Jannik,



Hi,

I've seen this quite often in the past; so far deleting the site cookies and 
logging back in always solved it (for a while anyway).

That indeed did the trick.

Cheers
Sebastian


Cheers,
Jannik

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70752#70752





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Forum problems

2017-04-12 Thread Sebastian Messerschmidt


Hi folks,

Is anyone else experiencing forum problems related to getting  a "502 
Bad Gateway" for some topics?
@Robert: I sent you a private message/email concerning the topic. Could 
you please check if you got it?


Cheers
Sebastian
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Fast move a lot of nodes to another group

2017-04-10 Thread Sebastian Messerschmidt


Hi Yura,

Hi,

Quads are unique and images are different.
Sorry but I cant make screenshot of real images because of author. It is just 
like big puzzle. This is editor, and user decides how many objects can be.
I am using PagedLods to draw images and have no problem with memory. I have 
problem with moving a lot of nodes by user input. If I put put them into matrix 
i can move only it. This is fast but i need to move nodes to another group. 
Maybe I can use NodeCallback?


I think you need to think outside of the box here. There is more than 
one way to draw a collection of quads. You could render them as a big 
vertex array or even instanced and modify the sub-region of your vertex 
buffer/instance matrices instead of moving individual nodes around. If 
you need individual texturing, that still could be done via texture 
arrays or atlas-texturing.


If you absolutely want to keep them in your tree-structure you can still 
keep duplicates and simply turn them off by setting an appropriate 
node-mask (copy them to the new transform and disable drawing in the 
original group),
As a second step you could periodically sort the child vectors by the 
nodemask and batch-remove non-drawn childs from it (this is faster, 
since sorting doesn't need to resize the vector and removing a 
contiguous number of elements from the end of a vector is essentially free).


You could also apply the sort-prune algorithm in a custom osg::Group 
which will mark elements to be deleted instead of directly removing 
them. In the update phase it then could efficiently batch-sort and remove.


Anyways, this all theory as it still unclear what you want to achieve 
with your puzzle. We need more details or a small example to look at. If 
you cannot present the work, try to create a minimal example to 
demonstrate the problem (as a compilable example, so lazy people like me 
will take an actual look at it)


Cheers
Sebastian






Thank you!

Cheers,
Yura

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70724#70724





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] NodeCallback does not traverse children

2017-04-10 Thread Sebastian Messerschmidt




Hi Yura,

Hi,

I have created NodeCallback like in example osggeometry to update 
MatrixTransform of all nodes in a group.
I applied it only for group: group.setUpdateCallback(mycallback);
In operator() of mycallback i am calling traverse(node,nv) but it works only 
for group, not for it children.
What i am doing wrong? Do I need to call setUpdateCallback for every child?


That is expected behavior. The callback is called for the element you 
added it to only. The traverse will simply tell the visitor to go on in 
its traversal so it can find nodes with an update-callback deeper  below 
your elements.
If you need to modify all childs anyways, you can run your own visitor 
from the entry of the callback.


Thank you!

Cheers,
Yura

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70725#70725





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Fast move a lot of nodes to another group




Am 4/4/2017 um 3:53 PM schrieb Yura Ivanov:

Nodes are unique quads with editable geometry. I had no problem with 
performance exept removeChild when i tried to move them into transform matrix.
If you're actually holding all the childs in a single group, the remove 
will become horribly expensive (due to removal somewhere in the vector). 
Try to restructure your group to have a tree-like substructure 
(basically a quad-tree) to have smaller sets to work with.



 I would be nice if osg will have function to move node to another group 
whithout internal std remove and erease.
P.S. Sorry if my english is bad.


Cheers
Sebastian


--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70658#70658





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg Earth




Hi Ramababu,

Hi,Sebastian I added that dll but it is asking some other dlls i added those 
dlls also but again one error i.e ordinal 1338 not located in the dynamic link 
library for dirapi.dll.


You can use the dependency-walker [1] to see what dlls are missing.

[1] http://www.dependencywalker.com





...

Thank you!

Cheers,
Rambabu

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70652#70652





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg Earth


Hi,


Hi, Iam loading the tiff image in osg earth then i got this ERROR 6: Unable to 
load PROJ.4 library (proj.dll), creation of OGRCoordinateTransformation 
failed.How to solve this ?


By reading the error message carefully and putting the appropriate 
proj.dll in the folder ;-)


Cheers
Sebastian



...

Thank you!

Cheers,
Rambabu

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70649#70649





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Fast move a lot of nodes to another group




Hi Yura,

Hi,
I need to move a lot of nodes from Group to MatrixTransform to translate them 
into new position by user input, and then move them back into Group with new 
position. Call addChild and removeChild for each node is slow because of 
removeChild. Also I cant use removeChildren to remove all nodes at once because 
my node list is not continuous.
You could use the replaceChild like this: (assuming node is the Node to 
move and group its current parent)


transform = new MatrixTransform
transform->addChild(node);
group->replaceChild(node, transform);

This way the child list (implemented as a vector) is not changed in size 
for every operation.


Cheers
Sebastian



>



Thank you!

Cheers,
Yura

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=70624#70624





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] wireframe darker wrt the surface color