Re: [osg-users] Has anyone tried 64-bit SUSE enterprise

2007-08-19 Thread Robert Osfield
Hi Brede,

Does the onscreen help cause the same performance slow down, or is it
just stats.  The difference being that help is static text, and stats
is being dynamically update.  The cost should be pretty negligible
though - the stats scene graph is trivial in size.

With the stats I have found that text is relatively slow to update,
suggesting a need for a rewrite of osgText further down the line,
but.. the currently implementation should not go leaking like you have
found, this suggest another problem all togther.

Robert.

On 8/18/07, Brede Johansen [EMAIL PROTECTED] wrote:
 Jan and Robert,

 This happens with the latest ForceWare release 162.18.
 osgviewer from SVN.
 I have two screens attached to a 8800GTX and one screen attached to a
 8600GS.  I know the GS isn't the best but I had  a spare slot  and a  spare
 screen so I had to try. The CPU is a Core 2 Duo.

 Brede



 On 8/18/07, Jan Ciger [EMAIL PROTECTED] wrote:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1
 
  Brede Johansen wrote:
   Hi Jan,
  
   The framerate continues to drop so if it starts at 60Hz it slowly drops
 and
   reaches 30Hz after aproximatly 20 seconds.  It is not a one time drop
 due to
   the HUD.  This happens in SingleThreaded mode with a very simple model.
  
   Brede
  
 
  If this is happening with a standalone viewer, then this indeed looks
  like a driver bug. I do not see this behaviour on a GeForce nor ATI
  hardware.
 
  Jan
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.7 (GNU/Linux)
  Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
 
 
 iD8DBQFGxylsn11XseNj94gRAu7vAJ9yASBA0Nfy1YV30Cdou9w2RmcbogCg6wq/
  Y4cDyO3QqkydYX/uLkqXQm0=
  =p5qa
  -END PGP SIGNATURE-
  ___
  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


Re: [osg-users] ECW Image Files - Secret Tricks?

2007-08-19 Thread Nick Prudent

Antoine,

