Ответ на сообщение пользователя Mentalist
@cloudou A workflow that may work for you is:
Animate different empties to represent your camera views in Blender. Use Copy Transform constraints to attach your camera to the empties. Then you can keyframe the visibility (or influence sliders) of these constraints, and in doing so "hand-off" the camera between the empties.



Example setup: empty_handoff.blend

When you're done animating the empties and constraints (remember to Save As), you can bake the camera's movement.
Object > Animation > Bake Action
Remember to enable the Visual Keying option so that the effect of your constraints will be taken into account.





Example result: empty_handoff_baked.blend

The only drawback of a sudden camera hand-off is that if you are using motion blur it will blur between the huge leap the camera takes and look wrong. Currently B4W does not have motion blur, so don't worry about it. There is indication that motion blur is planned for the future, but by then support for multiple cameras may also be added. Anyway, this technique is something you can use for now.

Ответ на сообщение пользователя Mikhail Luzyanin
B4w suports only one exported camera, so if you want to switch between cameras like in films, you need to bake all cameras movement into actions using blender animation baker, then convert all actions into NLA strip and combine from them long animation chain in timeline in one exportable camera. If you look into the sdk examples you can see there the Petigors_Tale game. If you push Intro button you can see a short movie made using this method.

Ответ на сообщение пользователя Alexander Kovelenov
Hi!
Maybe your texture does not have alpha channel or so. Check blender/materials/alpha.blend file inside your SDK to see how this type of transparency is configured.