To reduce VRAM usage, try the following." (suggestions as noted above) I'm suggesting the pop-up could say something like "your GPU VRAM has likely reached its capacity. Turning off RTX features, reducing the amount of geometry in the scene (section box in Revit,) reducing quality from Ultra to High, reducing output resolution, or a combination of those fixes the issue 95% of the time.Įvery time I have submitted this error to Enscape, I get a diagnosis of "VRAM maxed out." Every time I see this error discussed on the forum, the diagnosis ends up being "VRAM maxed out." So if that is the leading cause of the crash, why is the message suggesting to switch the graphics card and update drivers? Our drivers are kept fairly up to date, and this never solves the issue.Īfter wasting time with that, the helpdesk gets in touch with our rendering specialists to troubleshoot the issue further. Checks the switching of the internal graphics card. Their first line of action is to call our internal IT helpdesk. Typically the user is working along just fine rendering lower-res drafts, then they try to do final output and crank up the resolution, and the error occurs. I'm talking about the language in the error message pop-up. Regarding your experience when it comes to troubleshooting this for your users, are you strictly talking about what is being communicated here in the Forum, or the support channels? ( / Crash Report) (Ray-Tracing was indeed enabled) I've made that more clear in my previous reply, pardon me for overlooking that this particular GTX card is indeed capable of Ray-Tracing but not suited at all. You are correct when it comes to what caused this crash as I can see per the provided feedback report we received. It sends our users and IT dept down useless troubleshooting paths that do not solve the problem. It is almost never solved by updating GPU drivers or changing which graphics card is used. In 99% of cases the cause is running out of VRAM due to large models, rendering at ultra hi-res, using RTX reflections, or a combination of those. This seems to be the default error that Enscape throws up when anything goes wrong. Could you consider updating this message to better indicate what is -actually- causing the crash?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |