From: Chris Taylor (
Date: Thu Aug 11 2022 - 17:26:42 CDT

I get this when the latest build starts up and then it crashes. I didn't see anything in the release notes, maybe I'm missing some OSPRay runtime- is it built in? Could Windows 11 be causing an incompatibility? Thanks.

Info) VMD for WIN64, version 1.9.4a53 (June 29, 2021)
Info) Email questions and bug reports to
Info) Please include this reference in published work using VMD:
Info) Humphrey, W., Dalke, A. and Schulten, K., `VMD - Visual
Info) Molecular Dynamics', J. Molec. Graphics 1996, 14.1, 33-38.
Info) -------------------------------------------------------------
Info) Multithreading available, 24 CPUs, ISA dispatch enabled.
Info) CPU features: SSE2 SSE4.1 AVX AVX2 FMA F16 HT
Info) Free system memory: 26GB (80%)
Info) Creating CUDA device pool and initializing hardware...
Info) Unable to load NVML library, GPU-CPU affinity unavailable.
Info) Detected 1 available CUDA accelerator::
Info) [0] NVIDIA GeForce RTX 3080 68 SM_8.6 1.7 GHz, 2.0GB RAM SP32 KT AE1 ZC
Info) OpenGL renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
Info) Full GLSL rendering mode is available.
Info) Textures: 2-D (32768x32768), 3-D (16384x16384x16384), Multitexture (4)
Info) No joysticks found. Joystick interface disabled.
Info) Detected 1 available TachyonL/OptiX ray tracing accelerator
Info) Compiling OptiX shaders on 1 target GPU...
#osp: INITIALIZATION ERROR --> #osp:api: could not find module initializer ospray_init_module_ispc
#osp: INITIALIZATION ERROR --> Could not find device of type: default. Make sure you have the correct OSPRay libraries linked.
#osp: INITIALIZATION ERROR --> OSPRay not yet initialized (most likely this means you tried to call an ospray API function before first calling ospInit())(pid 5748)