So how do I make sure that the osgdb_ecw.dll plug-in gets called instead of 
GDAL? As it is, osgDem just stops (crashes actually...). I am not looking 
foward to recompiling GDAL ;(


- Nick -


I meant that OSG plugins are called in sequence, each plugin is trying
to load the file and returns either an image handler or an error code.
The way the GDAL plugin is trying to read a file is to open a GDAL
dataset from this file. If it fails the operation returns a null pointer
to the plugin but also displays an ERROR 4 message. Then the plugin is
returning an error code. If later on an other plugin is able to open
this file, you do not need to care much about the GDAL error.

Recompiling GDAL with ECW support would also work but would make the ECW
plugin useless.
 (PS: Peut-etre pouvez-vous m'expliquer en francais. Merci pour le coup 
de

 pouce.)

De rien, c'est normal pour un membre du Petit Poucet.

Antoine

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


_
Former Police Officer Paul Gillespie’s TAKE BACK THE INTERNET tips and 
tricks, watch the video now  http://safety.sympatico.msn.ca/


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


Re: [osg-users] osgViewer + Fox Toolkit example

2007-08-19 Thread Markus Hein
Robert Osfield schrieb:

 BTW, the example runs fine under Linux, but on segfaults.  Do others
 see this issue?

Hi all,

why I'm forced to run the Viewer SingleThreaded with current OSG from SVN ?

when I tested the FOX-Viewer code for the first time, I used the OSG-2.0 
Release code. There was no problems.
The last days I updated the system , using the current OSG-SVN code 
(Core2Dual,Win32, Nvidia Driver 162.18) , but this time I was forced to 
set the Viewer Mode to SingleThreaded. Else it would crash in a 
threading issue, difficult for me to track down.

I have no multicore CPU running Linux here, so I need to ask other users 
if they have seen the same Problems  in the last time on Linux too ?

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


[osg-users] Text - SCREEN_COORDS

2007-08-19 Thread mprosicky
Hi,
I would like to display text with constant size in pixels, so I have
used CharacterSizeMode as in the simple code sample below:

/ code start
#include osg/ref_ptr
#include iostream
#include osg/Geode
#include osgText/Text
#include osgText/Font
#include osgViewer/Viewer

osg::ref_ptrosg::Node createSceneGraph() {
//this create geode with text C++
osg::ref_ptrosg::Geode textGeode = new osg::Geode;
osg::ref_ptrosgText::Font font = osgText::readFontFile(fonts/arial.ttf);

osg::ref_ptrosgText::Text text = new osgText::Text;
text-setFont(font.get());
text-setFontResolution(256,256);
text-setText(C++);
text-setAxisAlignment(osgText::Text::SCREEN);
text-setCharacterSize(500);

//this is the problem
text-setCharacterSizeMode(osgText::Text::SCREEN_COORDS);

textGeode-addDrawable(text.get());
return textGeode.get();
}

int main(int, char **) {
osg::ref_ptrosg::Node root = createSceneGraph();
osgViewer::Viewer viewer;
viewer.setUpViewInWindow(0,0,1000,300);
viewer.setSceneData(root.get());
return viewer.run();
}
/ code end

But the problem is that the text is contracted. It has right proportion
only when I use squere window. I could see the same efect also with
the osgtext example (more clearly if you use higher aspect ratio window).
I am using widescreen display but it should be no problem.
Did I forgot something or is it standart behaviour when using SCREEN_COORDS?
And also the real text size is not what I requested (500 pixels).

Here is image of the sample window:
http://www.cotopaxi.cz/m/text.jpg

Thank you,

Martin

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


Re: [osg-users] ECW Image Files - Secret Tricks?

2007-08-19 Thread Jason Beverage
Hi Nick,
I think there is a misunderstanding of how osgdem works.  The OSG
readImageFile method, which invokes the plugins you are talking about, is
not used in osgdem/VPB currently: it uses the GDAL library directly.  I
don't want you all to go down the wrong path trying to tweak OSG plugins
that will have no effect.

As far as recompiling GDAL to get ECW support, I would suggest trying to
download the binary releases of GDAL included in the FWTools package (
http://fwtools.maptools.org/).  The sight is down this morning, but should
be back up at some point.  It has almost all the optional plugins built for
you and I'm pretty sure ECW is supported out of the box with those
libraries.

Thanks!

Jason

On 8/19/07, Antoine Hue [EMAIL PROTECTED] wrote:

 Nick Prudent wrote:
  Antoine,
 
  So how do I make sure that the osgdb_ecw.dll plug-in gets called
  instead of GDAL? As it is, osgDem just stops (crashes actually...). I
  am not looking foward to recompiling GDAL ;(
 
 You may get debug messages from OSG setting in environment
 OSGNOTIFYLEVEL=DEBUG_INFO
 or setting it directly in your app:

 #include osg/Notify
 ...

 osg::setNotifyLevel(osg::DEBUG_INFO);

 This will list all tried plugins. A lot of text to analyse but the only
 way to verify that the ECW plugin is in the list.


 Antoine

 ___
 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] osgViewer + Fox Toolkit example

2007-08-19 Thread Robert Osfield
Hi Markus,

On 8/19/07, Markus Hein [EMAIL PROTECTED] wrote:
 Robert Osfield schrieb:
 why I'm forced to run the Viewer SingleThreaded with current OSG from SVN ?

Which viewer are we talking about here?  What do you mean by forced to
run the Viewer SingleThreaded?

 when I tested the FOX-Viewer code for the first time, I used the OSG-2.0
 Release code. There was no problems.
 The last days I updated the system , using the current OSG-SVN code
 (Core2Dual,Win32, Nvidia Driver 162.18) , but this time I was forced to
 set the Viewer Mode to SingleThreaded. Else it would crash in a
 threading issue, difficult for me to track down.

I don't know if the FOX viewer was ever thread safe.  It runs just
fine on my machine, running SingleThreaded, but still hangs on exit.

I don't know how you the threading model to something other than
SingleThreaded, as there is threading model event handler registered.

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


Re: [osg-users] running vrml plugin on 2.0

2007-08-19 Thread Jan Ciger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello Robert,

I have new information regarding the hangs. I have finally managed to
get my gdb to produce a meaningful backtrace when the viewer hangs and
this is the result.

For DrawThreadPerContext, it is blocked at:

Thread 1:
#0  0xb7f507f2 in _dl_sysinfo_int80 () at rtld.c:788
#1  0xb7a83206 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/libpthread.so.0
#2  0xb7ab50a8 in OpenThreads::Condition::wait (this=0x8128d88,
mutex=0x8128d80) at
/media/backup/osg/OpenSceneGraph/src/OpenThreads/pthreads/PThreadCondition.c++:130
#3  0xb7b3ac91 in osgViewer::Viewer::renderingTraversals
(this=0xbfdb968c) at
/media/backup/osg/OpenSceneGraph/include/OpenThreads/Block:133
#4  0xb7b3b9e3 in osgViewer::Viewer::frame (this=0xbfdb968c,
simulationTime=1.7976931348623157e+308) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Viewer.cpp:983
#5  0xb7b3bb3a in osgViewer::Viewer::run (this=0xbfdb968c) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Viewer.cpp:195
#6  0x0804b069 in main (argc=Cannot access memory at address 0x0
) at
/media/backup/osg/OpenSceneGraph/applications/osgviewer/osgviewer.cpp:148

