VMD-L Mailing List

From: Bart Bruininks (b.m.h.bruininks_at_rug.nl)
Date: Fri Dec 13 2019 - 05:01:18 CST

However, which build should we use and how can we obtain it?

---------- Forwarded message ---------
Van: John Stone <johns_at_ks.uiuc.edu>
Date: vr 13 dec. 2019 om 07:53
Subject: Re: vmd-l: Files not written during OptiX ray tracing
To: Bart Bruininks <b.m.h.bruininks_at_rug.nl>
Cc: <vmd-l_at_ks.uiuc.edu>

Bart,
  If you have a fully up-to-date video driver, you might want to try a
newer test build. In my testing here I've finally been able to disable
a piece of workaround code in the OptiX renderer that leaked a bit of
memory to avoid a potential crash. I've tested the new code with driver
440.44 with good results so far. Assuming continued testing goes well
tomorrow, I would say that a new build would likely resolve this issue
for you.

Best,
  John Stone
  vmd_at_ks.uiuc.edu

On Thu, Dec 05, 2019 at 05:56:54PM +0100, Bart Bruininks wrote:
> Heya,
> I have been rendering some movies as of late, and I keep running in to
the
> following error after about 150 frames:
> ERROR) OptiXRenderer) ERROR: Unknown error (Details: Function "RTresult
> _rtContextLaunch2D(RTcontext, unsigned int, RTsize, RTsize)" caught
> exception: Assertion failed: "!m_enteredFromAPI : Memory manager
already
> entered from API", file: <internal>, line: 1099) (OptiXRenderer.C:2597
> I am running vmd 1.9.4a31.
> It results in the rendering to continue in the moviemaker, but no
actual
> files are written (an empty file does get created).
> Cheers,
> Bart 

-- 
NIH Center for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
http://www.ks.uiuc.edu/~johns/           Phone: 217-244-3349
http://www.ks.uiuc.edu/Research/vmd/