Hi Thomas.
I think that I this might be an issue of display adapter driver. I'll check
this first and give you an update.
On Tue, Oct 22, 2013 at 2:28 PM, Thomas Holder <
spel...@users.sourceforge.net> wrote:
> Hi Yotam,
>
> you are welcome to send me your file, then I'll have a look.
>
> Chee
Hi Yotam,
you are welcome to send me your file, then I'll have a look.
Cheers,
Thomas
On Oct 22, 2013, at 5:52 AM, Yotam Avital wrote:
> Hi Thomas.
>
> Thanks for the quick replay. I installed the svn version of pymol with the
> same result. I know that 6000 atoms isn't much for this task
Hi Thomas.
Thanks for the quick replay. I installed the svn version of pymol with the
same result. I know that 6000 atoms isn't much for this task and this
baffle me. Is there a way for me to de-bug this? Perhaps my input file is
faulty.
On Tue, Oct 22, 2013 at 1:32 AM, Thomas Holder <
spel...@u
Hi Yotam,
6000 atoms should be absolutely no problem, even with much less memory. There
were few known memory leaks that have been fixed since 1.4, so could you try to
compile the latest code from SVN?
http://pymolwiki.org/index.php/Linux_Install
Cheers,
Thomas
On Oct 21, 2013, at 4:58 PM,
Hi.
I have python (1.4) on a xubuntu 12.04 machine (fresh install). The machine
has 6GB ram and an intel i3 processor (I don't remember the exact model).
On a previous install of Ubuntu (13.04) I had no trouble viewing files of
that size, but now I can't. I get the "standard" EEK! pymol just run o
