Re: [osg-users] VPB stuff

2009-05-21 Thread Mao
Thank all of you for the helpful answer! From: Mao [mailto:sherlock...@gmail.com] Sent: Friday, May 15, 2009 11:09 AM To: 'osg-users@lists.openscenegraph.org' Subject: VPB stuff Hi! Recently, our project is planning to migrate from mini to VPB. However, we encounter with several

Re: [osg-users] VPB stuff

2009-05-15 Thread J.P. Delport
Hi, Mao wrote: Hi! Recently, our project is planning to migrate from mini to VPB. However, we encounter with several questions. 1. In the example of osgDEM, I infer that osgDEM processes tiff format only. But tiff uses 32-bit offset which limits its size to 4G bytes. Most of our

Re: [osg-users] VPB stuff

2009-05-15 Thread Pierre Bourdin (gmail)
Hi, I can confirm it works well with many textures... Here's screenshot of some terrain build with 2 textures: http://perso.imerir.com/bourdin/wiki/doku.php/en/projet/massane The only problem I have is with Shapefile, but I'm using osggis for that... If you know how to use them with osgdem ?

Re: [osg-users] VPB stuff

2009-05-15 Thread J.P. Delport
Hi, Pierre Bourdin (gmail) wrote: Hi, I can confirm it works well with many textures... Here's screenshot of some terrain build with 2 textures: http://perso.imerir.com/bourdin/wiki/doku.php/en/projet/massane The only problem I have is with Shapefile, but I'm using osggis for that... If you

Re: [osg-users] VPB stuff

2009-05-15 Thread Robert Osfield
HI Pierre, On Fri, May 15, 2009 at 8:24 AM, Pierre Bourdin (gmail) pierre.bour...@imerir.com wrote: For the --terrain option, it works also very well, but I have to disable GL_ARB extension with my ATI otherwise it crashes. Could you try the OSG-2.8 or svn/trunk version of the OSG as there is

Re: [osg-users] VPB stuff

2009-05-15 Thread Robert Osfield
Hi Mao, On Fri, May 15, 2009 at 4:09 AM, Mao sherlock...@gmail.com wrote: 3.   The last question is when applied with “--Terrain” or “—HEIGHT_FIELD” options, there is no texture at all. Can we encapsulate both texture and DEM data into one output file? And it seems that osg::HeightField

Re: [osg-users] VPB stuff

2009-05-15 Thread Pierre Bourdin (gmail)
Hi Robert, is it the expected comportement ? log machine=DELL-VOSTRO-02 running task=tasks/build_subtile_L2_X3_Y1/build_subtile_L5_X31_Y14.task Error: :0.0 no Pbuffer support in GLX available. libGL error: drmGetMagic failed libGL error: reverting to (slow) indirect rendering Warning: detected

Re: [osg-users] VPB stuff

2009-05-15 Thread Robert Osfield
Hi Pierre, You are getting an OpenGL related error which clearly isn't good as is something you need to look at. What hardware + drivers are you using? Robert. On Fri, May 15, 2009 at 1:43 PM, Pierre Bourdin (gmail) pierre.bour...@imerir.com wrote: Hi Robert, is it the expected comportement

Re: [osg-users] VPB stuff

2009-05-15 Thread Pierre Bourdin (gmail)
Hi Robert, Le vendredi 15 mai 2009 à 13:51 +0100, Robert Osfield a écrit : Hi Pierre, You are getting an OpenGL related error which clearly isn't good as is something you need to look at. Yep ,but the terrain is built and rendering is slow and popping but correct... What hardware +

Re: [osg-users] VPB stuff

2009-05-15 Thread Robert Osfield
Hi Pierre, I'm currently using a ATI 4670 graphics card under Kubuntu 9.04 and osgdem/vpb has been working fine for me. fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Radeon HD 4670 OpenGL version string: 2.1.8591 Robert. On Fri, May

[osg-users] VPB stuff

2009-05-14 Thread Mao
Hi! Recently, our project is planning to migrate from mini to VPB. However, we encounter with several questions. 1. In the example of osgDEM, I infer that osgDEM processes tiff format only. But tiff uses 32-bit offset which limits its size to 4G bytes. Most of our data are ERDAS img

Re: [osg-users] VPB stuff

2009-05-14 Thread Chris 'Xenon' Hanson
Mao wrote: 1. In the example of osgDEM, I infer that osgDEM processes tiff format only. Are you talking about for image drapes? osgDEM supports many formats for images and DEMs. But tiff uses 32-bit offset which limits its size to 4G bytes. Most of our data are ERDAS img file or rrd