Blender 2.71 - FBX exporter is not compatible

I installed Blender 2.71 yesterday (official release).
Now Unity 4.5 reports that

“Blender could not convert the .blend file to FBX file.
You need to use Blender 2.45-2.49 or 2.58 and later versions for direct Blender import to work.”

I contacted Blender.org, and their answer was:

“Thanks for the report, but that’s a Unity “bug”, not Blender’s. They have to update their own script (which is a shallow wrapper around Blender’s FBX exporter) to support new addon.”

Is there a patch that will fix that problem?
I looked around and couldn’t see any reference to that issue.
All work has stopped, not good.

This issue should be fixed in blender 2.72. I updated blender’s python to 3.4.1 and worked around the compiler bug in MSVC 2013 that made this issue appear in python. I am not a Unity user and do not have it installed to test with but I am very happy with any feedback and will spend the time to make sure that 2.72 official does not have this defect whomever is at failt.

As of today testbuilds are up at: Index of /release/Blender2.72/

For reference:

If you know what you’re doing(I don’t!) the import script lives somewhere like C:\Program Files (x86)\Unity\Editor\Data\Tools\Unity-BlenderToFBX.py

I think it just loads blender in the background then runs that script on the file, the new fbx exporter must have new parameters that need putting in. Would like to know if you manage to fix it!

Use Blender’s FBX Export instead. If an FBX is incompatible somehow, run it through Autodesks free FBX Converter tool.

I sometimes see this problem when I save my blender file in edit mode and try to import directly to Unity (meaning, I drag and drop the .blend file into my unity project window). I always make sure I save my .blend files when they are in object mode. I use Blender 2.70.

I updated blenders python version to 3.4.1 and to include a workaround for the bug that Microsoft introduced in their compilers that is the actual cause of this issue.

Index of /release/Blender2.72/ has a testbuild for 2.72 that includes the actual fix.

http://bugs.python.org/issue17797