Re: [osg-users] OSG runtime error on Visual Studio Debug mode

2012-02-15 Thread Ulrich Hertlein
Hi Clement, On 16/02/12 13:59 , clement@csiro.au wrote: > I am using osg version 3.0.1 with MS Visual Studio 2008. My application is > embedded > osg viewer to display sample, so it is not necessary to build my application > with using > debug version of osg. The application build settings

Re: [osg-users] osgvolume opacity settings

2012-02-15 Thread Clement.Chu
Hi Robert, I think my problem is related to AlphaFuncProperty and SampleDensityProperty settings. From your previously explanation for the function AlphaFuncProperty , TransparencyProperty and SampleDensityProperty. - AlphaFuncProperty is equivalent to glAlphaFunc and sets the alpha value be

[osg-users] OSG runtime error on Visual Studio Debug mode

2012-02-15 Thread Clement.Chu
Hi, I am using osg version 3.0.1 with MS Visual Studio 2008. My application is embedded osg viewer to display sample, so it is not necessary to build my application with using debug version of osg. The application build settings is using all non-debug osg libraries even on "Debug" or "Rele

Re: [osg-users] Segmentation fault when I try to assign MatrixD

2012-02-15 Thread Ulrich Hertlein
Hi guys, On 15/02/12 23:52 , Philipp Moeller wrote: >> I have a class (Car) which extends|osg::PositionAttitudeTransform|. >> Now I want to create camera which has the same position. So I get >> car's matrix in Camera's getMatrix() method: >> >> |matrix= car->asMatrixTransform()->getMatrix(); //

Re: [osg-users] Segmentation fault when I try to assign MatrixD

2012-02-15 Thread Scott Wasinger
Just for some clarification are you trying to make a camera that follows your car model? Because I had the similar issue recently and through my research I found I could attach a camera manipulator to a node and the camera will be translated relative to the position of the PositionAttitudeTrans

Re: [osg-users] bug in Imagef::readImageFromCurrentTexture

2012-02-15 Thread Robert Osfield
Hi Alex, I guess this will be something that is rather driver dependant - and why I had spotted this issue with my own usage. Could you modified Image.cpp to get things working for and post the full modified file to osg-submissions. Thanks, Robert. On 15 February 2012 16:35, Pecoraro, Alexander

[osg-users] bug in Imagef::readImageFromCurrentTexture

2012-02-15 Thread Pecoraro, Alexander N
I was trying to use osg::Image::readImageFromCurrentTexture() to read back a texture from the GPU. The glGetTexImage() call was failing because it was using an invalid pixel format. The pixel format that it uses comes from calling osg::Image::computePixelFormat() with the internal format of the

Re: [osg-users] FrameStamp on viewer's GUIEventHandler

2012-02-15 Thread Riccardo Corsi
Hi Robert, cool, I was afraid there was a specific reason not to pass the visitor to those handlers... I've submitted the patch. Also, while checking the event handling related code, let me remind you that some people found in the past that cameras sometimes receive twice the same event: https://

Re: [osg-users] Missing parts of 3rdParty_VC10_x86_x64.zip

2012-02-15 Thread Terry Welsh
Hi Brad, Thank you for the binaries. Now that I have things figured out a little better, I don't see anything additions or changes that need to be made. Everything compiles and runs fine, and, as a bonus, I was able to leave a couple DLLs out of my installer when building with VS2010. -- Terry We

Re: [osg-users] FrameStamp on viewer's GUIEventHandler

2012-02-15 Thread Robert Osfield
HI Riccardo, On 15 February 2012 15:38, Riccardo Corsi wrote: > while checking the code related to event handling, > I've noticed that node callbacks receives a NodeVisitor in their handle() > callback, and can then extract the frameStamp if needed. > > The same does not apply to theĀ GUIEventHand

[osg-users] FrameStamp on viewer's GUIEventHandler

2012-02-15 Thread Riccardo Corsi
Hi All, while checking the code related to event handling, I've noticed that node callbacks receives a NodeVisitor in their handle() callback, and can then extract the frameStamp if needed. The same does not apply to the GUIEventHandler added directly to the osgViewer classes, as thy are invoked

Re: [osg-users] Segmentation fault when I try to assign MatrixD

2012-02-15 Thread Philipp Moeller
Maciej Ciemborowicz writes: > Hello, > > I have a class (Car) which > extends|osg::PositionAttitudeTransform|. Now I want to create camera > which has the same position. So I get car's matrix in Camera's > getMatrix() method: > > |matrix= car->asMatrixTransform()->getMatrix(); // osg::Matrixd* m

[osg-users] Segmentation fault when I try to assign MatrixD

2012-02-15 Thread Maciej Ciemborowicz
Hello, I have a class (Car) which extends|osg::PositionAttitudeTransform|. Now I want to create camera which has the same position. So I get car's matrix in Camera's getMatrix() method: |matrix= car->asMatrixTransform()->getMatrix(); // osg::Matrixd* matrix| At this point I get stack overfl

Re: [osg-users] compileGLObjects problem

2012-02-15 Thread Robert Osfield
Hi Aurelien, On 14 February 2012 22:01, Aurelien Albert wrote: > Is it the same mechanism for StateAttribute ? Yes. > For example, if I create a subclass "MyTexture" of osg::Texture, will > compileGLObjects/releaseGLObjects methods of "MyTexture" be automatically > called when needed ? Yes,