I would love to know what is causing this issue so I could possibly work around it but so far Support has not been able to provide any more details or workaround. Talked to support and associated my case to the same ticket number. I am using an iMac Pro 10 cores with 64gb RAM and Big Sur 11.1. The UI becomes laggy to the point it’s unusable and I can only solve the problem by restarting. Complexity of the scene does not matter in my case as I get this problem with a simple sphere. Houdini will become slower and slower after 10 minutes of use.
I am using Houdini 18.5 Indie(tried all build up to 437) and I am impacted by this issue.
Lazymouse reduce lag update#
I'm still using the Apprentice (tested 17 and 18 under macOS Mojave) but I'll probably switch soon to Indie in order to complete a project, I'll update this post in case things get better.
Lazymouse reduce lag full#
This is the bug id: #105946 (unfortunately, the bug tracker is only visible to users of the full commercial versions). jdmorani vvzen To everyone having the same issue, I spoke with support and they told me that it's actually a known bug and it's affecting many Indie users as well.
Lazymouse reduce lag install#
Does a company actually support Mac if it only supports discontinued hardware? This only started three updates ago and a fresh install hasn’t helped. When I’ve inquired before about other viewport problems, the help desk claims my 2019 Mac Pro graphics card isn’t officially supported but, um, it has been out for 2 years now. VRAM becomes quickly maxed out while doing relatively little and the app slows to a crawl until it crashes or I need to restart it. I get the sense it is overloading the GPU despite the geometry in the scene being simple (like one sphere). Any help would be much appreciated.Īlso experiencing this exact issue since the last few 18.5 updates. Knowing this issue was opened in June makes me very worried as I can’t work in this condition.
Vvzen To everyone having the same issue, I spoke with support and they told me that it's actually a known bug and it's affecting many Indie users as well.
0 kommentar(er)
