Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-18 Thread Thomas Holder
one more thing: PyMOL will not render twice if using prior=1: cmd.ray(..., renderer=0) cmd.png(..., prior=1) Cheers, Thomas João Rodrigues wrote, On 04/18/12 09:54: > Thanks for the tips all of you. As I told Jason, the renderer option was > the billionth thing I tried to make it work.

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-18 Thread João Rodrigues
Thanks for the tips all of you. As I told Jason, the renderer option was the billionth thing I tried to make it work.. all default settings didn't. So it comes down to what Thomas said: if running in batch mode, there is no opengl window to capture from and > PyMOL will always fall back to ray tr

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-18 Thread Thomas Holder
Hi João, Pete & Jason, I think pml vs. py or 1.4 vs. 1.5 will make no difference. But I see two other things here: 1) renderer=2 is a "dry-run" according to the documentation, so it will not actually render a image. 2) if running in batch mode, there is no opengl window to capture from and Py

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread Pete Meyer
It may be worth trying pymol 1.4 (instead of 1.5) - although this shouldn't make a difference, it might provide some more information (you also mentioned that you've got a large scene - depending on composition 1.4 may use less memory than 1.5). You may also want to try using a pml script vs py

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread João Rodrigues
Hi Jason, I've tried a lot of stuff, thus the renderer=2.. (i installed povray and tried to use it). With the default option the result is the same. cmd.png(default_name+'.png', width, height, dpi, ray=0) Doing what you wrote still causes the renderer to kick in.. I'm a bit out of ideas.. Cheer

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread Jason Vertrees
João, I'm not sure why this is giving you problems. Why do you have renderer=2? Why not the default? Are you counting primitives? If so, I suggest: cmd.set("ray_default_renderer", 2) # snapshot cmd.png(myFile, width=w, height=h, dpi=d, ray=0) # this will ray trace cmd.png(myFile, width=w, hei

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread João Rodrigues
Same result Jason, i also tried =false... No dia 17 de Abr de 2012 20:45, "Jason Vertrees" < jason.vertr...@schrodinger.com> escreveu: > Hi João, > > What about > > cmd.png(default_name+'.png', dpi=300, ray=0) > > Cheers, > > -- Jason > > > On Tue, Apr 17, 2012 at 11:18 AM, João Rodrigues > wrote

Re: [PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread Jason Vertrees
Hi João, What about cmd.png(default_name+'.png', dpi=300, ray=0) Cheers, -- Jason On Tue, Apr 17, 2012 at 11:18 AM, João Rodrigues wrote: > Hello all, > > I'm using Pymol v1.5 (from fink, so open source version) to trace large > scene that I have. To that end, I'm avoiding having PyMOL open

[PyMOL] Using cmd.png with ray=False still ray traces the image

2012-04-17 Thread João Rodrigues
Hello all, I'm using Pymol v1.5 (from fink, so open source version) to trace large scene that I have. To that end, I'm avoiding having PyMOL open and I wrote a small python script to do the rendering for me. All goes well, except this last part (don't mind the obvious variable names): cmd.ray(wid