Thread 2:
#0  0xb7f507f2 in _dl_sysinfo_int80 () at rtld.c:788
#1  0xb7a8591e in __lll_mutex_lock_wait () from /lib/i686/libpthread.so.0
#2  0xb7a8184e in _L_mutex_lock_80 () from /lib/i686/libpthread.so.0
#3  0xb7a8139d in pthread_mutex_lock () from /lib/i686/libpthread.so.0
#4  0xb7ab5273 in OpenThreads::Mutex::lock (this=0x8058f74) at
/media/backup/osg/OpenSceneGraph/src/OpenThreads/pthreads/PThreadMutex.c++:122
#5  0xb7b1a52e in osgViewer::Renderer::draw (this=0x8058f20) at
/media/backup/osg/OpenSceneGraph/include/OpenThreads/ScopedLock:31
#6  0xb7b1af58 in osgViewer::Renderer::operator() (this=0xfe00,
context=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Renderer.cpp:548
#7  0xb7e4d45f in osg::GraphicsContext::runOperations (this=0x812dd70)
at /media/backup/osg/OpenSceneGraph/src/osg/GraphicsContext.cpp:654
#8  0xb7e538dd in osg::RunOperations::operator() (this=0x8129278,
context=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osg/GraphicsThread.cpp:134
#9  0xb7e53947 in osg::GraphicsOperation::operator() (this=0x8129278,
object=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osg/GraphicsThread.cpp:50
#10 0xb7e7c627 in osg::OperationThread::run (this=0x8128f78) at
/media/backup/osg/OpenSceneGraph/src/osg/OperationThread.cpp:413
#11 0xb7e53a89 in osg::GraphicsThread::run (this=0x8128f78) at
/media/backup/osg/OpenSceneGraph/src/osg/GraphicsThread.cpp:38
#12 0xb7ab47e4 in OpenThreads::ThreadPrivateActions::StartThread
(data=0x8128f88) at
/media/backup/osg/OpenSceneGraph/src/OpenThreads/pthreads/PThread.c++:158
#13 0xb7a7f462 in start_thread () from /lib/i686/libpthread.so.0
#14 0xb769c82e in clone () from /lib/i686/libc.so.6


For CullThreaPerCameraDrawThreadPerContext I get the hang in:
Thread 1:
#0  0xb7f807f2 in _dl_sysinfo_int80 () at rtld.c:788
#1  0xb7ab3206 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/libpthread.so.0
#2  0xb7ae50a8 in OpenThreads::Condition::wait (this=0x8128d88,
mutex=0x8128d80) at
/media/backup/osg/OpenSceneGraph/src/OpenThreads/pthreads/PThreadCondition.c++:130
#3  0xb7b6ac91 in osgViewer::Viewer::renderingTraversals
(this=0xbfc66d0c) at
/media/backup/osg/OpenSceneGraph/include/OpenThreads/Block:133
#4  0xb7b6b9e3 in osgViewer::Viewer::frame (this=0xbfc66d0c,
simulationTime=1.7976931348623157e+308) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Viewer.cpp:983
#5  0xb7b6bb3a in osgViewer::Viewer::run (this=0xbfc66d0c) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Viewer.cpp:195
#6  0x0804b069 in main (argc=Cannot access memory at address 0x0
) at
/media/backup/osg/OpenSceneGraph/applications/osgviewer/osgviewer.cpp:148

Thread 2:
#0  0xb7f807f2 in _dl_sysinfo_int80 () at rtld.c:788
#1  0xb7ab591e in __lll_mutex_lock_wait () from /lib/i686/libpthread.so.0
#2  0xb7ab184e in _L_mutex_lock_80 () from /lib/i686/libpthread.so.0
#3  0xb7ab139d in pthread_mutex_lock () from /lib/i686/libpthread.so.0
#4  0xb7ae5273 in OpenThreads::Mutex::lock (this=0x8058f6c) at
/media/backup/osg/OpenSceneGraph/src/OpenThreads/pthreads/PThreadMutex.c++:122
#5  0xb7b4a52e in osgViewer::Renderer::draw (this=0x8058f20) at
/media/backup/osg/OpenSceneGraph/include/OpenThreads/ScopedLock:31
#6  0xb7b4af58 in osgViewer::Renderer::operator() (this=0xfe00,
context=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osgViewer/Renderer.cpp:548
#7  0xb7e7d45f in osg::GraphicsContext::runOperations (this=0x812dd70)
at /media/backup/osg/OpenSceneGraph/src/osg/GraphicsContext.cpp:654
#8  0xb7e838dd in osg::RunOperations::operator() (this=0x8129278,
context=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osg/GraphicsThread.cpp:134
#9  0xb7e83947 in osg::GraphicsOperation::operator() (this=0x8129278,
object=0x812dd70) at
/media/backup/osg/OpenSceneGraph/src/osg/GraphicsThread.cpp:50
#10 0xb7eac627 in osg::OperationThread::run 

Re: [osg-users] osgDEM layers and CoordinateSystemNode (Robert Osfield)

2007-08-19 Thread Gert van Maren
Hi Robert,

 The VPB state seems appropriate to me, I'm not sure what else need to be  
 added.

I know it works but performance over the internet is just not really  
anything like GE (OSG1.2). Maybe 2.x is faster... maybe it is our web  
server...

I saw there was a discussion about speeding up the net plugin about 8  
months ago and the answer was to wait for a complete multi threaded  
database pager?

Regards,

Gert.

-- 
Gert van Maren

Head of Research  Development
K2Vi Virtual Reality Software
Data Interface Technologies Ltd

Phone: +64 21 2855581
Email: [EMAIL PROTECTED]
Web: http://www.k2vi.com

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