Hello,
this happens only on windows, not in linux. When I'm in sculpt/retopo mode, changing the 3D view (pan, rotate, zoom) produces a 3 second lag. Everytime!
After some investigation it appears it's a problem with the zbuffer depth. Forcing the driver to 16bit makes it run smoothly, 24bits produces the lag.
I use the latest drivers on windows.
It also happens when entering sculpt mode: the computer hangs (it seems to be swapping) for 3 seconds...
BTW, before finding out it was something to do with the zbuffer, cutting the 3Dview in two solved the problem too, but that was clearly not a good solution.
Dani
Description
Description
Event Timeline
Comment Actions
Angemeldet: JA
user_id=5357
i think this is somehow related with "partial redraw". u need to tick of "partial redraw" ini sculp menu.
Comment Actions
Logged In: YES
user_id=103
partial draw is off by default though.
Sculpt uses heavy opengl very heavy, so the driver/card combo could not handle it well.
What kind of graphics you have?
Further, the fact linux on your system works fine, but windows doesn't. really indicates an issue in your system install...
Comment Actions
Logged In: YES
user_id=651
Okay, I ran several tests during the weekend.
After many tries at installing ati's catalysts ("please install a default vga driver before installing catalysts") or ati's mobility's ("sorry your computer doesn't support ati...") I installed new omega drivers and the lag was gone on windows.
On linux (ubuntu edgy eft, latest proprietary drivers from ati, recompiled for my system) there is a lag, though it is quite short (half a second). So it remains useable. (asides from that, Blender freezes totally in any circumstance (not only sculpt/retopo), but I need to test more to see when i actually get the freeze and with the free drivers to see if it's that problem again)
So this is again a driver problem solved again by the use of recent drivers (although they're not the official ones!)
Cheers!
Dani
Comment Actions
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.