PDA

View Full Version : Baking using SVN crashing blender...

Michael-Williamson
01-06-2008, 10:38 AM
I'm posting this in Blender artists forum as well!

I'm using the latest SVN blender for this project.
This is tricky as I can't post the blend due to non disclosure agreements, but I have recently encountered a problem:
---------------------------------------------------------------
In the last day or so whenever i try to bake a lightmap blender just crashes (ie completely disapears! (console says "Segmentation fault (core dumped).)

Now, I can load my scene in 2.45. When i load it i get the following console message that doesn't appear when I use the SVN version

"Memoryblock free: attempt to free NULL pointer"

2.45 will bake the map no problem, unfortunately I really need the SVN version to work as the QMC sampling gives really nice smoothed lightmaps rather than the severely aliased and harsh output from 2.45 (I'm already rendering the maps large and downsizing them to reduce artefacts....

--------------------------------------

I don't know exactly what I did that made things stop working, but older versions of the file still bake fine.

Beside a lot of general modelling I have done the following:

1) Imported OBJ files (from a collaborator)
2) Imported LWO files (from a collaborator)
3) Joined lots of meshes and broken them into other parts
4) Added curves and used some array modifiers with and without curve modifier

A weird (maybe) related issue:
some objects (that have been in the scene for a LONG time) seem to dissapear when I switch to local view.
I've tried shenanigans with the cursor, show all, show selected, center cursor etc but to no avail. selecting the mesh and separating all of the faces as a new object and deleting the original worked a s a workaround, but it's a bit of an indication that something is rotten in Denmark....

Hope some one can help!

Mike
fulg0re
01-06-2008, 01:28 PM
Hi, I cant help you with the baking problem, but the disappearing of objects in local mode happened to me yeseteray too. In blender in edit mode when you ctrl+LMB you add a new vertex in 3d space somewhere, maybe you accidentally ctrl+LMB during modelling, by doing this the bounding box size of the object increases depending of the location of the new vertex. If the added vertex is very far away then the object (bounding box) size is very big.
When you switch to local mode then it fits the bounding box of the object to the screen. In your case the bounding box is very big because you have a small mesh + a vertex that is far away.The object (bounding box) does not disappear, you just cant see the mesh because it is very small regarding the bounding box (object). To solve this go to edit mode and select all original vertices with the laso tool, or box select, or brush select, do not select with "A", them make a slect swap to slect the "new" vertex, delete it.
Maybe this vertex is the reason for the baking problem too.
I hope this helps.
Michael-Williamson
01-06-2008, 01:48 PM
Hi, I cant help you with the baking problem, but the disappearing of objects in local mode happened to me yeseteray too. In blender in edit mode when you ctrl+LMB you add a new vertex in 3d space somewhere, maybe you accidentally ctrl+LMB during modelling, by doing this the bounding box size of the object increases depending of the location of the new vertex. If the added vertex is very far away then the object (bounding box) size is very big.
When you switch to local mode then it fits the bounding box of the object to the screen. In your case the bounding box is very big because you have a small mesh + a vertex that is far away.The object (bounding box) does not disappear, you just cant see the mesh because it is very small regarding the bounding box (object). To solve this go to edit mode and select all original vertices with the laso tool, or box select, or brush select, do not select with "A", them make a slect swap to slect the "new" vertex, delete it.
Maybe this vertex is the reason for the baking problem too.
I hope this helps.





...I'll bet that's the problem.... I use a tablet almost exclusively, which makes LMB clicks all too easy to do inadvertently, especially when navigating the views I can see how I'd CTRL_LMB all the time!

I'm surprised it doesn't happen more often actually!

Any tips on how to locate them? they're hard to see, especially with the viewport clipping....



I've gone back to an old file and am merging the changes from the new file one by one to see if I can recover things... I've made a lot of changes, been doing it a while... It'll take a few hours!
fulg0re
01-06-2008, 03:01 PM
Any tips on how to locate them? they're hard to see, especially with the viewport clipping....


Just select all the vertices but not the "new" vertex, if the mesh consists of connected vertices select them with ctrl+L (seect linked), otherwise do it manually with other selection tools. Then when you have all vertices selected (not the "new" vertex) make a select swap (press W then a menu appears an d you can choose select swap). The select swap slects the "new" vertex, if you want to locate it press nummpad "," (zoom to selection).
LetterRip
01-07-2008, 09:39 AM
Since you are using SVN and can compile yourself - please do a debug build (make debug or scons debug i think?). Then run blender from a debugger (gdb blender.exe ; run) and when it crashes do a back trace; then submit the backtrace as a bug report and I'll see if brecht can have a look (if you aren't building with gcc then it might require other directions to debug since build environments vary..).

LetterRip
Michael-Williamson
01-07-2008, 09:44 AM
Since you are using SVN and can compile yourself - please do a debug build (make debug or scons debug i think?). Then run blender from a debugger (gdb blender.exe ; run) and when it crashes do a back trace; then submit the backtrace as a bug report and I'll see if brecht can have a look (if you aren't building with gcc then it might require other directions to debug since build environments vary..).

LetterRip


Sure, will try now (although I've managed to merge most of the changes into an older file)
CGTalk Moderation
01-07-2008, 09:44 AM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.