--- Operating System, Graphics card ---
Windows 7, Nvidia Quadro 2000
--- Blender version with error, and version that worked ---
Initially worked on Blender official 2.67a release, but then caused error and does not work on any revision.
--- Short description of error ---
Baking to texture (any settings and bake option, and on any object) does not work as supposed.
Starts off baking all nice and good with progress in UV editor, then crashes when hit completion.
Blender just automatically closes without any error or bug screen.
checking with other computers finding that bug is within the blender file, not the program itself.
--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
https://www.dropbox.com/s/i5bj7n1gxikqyjk/wall.blend / or use attached
Open blender file above ^ in any revision in the 2.67 series, use current object/ make new and attempt baking a to any texture.
Description
Event Timeline
This looks like simple missing NULL pointer check, (happens on render too).
Assigning to Lukas incase the error should be fixed elsewhere.
Hey, thanks a lot for taking the time to fix the problem in such a short time!
By any chance a way to fix a blender file by hand to resolve this issue on my main workfile? as the issue follows the file and not the software itself, i cannot simply append the whole scene from one file to another as the bug follows along, though i can append some parts over without having the bug along. But as i have a big project stored in one file, it is very time consuming taking out every object i need, bake it in another file then get it back. Any quick solutions i could do to fix the file by myself?
Yes, you just need to make sure none of the node groups has a "Missing Datablock". I have attached a demo file with a small script that prints out faulty node groups to help fix this. You can then check the broken materials and either assign a correct node group to these nodes or delete them. Missing data blocks can sometimes happen when you use linked data that gets lost somehow, e.g. by changing file paths. Generally this can break materials of course but should not be a crasher (which is fixed in trunk now).