[vtkusers] SuSe7.0_VTK3.2
Karshi Hasanov
karshi.hasanov at utoronto.ca
Wed Aug 1 13:38:51 EDT 2001
On SuSe 7.0, I did "./confige --with-opengl" instead of " --with-mesa", and
it worked for me. May be you should try it?
---------- Forwarded Message ----------
Subject: vtkusers digest, Vol 1 #503 - 8 msgs
Date: Wed, 1 Aug 2001 12:00:07 -0400
From: vtkusers-admin at public.kitware.com
To: vtkusers at public.kitware.com
Send vtkusers mailing list submissions to
vtkusers at public.kitware.com
To subscribe or unsubscribe via the web, visit
http://public.kitware.com/mailman/listinfo/vtkusers
or, via email, send a message with subject or body 'help' to
vtkusers-request at public.kitware.com
You can reach the person managing the list at
vtkusers-admin at public.kitware.com
When replying, please edit your Subject line so it is more specific than
"Re: Contents of vtkusers digest..."
Today's Topics:
1. VRMLExporter bug? (sacha.jp at pg.com)
2. MRI Tiff stacks (Maneesh Yadav)
3. Large Image rendered white? (Robert Mitchell)
4. Re: Large Image rendered white? (John Biddiscombe)
5. Fps in VTK (Christophe ATTANASIO (cai))
6. Re: Fps in VTK (Schaap, J.A. (LKEB))
7. Problems on SuSE7.0 and VTK3.2 (Rene Hommel)
8. Stereo on an ONYX3400 (A. Meijster)
--__--__--
Message: 1
From: sacha.jp at pg.com
To: vtkusers at public.kitware.com
Date: Tue, 31 Jul 2001 17:16:09 -0400
Subject: [vtkusers] VRMLExporter bug?
Looks that VRMLExporter creates incorrect view point while saving VRML files.
When the generated file is loaded into Cosmo Player the scene is typically
somewhere off the screen. It takes some "blind" rotation and zooming before
it shows in the field of view.
Is there some way around it?
Jarek
--__--__--
Message: 2
Date: Tue, 31 Jul 2001 17:58:03 -0400 (EDT)
From: Maneesh Yadav <97yadavm at utsc.utoronto.ca>
To: <vtkusers at public.kitware.com>
Subject: [vtkusers] MRI Tiff stacks
Hi all,
Many moons ago I was trying to write some molecular viz stuff in vtk but
it never turned out (not so much vtk's fault as it was sort of underlying
molecular semantics that frusturated me)
Anyhoo I'm back to vtk as I have some mouse embryo MRI data that I'd like
to visualize and
I've been given a tiff stack, which I really not sure how to process (is
it just a concatenated set of tiff files?). I think Sebastien Barre's
tutorial provides me with most of the other help I'll need.
Any other advice from people who have done this sort of thing would be
appreciated.
Many Thanks,
Maneesh Yadav
--__--__--
Message: 3
Date: Wed, 01 Aug 2001 12:03:33 +1000
From: Robert Mitchell <robmitch at eng.uts.edu.au>
Organization: University of Technology, Sydney
To: VTK USERS <vtkusers at public.kitware.com>
Subject: [vtkusers] Large Image rendered white?
Dear Users,
I am reading in a large (10MB) Bitmap (vtkBMPReader) and rendering it
with a vtkImageActor having been passed through vtkImageLuminance (see
previous message re:Dynamic Pipeline changes). The problem is that the
whole image is rendered completely white, although when I clip the data
and only render the clipped extent, it does it properly. Is there some
limit on the size of the extent to render properly, or is there some
caching things that need to be attended to?
Cheers,
Rob
--
Robert Mitchell
Faculty of Engineering
University of Technology, Sydney
+61 2 9514 2317
--__--__--
Message: 4
Date: Wed, 01 Aug 2001 03:33:25 +0100
To: Robert Mitchell <robmitch at eng.uts.edu.au>,
VTK USERS <vtkusers at public.kitware.com>
From: John Biddiscombe <jbiddiscombe at skippingmouse.co.uk>
Subject: Re: [vtkusers] Large Image rendered white?
glGetIntegerv(GL_MAX_TEXTURE_SIZE, ¶ms);
if your bitmap is bigger than this, then it won't be displayed correctly
JB
At 03:03 01/08/2001, Robert Mitchell wrote:
>Dear Users,
>
>I am reading in a large (10MB) Bitmap (vtkBMPReader) and rendering it
>with a vtkImageActor having been passed through vtkImageLuminance (see
>previous message re:Dynamic Pipeline changes). The problem is that the
>whole image is rendered completely white, although when I clip the data
>and only render the clipped extent, it does it properly. Is there some
>limit on the size of the extent to render properly, or is there some
>caching things that need to be attended to?
>Cheers,
>Rob
>
>--
>Robert Mitchell
>Faculty of Engineering
>University of Technology, Sydney
>+61 2 9514 2317
>
>
>
>_______________________________________________
>This is the private VTK discussion list.
>Please keep messages on-topic. Check the FAQ at:
><http://public.kitware.com/cgi-bin/vtkfaq>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/vtkusers
--__--__--
Message: 5
Date: Wed, 01 Aug 2001 14:04:35 +0200
From: "Christophe ATTANASIO (cai)" <c-attanasio at paris1.matra-dtv.fr>
To: vtkusers at public.kitware.com
Subject: [vtkusers] Fps in VTK
Hello all,
Is there a way to display dynamically the fps (frame per seconds) in a
VTK viewer ?
I use a vtkRenderWindowInteractor to display large STL mesh.
Thanks for your help
Christophe.
--
Christophe ATTANASIO
Open CASCADE
email : c-attanasio at opencascade.com
http://www.opencascade.com
Open CASCADE, the Open Source Standard for 3D modeling solutions
--__--__--
Message: 6
From: "Schaap, J.A. (LKEB)" <J.A.Schaap at lumc.nl>
To: Christophe ATTANASIO <c-attanasio at paris1.matra-dtv.fr>,
vtkusers at public.kitware.com
Date: Wed, 01 Aug 2001 14:15:09 +0200
Subject: Re: [vtkusers] Fps in VTK
vtkRenderer::GetLastRenderTimeInSeconds ()
1-8-2001 14:04:35, "Christophe ATTANASIO (cai)"
<c-attanasio at paris1.matra-dtv.fr> wrote:
>Hello all,
>
>Is there a way to display dynamically the fps (frame per seconds) in a
>VTK viewer ?
>I use a vtkRenderWindowInteractor to display large STL mesh.
>
>Thanks for your help
>Christophe.
>
>--
>Christophe ATTANASIO
>Open CASCADE
>email : c-attanasio at opencascade.com
>http://www.opencascade.com
>Open CASCADE, the Open Source Standard for 3D modeling solutions
>
>
>
>_______________________________________________
>This is the private VTK discussion list.
>Please keep messages on-topic. Check the FAQ at:
> <http://public.kitware.com/cgi-bin/vtkfaq> Follow this link to
> subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/vtkusers
--__--__--
Message: 7
Date: Wed, 01 Aug 2001 14:54:07 +0200
From: Rene Hommel <rene.hommel at addcom.de>
Reply-To: rene.hommel at addcom.de
To: vtkusers <vtkusers at public.kitware.com>
Subject: [vtkusers] Problems on SuSE7.0 and VTK3.2
VTK3.2 compile problems on SuSE7.0:
Configuration:
./configure --with-shared --with-contrib --with-tcl --with-tkwidget
--with-mesa --with-python
System:
gpp-2.95.2
libc-2.1.3
mesa-3.2-41 (incl. mesadev)
tcl-8.3.1 (incl. header files)
python-1.5.2
My user.make:
TCL_INCLUDE=-I/usr/include
TCL_LIB=/usr/lib/libtcl8.3.so
TK_INCLUDE=-I/usr/include
TK_LIB=/usr/lib/libtk8.3.so
MESA_INCLUDE=-I/usr/include/GL
MESA_LIB=/usr/lib/libMesaGL.so
PYTHON_INCLUDES=-I/usr/include/python
Error message:
make[1]: Leaving directory `/opt/PAKETE/VTK-3.2/vtk3.2/contrib'
cd tcl; make - vtk
make[1]: Entering directory `/opt/PAKETE/VTK-3.2/vtk3.2/tcl'
c++ -g -O2 -fPIC -I. -I./../common -I../common -I/usr/include
-I/usr/include -I/usr/include/GL -I/usr/X11R6/include -I./../graphics
-DVTK_USE_GRAPHICS -I./../imaging -DVTK_USE_IMAGING -I./../contrib
-DVTK_USE_CONTRIB -c -o tkAppInit.o ./tkAppInit.cxx
c++ -o vtk tkAppInit.o \
-L. -g -O2 -fPIC -I. -I./../common -I../common -I/usr/include
-I/usr/include -I/usr/include/GL -I/usr/X11R6/include -I./../graphics
-DVTK_USE_GRAPHICS -I./../imaging -DVTK_USE_IMAGING -I./../contrib
-DVTK_USE_CONTRIB -rdynamic -L/opt/PAKETE/VTK-3.2/vtk3.2/contrib
-lVTKContribTcl -lVTKContrib -L/opt/PAKETE/VTK-3.2/vtk3.2/imaging
-lVTKImagingTcl -lVTKImaging -L/opt/PAKETE/VTK-3.2/vtk3.2/graphics
-lVTKGraphicsTcl -lVTKGraphics -L../common -lVTKCommonTcl -lVTKCommon
-L/usr/X11R6/lib /usr/lib/libMesaGL.so /usr/lib/libtk8.3.so
/usr/lib/libtcl8.3.so -ldl -lpthread \
-L/usr/X11R6/lib -lXext -lXt -lSM -lICE -lX11 -lm
/opt/PAKETE/VTK-3.2/vtk3.2/imaging/libVTKImaging.so: undefined reference
to `OSMesaMakeCurrent'
/opt/PAKETE/VTK-3.2/vtk3.2/imaging/libVTKImaging.so: undefined reference
to `OSMesaCreateContext'
/opt/PAKETE/VTK-3.2/vtk3.2/imaging/libVTKImaging.so: undefined reference
to `OSMesaDestroyContext'
collect2: ld returned 1 exit status
make[1]: *** [vtk] Error 1
make[1]: Leaving directory `/opt/PAKETE/VTK-3.2/vtk3.2/tcl'
make: *** [build_tcl] Error 2
I guess: `OSMesaMakeCurrent' o.s.o. are in /usr/include/GL/osmesa.h
#ll /usr/include/GL
-rw-r--r-- 1 root root 77761 Jul 29 2000 gl.h
-rw-r--r-- 1 root root 21360 Jul 29 2000 gl_mangle.h
-rw-r--r-- 1 root root 15441 Jul 29 2000 glu.h
-rw-r--r-- 1 root root 3335 Jul 29 2000 glu_mangle.h
-rw-r--r-- 1 root root 29986 Jul 29 2000 glut.h
-rw-r--r-- 1 root root 4113 Jul 29 2000 glutf90.h
-rw-r--r-- 1 root root 5827 Jul 29 2000 glx.h
-rw-r--r-- 1 root root 2464 Jul 29 2000 glx_mangle.h
-rw-r--r-- 1 root root 7358 Jul 29 2000 osmesa.h
-rw-r--r-- 1 root root 9281 Jul 29 2000 xmesa.h
-rw-r--r-- 1 root root 3593 Jul 29 2000 xmesa_x.h
-rw-r--r-- 1 root root 6056 Jul 29 2000 xmesa_xf86.h
Where is the Problem? More configuration details on request! Please
help!
Regards,
Rene Hommel
--__--__--
Message: 8
Date: Wed, 01 Aug 2001 18:05:08 +0200
From: "A. Meijster" <A.Meijster at rc.rug.nl>
Organization: Center for High-Performance Computing and Visualization
To: vtkusers at public.kitware.com
Subject: [vtkusers] Stereo on an ONYX3400
Hi All,
We have a brand new ONYX 3400 with shutter glasses. We
are able to run several 3D stereo demo's from SGI, and were also
able to compile some on stereo glut programs.
Now my problem. I compiled VTK for this machine,
and tried to use the stereo capabilities by simply
pressing '3' in the render window. Then the system
replies (on stderr) that the system has
not Crystal glasses capabilities. In my view this should
be working on an ONYX, since GL-stereo is obviously
supported. Anyone got this working?
Cheers,
Arnold Meijster (a.meijster at rc.rug.nl)
--__--__--
_______________________________________________
vtkusers mailing list
vtkusers at public.kitware.com
http://public.kitware.com/mailman/listinfo/vtkusers
End of vtkusers Digest
-------------------------------------------------------
More information about the vtkusers
mailing list