In allselect.blend in the testing files for blender 242, if I select the metaball, enter edit-mode, and right-click (select) twice on it, blender crashes. Blender 241 doesn't crash in this place.
This seems to be the case with any type of meta object in any file.
computer: compaq presario SR1230NX
OS: windows xp home
RAM: 512MB
processor: AMD athlon xp 3200+ (2.2ghz)
graphics card: unknown (whatever the computer came with, and this isn't exactly a good computer)
Description
Description
Event Timeline
Comment Actions
Logged In: YES
user_id=1013
Hi,
I can't repeat this bug report. Can you tell me, what version of testing build do you use? Do you use CVS version? I fixed almost the same bug some time ago.
Best regards,
Jiri
Comment Actions
Logged In: YES
user_id=103
William: this should have been fixed in the RC2 version. Please confirm you used that.
Comment Actions
Logged In: YES
user_id=4945
I was using RC2. I also tried re-downloading RC2 and using the user preferences that come in the download and the bug was still present.
Comment Actions
Logged In: YES
user_id=4945
After playing with it a bit more, I can see that if I do anything at all and then try to select the metaball, Blender crashes. For example, I can go into edit mode, rotate the view, and then do a select on the metaball and Blender crashes.
Comment Actions
Logged In: YES
user_id=103
OK, I think the opengl card might be the problem. Download official release 2.41 from our site and retry?
Comment Actions
Logged In: YES
user_id=103
Really clueless still... lets try at least someone with windows and a debug build.
Andrea, can you do some metaball clicking? :)
Comment Actions
Logged In: YES
user_id=103
rulerofutumno: until now, nobody can redo your crash. it was tested with several Windows systems too.
We had a report before about selection sometimes crashing in opengl... depending on opengl card quality or driver install. It is very weird though that you claim 2.41 doesn't crash, the selection code for metaballs didn't change.
Googling for the compaq presario SR1230NX, I found it has 'on board' graphics, which probably means the intel graphics card. You could try to find out if there's driver upgrades for this card, or check on all variations of the opengl properties menu?
Comment Actions
Logged In: YES
user_id=4945
There doesn't seem to be any new drivers for my computer. The only name of any hardware in my computer connected to graphics that i can find is "VIA/S3G UniChrome IGP", so i would imagine that is the graphics card?
What is very odd, however, is how I can't reproduce my bug, despite it occuring consistently every time I tried selecting any meta object. I believe it stopped happening because I changed my default settings in Blender, and the settings I had before may have been set in my copy of 2.41. However, if I run Blender 2.42RC2 with any other .B.blend file from 2.41, metaball selection runs perfectly.
The only other thing to do with my computer that I have changed recently is changing my resolution and monitor refresh rate from 1024x768 at 100Hz to 1600x1200 at 60Hz; however, switching back to my previous settings does not seem to make the bug occur again.
Comment Actions
Logged In: YES
user_id=103
Oh dear, an S3 chip... that is really not good for opengl applications.
BTW; if you still have the faulty .B.blend that crashes meta selection, just upload that here.
Comment Actions
Logged In: YES
user_id=4945
I don't have the .B.blend anymore; it didn't occur to me that the user settings might be the problem.
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.