Release candidate 14.12 is out

Ситуация не столь плохая если учесть, что браузер умеет кешировать ресурсы.

Файловая система из браузера не доступна из соображений безопасности, однако имеются средства сделать виртуальное файловое хранилище внутри браузера. Как только соответствующие API будут доступны для всех браузеров (пока это доступно только в Chrome), можно будет рассмотреть и такой вариант.

Hi

Encoding video can be a tricky job, I don't know about websites, you may try Handbrake or some other GUI utility. Our converter depends on ffmpeg (libav tools) to operate and tested for UNIX OSes only (Linux/OS X). This converter designed for large amount of resources and can also convert textures and audio.

About css, the canvas size is setup by resize() function from main module. This is how it handled in webplayer app:

I have some updates about this issue

We have looked and encountered that there is a Firefox bug. Thus it's not possible to use video textures (any format) from html in this browser, so consider json export.

Also there is no support for video fallback in html (for IE or Safari if you use webm, for Firefox and Chromium if you use m4v). Again, consider json export.

Ok guys

I'd recommend using webm format. It has better quality and is open-sourced (myvideo.webm). For browsers like safari and IE you need also MPEG4 video, so you should use some converter, append lossconv suffix and place the new file along webm one (myvideo.lossconv.m4v). You may also check our converter from SDK, in the upcoming release it will be even better.

About ogv issue, thats some kind of a bug, will check it, thanks for report.

In your demo you may shorten NLA strips and get more responsive behavior (the sounds in NLA are never cropped and always play the whole length)

The feature will be available in our next release (expected next week). Also we plan to release early developer preview on Friday.

Firefox issue was fixed

Hi again!

You should specify the correct NLA strip length for your sound (because Blender is not doing it automatically). If the strip is longer the engine will play it repeated.

As about cycles. Some cycles nodes we plan to support in Blender's viewport, some are just impossible to implement. See also the FAQ

Hi Christoph and thanks for your interest in Blend4Web!

You are right, set_glow_intensity() conflicts with the glow animation because the glow animation itself is some kind of basic and periodic change of intensity. It's just a hint, you don't require to use it in your code. If you need custom solution I'd recommend to implement it in the render_callback() (see main module API). In this callback you have timeline so it's easy to create any effect you want.