I upgraded to 0.14 from 0.13. Blender lags so much it's not usable any more. Never mind if the scene has anything in it.
I saw something about archimesh - but it's difficult even trying to deactivate a plugin with this laggy interface - so I've tried to deactivate it, but it's kind of the same.
Deactivated crowdmaster too for good measure, same.
It seems to be able to connect to my Mac though, on which it works without lagging. On 0.13, it failed.
I'm on Windows 10, Blender 2.79.
Hi Nicolas, since 015 is out now, I wanted to get back in touch and see if 015 fixed your problem on linux? Please get in touch and let us know if its fixed!
James
Hi James
Thank you for the thourough reply.
If you need someone (else) with the problem to try out 0.15, just drop me an email and I'll be happy to test and report on it.
In any case I'll be waiting on 0.15 to make use of all the power I have at home :)
Keep up the good work!
Nicolas
Hi there Nicolas,
We've heard the same from a number of users, v0.1.5 is being built with a fix for this, we're still making improvements but two to three weeks is our estimate. The problem came from something that has always been there. The synchronisation algorithm is what is slowing down the ui.
Initially we mistakenly thought it was the old despgraph but after a short test, we found that it was CR. What happened with 0.1.4 is that we changed how the addon detected changes to the data. Instead of using BLender's view port update system, we chose to use user input events. We did this because of what's coming in 2.8
As far as I can tell, the viewport update system has been either radically changed, or removed. This made it highly impractical for us to rely on it and so we now respond directly to user input. This means that the UI in v0.1.4 can slow down and indeed dramatically so for some users, though it seems find on some systems, regardless of the OS used.
In v0.1.5 we managed to make some pretty huge optimisations, one scene I had been using had CR running at about 1.4 to 1.7 seconds, making the UI practically unusable. After the optimisations, the same file was running CR at 0.040 seconds. The change was dramatic, the UI went from completely unusable to pretty much normal.
We're not quite done yet though, we've still got some users that are testing 0.1.5 complaining of slow performance on some scenes, and we're testing their files directly so we can continue to find where things are running poorly.
The bottom line is you can expect 0.1.5 to be a lot more like using blender normally, so long as we can find all the slow areas. If you have a particular file that is running poorly, and don't mind sharing it with us, we can run it on our systems and test how much different 015 will make for you.
Just drop us an e-mail at info at crowdrender dot com dot au
Cheers!
James