![]() ![]() Right away, whenever you experience a technical issue like that or even crashes, please ideally instead get in touch with our technical support team directly by submitting a feedback report with logs/crash dumps and machine information: …sing-the-feedback-button/īesides that this error at hand usually occurs when your graphics card memory is running full (VRAM), although you mentioned the scene shouldn't be too complex, so in that regard the logs should tell us more. Please help as I do need to submit renders to clients soon! When I open a file that has less heavy geometry, I can run Enscape. My computer doesn't have the ray-tracing ability, so that's not the issue in my case I have deleted lighting, and complex geometry (Which is, to be fair, not much), saved the file as a new file and stored the file on the C: folderĤ. I have updated my GPU as suggested in the message box (This step haven't solved the issue)ģ. Uninstall Enscape and install the newest version (Currently, I have the most updated Enscape version, which is: Enscape Versopm 3.4.4+94564 (This step haven't solved the issue)Ģ. Vulkan Error: vk::Queue::submit: ErrrorDeviceLost at queue submit.ġ. When I start Enscape and get to 99%, it shows a window saying that "Enscape encountered an error during rendering. I was working on a project in Sketchup 2023 which does not have too much complex geometry, however, the last bit I did was adding more lighting + adding more models.ġ. I'll use your feedback to further reinforce the demand for this. In the end, our goal is to allow users to do more of the troubleshooting themselves though, if possible. I really appreciate the response, thanks, that clears it up of course - Matter of fact, we are actually looking into a dedicated additional system so to speak to what you proposed but it's still a bit too early to talk about details. I would also think that might reduce the number of logs getting submitted to Enscape by giving users more useful advice in troubleshooting their own issue. ![]() Then maybe "switch graphics card" and "update drivers" as secondary possible solutions. 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 |