On blender versions 2.44 through 2.45 (official & svn) - both static and normal, the sculpt tool fails to work. In any case (simplest being a plane), when I click, nothing will happen - apart from the occassional affecting wrong vertices.
I guess it's a very setup-specific thing: there are only a handful of people with this problem, at least that posted on elysiun: http://blenderartists.org/forum/showthread.php?t=94852 .
I know I'm supposed to tell you how to reproduce this (which would be; try to sculpt), but unless you get the exact hardware - which next to a financial challenge also possibly poses a physical one, regarding the motherboard (if you need the specific modelnumber, I'll look it up somehow)..
Abit motherboard with Intel ICH8 chipset
with Intel Core2Duo 1.86@1066FSB, 2GB RAM@1066FSB
Nvidia 8800 GTS with G80 gpu
Debian GNU/Linux testing, linux 2.6.21
so I'll tell you what I know :/
What exactly happens when I click isn't clear to me, but when an extreme angle is taken to the object (be it a plane, cube, suzanne or whatever), vertices *might* start to move - however, seldom the ones that are under the cursor, and never with the appropriate 'fade'.
I have been nibbling on the code for a bit, so I'm able to tell you this:
In sculptmode.c, inside the function do_brush_action, on line 936 (SVN version from 29/10/2007), inside a if-for construction where the vertices within reach are being calculated for damage, there's a
if(av_dist < e.size) {
and the code never gets past that calculation, which primarily compairs the editdata object, and some unproject()-results. As is probably clear by now, I don't at the least know what I'm talking about, but I'm willing to help, so I had to try at least :p ..
I've replaced this line with if(1) { to see what happens, and in fact it goes 'well' - it just returns a fade of 0.00000000. So I'm guessing, somewhere in the calculation of matrixes & vectors.. & stuff.. stuff goes wrong. Ahem.
I'd really like to give you guys more information, but I wouldn't know *what kind* of information, because I just dont know what could screw up matrices like that. For example, I'd like to 'draw' the editdata object that init_editdata generates, or at least the .center of it, so I could 'see' what blender is doing. Of course, that is not effective programming, but what do I know eh :p ..
(In case you were wondering how much I've tried, for example, clicking the 'other' LMB:
I've tried every setting I could think of, tested the tablet input (wasnt doing anything, which is good), removed my .B.blend & ~/.blender, reinstalled all my graphic drivers, used the nv-driver to assure myself GL was being done with software, etc. Running the windows version via wine yielded the same result.
To my knowledge, the only things I havent changed are described in my setup, above.)
So now, I'm completely stumped here, because apart from the video card I've got a fairly common setup. I really, REALLY, LOVE!! your tool, it's frigging awesome, to say the least - thanks a lodylodylot!; so if you need any help at all, even with simple things as scanning the code for.. little GL-devils or whatyacallit.., just PM me! (Assuming that's possible here, I just registered - otherwise, you could use roderik@gmail.om)
P.S.: Sorry for the messy report; I might have exaggerated my attempt to leave more than just 'sculpt mode doesnt work'...
Description
Event Timeline
whoops, my email address is wrong. Use roderik _at_ digicit.nl.
If your nickname is Nicholas Bishop, please read this ;p
Nicholas is not much available at the moment...
What I do know is that proper sculpting depends on opengl to work flawlessly. Try to set or disable everything you can find in our system to test? Further:
- is Blender 2.43 working for you? Or older? (Only official releases from blender.org)
download.blender.org/release/
If older versions don't work either, you got a system problem... :)
- load the static version of blender for linux, and test.
if that version does work, you got issues with opengl drivers.
Well, like I said, the static version doesnt work either: i even tried the nv X.org driver, which doesnt even have hardware support for OpenGL; i tried all different kinds of software OpenGL xorg binaries; and last but not least, older versions dont work either.
So apparently, I've got a system problem.. But what does it mean? What kind of system problem could it be, and/or how can i find out?
Or is it more like - it's a hardware quirk, and you can say goodbye to your dreams of ever sculpting again :P?
Also, will Nicholas Bishop be back after 6 dec. :P? I'd sure like to be able to get some more information, because right now there isn't a thing I can do to find out more..
Let me clarify my intentions - I will keep trying to make it work, doing whatever I can think of. The pool of things I can try however has dried up to a dash of dust - as this problem seems to be caused by OpenGL, but also occurs under nv & static/mesa, I'm confused as to what area I should tweak now.
I'm not deep enough into C & OpenGL programming (I'm a PHP programmer :S) to find the actual cause, but with a little help from your side - as to what I could be looking for, if not an OpenGL problem then what? - I think I'd manage it.
Ultimately this could result in a small P.S. in the blenderwiki at sculpt mode with a little bit of text information saying something like: "If your sculpt mode does not seem to react on clicks, try " and then whatever the solution will be in this case. I'm still hoping it could be a library, but I've had all the OpenGL libraries and I'm using a standard Debian distro. All in all, I want to nail this problem, but I can only do so if/when you guys tell me roughly in what direction to aim ;p
Thanks for listening/helping/coding this awesome program ;D
Possible fix.
I was also suffering from the same problem. After a couple of bumps I was able to solve the problem.
Under Debian, with libGLU >= 7.x Blender sculpt tool doesn't work.
To fix this I downgraded the package libglu1-mesa-7.0.1 to libglu1-mesa-6.5.1.
I don't know if this is an intentional change on the GLU libs or if they messed up something. In any case, either libGLU or blender is gonna need a fix to work in the future.
I'm still waiting for confirmation on this from scraze. But if this also solves his problem, I leave the rest to the dev teams :)
Thanks for everything.
Renato Alves' solution works for me too!
The new mesa-libs (which I apparently forgot to tweak in the downgrade-direction Dx) will apparently not gluUnproject right.
I don't know if the new libglu1-mesa needs other types of variables passed to it or that it's simply gone crazy - so I guess I'll go ask the mesa-guys and come back here with some kind of answer ;D . If there is something that needs to be changed, I guess you should know :?
Thanks all!
Well, it seems to be a genuine libglu1 mesa bug, but only in the debian archives. Apparently it has been fixed a version later (in 7.0.2).. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449490
So this can be closed! Sorry to annoy you guys ;p
I'll put the solution in the thread on BlenderArtists I mentioned, and that'll be that.
Thanks again!
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.