Maybe it can help...
sram...@japc17:~/Bureau/pythonOCC-0.4-samples/Level1/Animation$
LIBGL_DEBUG=verbose python animation.py
Display3d class initialization starting ...
libGL: OpenDriver: trying /usr/lib/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/dri/i965_dri.so
Graphic device creat
Hi guys,
Many thanks for this interesting discussion and your feedbacks. I still have
difficulties to check whether the display issues come from OCC or pythonOCC.
It's hard to compare the behaviour of pythonOCC and Salome since Salome
relies on a patched release of OpenCascade: I checked the OCC6.
Hello Marcos,
well now it is also running at my laptop. I've added the following lines
to the /etc/X11/xorg.conf (if this file is not present, one has to
create it):
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "DRI" "o
Hello Marcos,
and you got the python-occ GUI working from that svn compilation, when
you restart the X-Server before every use?
Well I tried your supposed solution, but I have had no success. To which
"hello.py" script are you referring in your description? If I want to
start the python-occ GUI i
Hi Marcos,
thank's for your input. Can you exactly explain how do you have
deactivated the graphic acceleration? I installed the driconf utility,
and after deactivating the 3D acceleration at the tab Debugging, even
the glxgears app crashed and python-occ was also not able to start. So I
was not y
;> Subject: [Pythonocc-users] python-occ GUI segmentation faults on intel
>> graphic cards
>> To: pythonocc-users@gna.org
>> Message-ID: <4c34b48d.4010...@web.de>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello,
>>
>> a
Hello,
yes glxgears is running without any problems. I've also tested the
following variable:
export LIBGL_ALWAYS_INDIRECT=yes
but that let's my whole desktop crashing, when starting the test python
script.
Best,
Oliver
Am 09.07.2010 10:23, schrieb M. Nawijn:
> Hello All,
>
> I have had some
Hi all,
I'm not sure whether this Intel problem comes from OCC or pythonOCC. I
suspect a part of the initialization code of pythonOCC 0.4 (file
Display3d.cpp) to be not really optimized. After diving into the Salome
source code, I recently committed changes to this file (
http://code.google.com/p/
Hello All,
I have had some problems previously with getting the graphics working
properly (with
NVidia card),
one of the reasons was that after a package update, some of the symbolic links
that link to the proper libGL* classes were set wrong.
Before diving into the problem, can you confirm that
Just checked the OCC forum, but the only comment für WinXP was to use
the mesa libraries. Unfortunately I'm using these libraries already with
Intel graphic cards under kubuntu. Checked the linked libs of
libTKOpenGl-6.3.0.so (as I thought this is the one which makes trouble -
am I right?)
~$ ldd
00
>> From: Oliver Borm
>> Subject: [Pythonocc-users] python-occ GUI segmentation faults on intel
>> graphic cards
>> To: pythonocc-users@gna.org
>> Message-ID: <4c34b48d.4010...@web.de>
>> Content-Type: text/plain; charset="utf-8"
>>
>
El 08-07-2010, a las 6:00, pythonocc-users-requ...@gna.org
> Message: 2
> Date: Wed, 07 Jul 2010 19:08:29 +0200
> From: Oliver Borm
> Subject: [Pythonocc-users] python-occ GUI segmentation faults on intel
> graphic cards
> To: pythonocc-users@gna.org
> Message-ID: <
Hello,
at the moment I have problems to start the python-occ GUI on a laptop
with Intel graphic card, as I get a segmentation fault. Attached you
will find my small test file and the gdb backtrace.
I'm using ubuntu 10.04 and the paython-occ 0.4 debian package from the
CAE-Team PPA. Any suggestion
13 matches
Mail list logo
