[Bf-committers] Ghostlike datablocks
Mon, 10 May 2004 13:47:09 +0200
No (Jeremy) it doesn't work that way.
Blender hardly frees data when "delete", instead it unlinks data. All
data that has links then still is written in a Blender file.
Sometimes, such links still exist (can be a tree with many brances).
The unlink options in Blender don't fully check entire trees, instead
it reconstructs trees on a file read.
The way to get rid of these Meshes is just by 2 save/load cycles. Not
with Blender quitting inbetween!
(In your case, when you delete a Scene for example, all Objects being
used by the scene get one 'user reference' less. But the data linked to
Objects itself remains.)
On Sunday, May 9, 2004, at 20:55 Europe/Amsterdam,
> Being one of those who pokes around the oops code. You can probably
> select the meshes there and then delete them in the 3d view. What's
> selected in Oops should be selected in 3d view. I don't know for sure
> if that will work but you might give it a try.
> On 9 May 2004 at 7:51, Meino Christian Cramer wrote:
>> I've got a problem and found no way to solve it so it may be a bug.
>> I had a *.blend file with one SCENE.
>> Then I added (SHIFT F1) a second scene from another file.
>> Then I deleted this scene (it was the wrong one).
>> Now I have tons of "wild" meshes with nothing is linked to. They only
>> increase the size of the file.
>> A save-quit-restart-reload cycle does not help.
>> In the OOPS window those meshes (scene datablocks) are drawn with
>> background color of the OOPS window (or one could say "without" any
>> extra background color). All "real" meshes do have a background
>> Nor more used materials get kicked out of the file after a
>> save-reload. This seems not to be true for mesh datablocks.
>> I found no way to delete them neither by experimenting nor by
>> searching the 2.3 book.
>> Any hint? If no, then it is a bug... ;)
>> Kind rrgards,
>> Bf-committers mailing list
> Bf-committers mailing list
Ton Roosendaal Blender Foundation firstname.lastname@example.org