Re: [osg-users] DISPLAY ignored by osgViewer?

2007-10-24 Thread Robert Osfield
Hi Paul, You are mis-reading the View::setUpView* code, they all read the display variable and then pass this on to the final GraphicsTraits used to set up the windows. The DISPLAY variable is an X11 variable for controlling where the window will appear. Robert. On 10/24/07, Paul Martz [EMAIL

[osg-users] Resize a shape?

2007-10-24 Thread Patrick Maier
Hi, I'm new to this list and to openscenegraph and I've a question regarding a problem and I don't know how to solve it. It should be really trivial, but I don't get it managed, and google or other searches could not help me. I've a cylinder, and while showing the scene, I want to change the

Re: [osg-users] osgviewerWX race condition.

2007-10-24 Thread Alberto Luaces
Hi Jose Luis, no problems here about the binary cow nor crashes are showing: $ set | grep LANG LANG=es_ES.UTF-8 $ uname -a Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 GNU/Linux Debian Lenny, OSG from today's SVN. nvidia geforce 7600, (100.14.11) Alberto El Wednesday 24

Re: [osg-users] Texture subloading

2007-10-24 Thread Robert Osfield
On 10/24/07, Sewell, Kenneth R Civ USAF AFRL/RYZW [EMAIL PROTECTED] wrote: I thought OSG provided a call to glTexSubImage2D, similar to how it handles glTexSubImage3D. I've since figured out that I just have to use the regular OpenGL calls in the load and subload routines. So the subloading

[osg-users] OSG-2.2 osgViewer-frame() access violation

2007-10-24 Thread Yanling Liu
Hello, don't know whether this has been reported or not. In OSG-2.2, osgViewer-frame() get access violation if there is no data in scene (didn't call setSceneData()). This doesn't happen in OSG-2.0. Do I must give something to osgViewer, even an empty Geode, before I can call osgViewer-frame()?

Re: [osg-users] OSG-2.2 osgViewer-frame() access violation

2007-10-24 Thread Robert Osfield
Hi Yanling, The is a bug that clearly needs fixing. Until its fixed addding a empty node to the scene may well work ok. Robert. On 10/24/07, Yanling Liu [EMAIL PROTECTED] wrote: Hello, don't know whether this has been reported or not. In OSG-2.2, osgViewer-frame() get access violation if

Re: [osg-users] Debugging Warning: detected OpenGL error 'invalid value' after RenderBin::draw(, )

2007-10-24 Thread beelzebob999-osg
We we're getting a lot of this error message as well. In our case, it turned out we were telling opengl to draw a line with a width of 0. - Original Message From: Jean-Sébastien Guay [EMAIL PROTECTED] To: osg-users@lists.openscenegraph.org Sent: Wednesday, October 24, 2007 2:59:44 PM

Re: [osg-users] Debugging Warning: detected OpenGL error 'invalid value' after RenderBin::draw(, )

2007-10-24 Thread Michael Henheffer
Hi J-S, I think calling the following might be what you are looking for to narrow down the source of your error. pState-setCheckForGLErrors (osg::State::CheckForGLErrors::ONCE_PER_ATTRIBUTE) where pState is a pointer to the osg::State. Hope this helps, Mike Jean-Sébastien Guay wrote:

Re: [osg-users] Debugging Warning: detected OpenGL error 'invalid value' after RenderBin::draw(, )

2007-10-24 Thread Cole, Charles E. (LARC-B702)[GENEX SYSTEMS]
This was Robert's response to a similar situation: --- Its likely that some OpenGL state you are setting isn't supported on your hardware. The big question is what OpenGL features are causing this problem. You could enable finer grained checking for OpenGL errros via

[osg-users] osgViewerMFC Resize Issue

2007-10-24 Thread Donald Cipperly
I found a small error in calculating the x mouse location after resizing the render window in the osgViewerMFC example. I've traced this back in the debugger to osgViewer::Viewer::eventTraversal(). Line 550 in this file has the correct value: float x = event-getX(); However, the calculations

[osg-users] Texturing w/ osg::Image

2007-10-24 Thread Shawn Cook
Hi Jean, Ugh, the code that I pasted was just tainted with something I was trying. I have indeed tried that code with GL_TEXTURE_2D in every place where it ought to be and get the same result: a blank, white square with no texture. Am I using the osg::Image-data() function incorrectly?

Re: [osg-users] Debugging Warning: detected OpenGL error 'invalid value' after RenderBin::draw(, )

2007-10-24 Thread Jean-Sébastien Guay
Hello Joel, We received this error message whenever our thread tried to update the state of a node while the drawing thread was trying to render it. Adding a mutex solved our issue. Hmmm, I'm doing this in the update traversal, so I should be ok on that front... But maybe I'll test it out

Re: [osg-users] Debugging Warning: detected OpenGL error 'invalid value' after RenderBin::draw(, )

2007-10-24 Thread Jean-Sébastien Guay
Hello again, We received this error message whenever our thread tried to update the state of a node while the drawing thread was trying to render it. Adding a mutex solved our issue. Hmmm, I'm doing this in the update traversal, so I should be ok on that front... But maybe I'll test it out

[osg-users] Is antialising supported by OSG?

2007-10-24 Thread Yi Wang
Is antialising or point/line/polygon smoothing supported in OSG? I did not find any implementation for ANTIALIS StateAttribute type in the code. Can anyone tell me know how to do it? Call gl functions before the draw traversal in the main loop? Thanks. yi

Re: [osg-users] Collada Plugin DAE build errors

2007-10-24 Thread Hamm, Brandon
Wojtek, This worked beautifully, with one very minor exception: The correct preprocessor definition is DOM_DYNAMIC (see reference below): http://www.collada.org/mediawiki/index.php/DOM_guide:_Setting_up#Linking_with_the_dynamic_COLLADA_DOM_library Thank you so much for this! Brandon Hamm