Feature request by Wegg__, when reimporting lwo object add the ability to optionally not create new materials
and instead use the materials that exist in the scene by name. Note: this is case sensitive

To properly support this functionality we would need to extend our API's
and there are better, dedicated tools to do this on each platform.

Some highlights:
  * New panel in the render options to control publishing
  * Easier cross-platform publishing
  * Ability to archive published binaries

More information can be found on the addons wiki page:
http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Game_Engine/Publishing

Note: This addon is intended to replace the Save As Runtime addon.

Proper handling of drawing node border when the node is partially out of view.

Nicer Lazy Connect node outline for hidden nodes and reroute nodes
Support hack_force_update for compositor (didn't refresh when doing some things)
Support volume shaders and group nodes with shader output for Emission Viewer

Added "UV Map" in Shaders and "Corner Pin" in compositing

Based on patch/idea by jrestemeier (Jens Restemeier), many thanks!

Differential Revision: https://developer.blender.org/D601

Based on patch/idea by jrestemeier (Jens Restemeier), many thanks!

Differential Revision: https://developer.blender.org/D600

Fix T40629: Dynamic Space Bar adds Lattice instead of empty after adding at least one lattice object. Menu act correctly though.

Patch by meta-androcto (Brendon Murphy), thanks!

Idea from karanikk (Kostas Karanikolas).

also rename 'Bake Space Transform' -> 'Apply Transform'

Patch by ldo (Lawrence D'Oliveiro), with very minor changes by myself.

not in sync with actual loc/rot/scale values (and hence export wrong 'rest' transform
of some objects).

Note this needs testing still, not quite sure the result is correct yet (though it looks correct),
as usual with FBX (FBX Converter at least does not seems to read embedded textures). :/

Will disable this option before release, if I can't make it work till then.

Fix T40216: Binary FBX exporter doesn't export proper materials to Unity when there's a modifier added.

This is not a bug, in fact, but imho we do not need to compare exactness of values
up to the 6th decimal, 4th decimal should be enough, and will avoid such cases of
"over generation" of data...

Export: generate a valid scale value from Blender scene's Scale setting (if valid, else 1.0),
assuming 1BU = 1m and 1FBX unit = 1cm.

Import:
* Use by default axes and scale data in FBX file instead of manually specified ones (using same
conventions as in exporter).
* Also import FPS data from FBX file (crucial for future animations import!).

And a few fixes for issues found in those areas as well...

Rename export_fbx_bin_utils to fbx_utils, since some of its content will be used by importer as well.

As suggested by meta-androcto:
http://blenderartists.org/forum/showthread.php?336209-ANT-Landscape-generates-terrain-with-incorrect-normals

Separate all utils and constants definitions into a new export_fbx_bin_utils.py file,
helps (a bit :/) to navigate in insanely big export_fbx_bin.py itself!

FBX export: Huge refactor of 'Model' part of the code, and fix exporting instances when org objects are not selected.

'Model' data (which can be Blender Object, DupliObject or Bone/PoseBone) are now
wrapped in an ObjectWrapper class that present the same API in all cases.
Hopefully this will make that part of the code easier to follow (and maintain/troublefix).

Also made var names a bit more consistent.

Note all this makes export slightly slower in worst cases (many actions to check against objects),
about 15% it seems. But tha 'export all actions' code need some more attention, maybe it's
possible to enhance its performances?