Hi Istvan, With regards to CPU ray tracing only running on a single core, that sounds like a major regression; we haven't changed anything in regards to that so I'll investigate. As for your first issue, do you have any examples that I can inspect myself to see what the issue is?
Jarrett J. On Fri, Jul 19, 2024 at 6:11 PM Istvan Kolossvary <ikolos...@gmail.com> wrote: > Hi, > > I have had these issues with the new timeline. It works fine with scenes > and short multi-state objects (like those showcased in the Pymol 3 online > visualization course) but when it comes to real life MD trajectories I > found two "dealbreaker" issues. > > 1) With complex movies based on MD trajectories and not scenes, the Draw > mode is not working. If I select Draw to generate a movie file quickly for > testing then (a) it takes almost as long as Ray Tracing and (b) the movie > is complete garbage, showing only random parts of the system. > > 2) The Ray Tracing mode works fine, but processing time is prohibitively > slow because Pymol 3 only uses a single CPU core for ray tracing. Pymol 2.5 > automatically uses all the available cores for ray tracing. The way Pymol 3 > is right now, it takes 24-48 hours to produce a 3000 frame movie, which is > only 100 seconds. > > Has anyone encountered similar issues? > > Thanks, > > Istvan > _______________________________________________ > PyMOL-users mailing list > Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net > Unsubscribe: > https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe -- *Jarrett Johnson* | Senior Developer, PyMOL
_______________________________________________ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe
