Visualize 2019 Standard...
"Application Error" on render. Happened immediately on completion of render.
Thanks for any assistance.
I used to get a lot of these crashes when my application installation locations were different from the default install location suggested by visualize. Do not assume that putting the various (appearance, environment, plate) files in custom locations, especially if you work in a networked environment, will make Visualize work faster or smoother. It will not.
Thanks Rich, I am using the default locations and several months ago while experiencing problems I moved my work files locally. Unfortunately it made no difference.
After SP3 this still occurs. It does it only on a high pass count, in this case I had it set to 4000. It does not do it at 400. The temp folder it is trying to access doesn't seem to exist. The render seems to finish ok, the image looks great.
An error has occurred. Please contact your local SOLIDWORKS support representative for assistance.
Error occurred at 01:10:26 on Wednesday, 15 May 2019. Build version is 126.96.36.199.
System.IO.DirectoryNotFoundException = "Could not find a part of the path 'C:\Users\djohnston\AppData\Local\Temp\SOLIDWORKS\SOLIDWORKS Visualize 2019\805b4bd0-37dd-4a91-825e-eb500592500e\Thumb.png'."
Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at Bunkspeed.Common.DataModel.DataStore.PackageThumbnailStore.SerializeFile(BitmapSource thumbnail) at Bunkspeed.Common.DataModel.DataStore.FileBasedDataStore`1.UpdateValue(TValue value) at Bunkspeed.Common.DataModel.Manage.ProjectDocument.SaveShadowProjectFile(IProjectCurrents simpleCurrents, IViewBaseContext viewContext) at Bunkspeed.Common.DataModel.Manage.ProjectDocument.<AutoSaveCallback>b__55_0() at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore() at System.Windows.Threading.DispatcherOperation.InvokeImpl()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout) at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout) at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout) at System.Windows.Threading.Dispatcher.Invoke(Action callback) at Bunkspeed.Common.DataModel.Manage.ProjectDocument.AutoSaveCallback(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers()
Direct3D Device Feature Level: Level_11_0Microsoft Windows 7 Professional Service Pack 1 - Pass8 x Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz - Pass24518 MB RAM available - Pass8192 MB NVIDIA Quadro M4000 - Pass188.8.131.523 GraphicsCard drivers - Pass1 CUDA devices708281 MB disk space free - Pass11968 MB ram used by application
NeurayDeviceMode is Hybrid
THanks in advance.
Based on that log/callstack (see line's referring to "serialize" and "SaveShadowProjectFile"), this looks to be an error in the Auto-Save, Auto-Recover functionality.
I have also "randomly" seen this internally fairly recently and have asked our QA to try and get reproducible case for us to work on.
Large # passes could be the key. But I'm also suspecting it's more of a timing issue.
Your suspicion is probably accurate. I just did a 4000 pass render and it worked just fine that time. For some reason it seems more likely that the error occurs when I leave for the day and let the machine render unsupervised.
Retrieving data ...