high-res snapshoots stops being writen to disk after a while


high-res snapshots are not processed to disk, after a while (at least in stressed regions, like burn2 atm)

Switching down to normal snapshot-size(screen-size) process that snapshot to disk. Switching back to high-res do not heal the issue. A relog do.

This is a bit annoying due mostly nobody control the output while shooting and some scenes are gone.
So it would be not so nice if the release version would have this issue too.


Exodus Viewer 12.10.19 (0) Oct 19 2012 19:23:28 (Exodus Viewer DEVELOPMENT)
Exodus Viewer 12.9.24 (1) Sep 24 2012 17:03:03 (Exodus Viewer DEVELOPMENT)

CPU: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz (3135.42 MHz)
Memory: 24575 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 670/PCIe/SSE2

Windows Graphics Driver Version: 9.18.0013.0697
OpenGL Version: 4.2.0

RestrainedLove API: RLV v2.7.0 / RLVa v1.4.6a
libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU v6.4.1
Audio Driver Version: FMOD version 3.750000
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Not Connected
Built with MSVC version 1600


Dil Spitz
November 18, 2012, 5:14 PM

yesterday i had the chance to do (3 hours) some (~300) snappies with build in a stressed (~40 people, Time Dilation dropped down to some like 0.5) region and had no problems with non writes.
So i believe this issue is a so rare or fixed issue that this issue should be seen as closed for now.

Dil Spitz
November 10, 2012, 8:00 PM

The s2d-shortcut (ctrl-`) is what i use.
S-floater works as long as i let it do default screen resolution. When the issue comes up and i switch the s-floater to high-res-snapshots (double screen dimensions), it also stops processing to disk.
Will keep on shooting with and try to catch up the logs. But as mentioned, it may takes a while (and maybe a stressed region too) to get the effect. Your viewer is somewhat to good

Katharine Berry
November 3, 2012, 4:29 AM

Are you using the Snapshot to Disk shortcut (ctrl-`) or the Snapshot floater? If the former, what happens if you try the latter? If the latter, does the preview display properly?

Please provide us with a log of the failure, if possible. This could most easily be done by noting the time at which a snapshot fails, then hitting the Panic toolbar button (not shown by default) or Develop -> Force an Error -> Force Bad Memory Access. Then comment here with the time you failed to take a snapshot, the time you crashed the viewer, and your name if on an alt. It would also be good to know what resolution you're trying to use.

I looked up your hardware and it's clearly not that, so that's one potential issue eliminated.

Dil Spitz
October 23, 2012, 12:50 AM

Build has this issue too.

Maybe the issue is seen in this two builds cause they run so much more stable (longer, even in stressed sims) and only crash on real heavy use after hours. crashed before Snap2DiskStop-issue hit. So, its not testable.

Also speculation:

the view shows a nearly maximum 'Bound' (374/384 MB), maybe here is something gone over the edge?

a cross-test against LLs dev viewer (Build 266075) were not able, cause it crashed also before Snap2DiskStop-issue hit.

Cannot Reproduce
Your pinned fields
Click on the next to a field label to start pinning.




Dil Spitz