Activity Feed

Important question. Does this happen always with default scene, or when you enable certain material settings? If the latter, we need a test file.

Ok, sorry for my unprecision.

Moderation
Suggest we stop discussing ASD vs. WER vs. ERT vs. ... for now, as it seems to be an endless discussion with the only result of a big wall of text without much helpful arguments. There isn't much interest in keeping such tasks open.
So let's not focus on such "unimportant" details for now and tackle the real issues, okay? :)

And there, down below is a nice button with "Set Selected strip proxies" to enable the ones you want

Yes. Most of us agree on that. But there is no simple choice between ergonomy and user habits (from other softwares). Two similar standard keymaps would be great.

Are you sure the issue still appears in the latest build from here?

Can't find a Collision Bounds panel or so, could you attach a .blend so we can easily reproduce?

Hi bounsir,

new po
I try to download it after committing to fix new strings for 2.74.
Deadline is 8/3, isn't?
it.zip

@psy-fi did some work on this, so maybe he knows more?

AFIAK, this is already fixed, so could you try again with the latest build from buildbot? (Please use an "Official" build, not "Gooseberry)

I think ASD is better because there is more accessibility to keys like shift and control. It also is easier to reach more keys because your fingers are in the middle of the key board..

I think that it is due to when you call the second getScreenVec the physics have not been evaluated yet.
For example, if you use the post_draw call then the physics have been evaluated and you will obtain the right values:

From watching the video Im still not totally sure what the error is. (diagonal cut across a face when that face is aligned directly on the view axis?)

Closed by commit rBd2b6c6fd9b04.

Please use forums of mail for that, not our bug tracker. Especially not setting priority to high!