You should never have to erase Blender's bundled Python with a custom Python installation, I guess this is what triggers the crash. So could you repeat the tests mentioned by Bastien without the Python hack, just using a out-of-the-box Blender build (from buildbot)?
Can confirm that. @psy-fi, Maybe something stupid like a GL_DISABLE is missing or so? But looks like the root of the bug comes from the game engine -> moved to Game Engine
Can confirm that. Caused by rBb62c2a913bb41.
What do you mean by 'I can't export audio files'? A valid bug report needs a precise description of the issue, and simple, precise steps to reproduce it, with all needed files…
Campbell committed better fix
Thank you for helping solving this bug.
It's not correct to actually change the lamp in rna_use_shadow_get, such getter functions should never modify data, only read it. If anything needs to change, it needs to happen when the new lamp type is set. But also a problem is, spot lamps can have raytraced shadows with Blender Internal, so it's not correct to always switch them to buffer shadows automatically.
I'm not sure if this is the right place for discussion (especially as this is closed), but some places are still missing the separator, e.g. the face count in the decimate modifier:
@ton -
A) the idea is to show snippets of info that can be easily be seen/absorbed, not a full tutorial mode.
Thanks Brita - I thought it better practice to separate that behaviour from the implementation, but perhaps it's not an issue.
So, for the motivation, I decided to make a dimension property available in BGE because I was programatically creating a tiled map with hexagons and to place the hexagons well obviously I needed to get have the dimensions. It seemed rather weird not to be able to get such a basic property from BGE. The workaround at the time for me was to create the hexagon at the proper dimensions and then apply the scaling and use the scale in BGE instead.
@sybren I meant storing the dimensions during conversion, because blender does take into account the object space, instead of a bb.
Then for what could change that in runtime... scaling an object? or if it is a softbody or cases that don't even come up to mind easily. So I foresee an easily broken property, without further motivation I'd say not to add.
thumbs up for the patch and thumbs up for sybren's review.
best to move that in before getting in fix-only mode tomorrow at the meeting.