We'll fix this bug in 17.06, thanks for the report!
You can also try to fix it by yourself to check if it works for you. The bug is in the SDK's file blend4web_ce\scripts\process_blend.py. You can replace the line:
with the following:

and also change
to

Hi, I couldn't reproduce this under Win7, can you attach this project here? You can use "Export Project(s)" button in the Project Manager for sharing.

Hi, if you want to move objects away from a certain point you can do it without shape keys. For a set of objects you can just use get_translation/set_translation API methods and translate every object in a slider callback.

Hi! Blend4Web supports only the Group duplication method. The example uses "Verts", so it won't work.

Hi Jonathan, we've managed to find out what's the problem.

It seems that there's a driver bug related to Adreno 4xx/5xx GPUs, that are used in Samsung Galaxy S7 and Google Nexus 6 devices. This bug affects applications with multisample anti-aliasing enabled, so it may or may not appear on different webgl demos. Regarding the blend4web engine - this bug appears if WebGL 2 context is used. WebGL 2 was recently made available in Chrome Mobile and unfortunately it's not so stable at the moment and the latest 58 version is buggy. This bug is known and the next 59 chrome beta version works OK.

The immediate solution is to fix the app, by enabling the custom quality profile and setting the "msaa_samples" parameter to 1 before the initialization in the "m_app.init" method, for example:

- this will disable the buggy feature.

Also, according to the Chromium Development Calendar the estimated release date for the working beta is about Jun 6th, 2017: Chromium Development Calendar and Release Info, so the bug should disappear after updating the browser. Additionally, we'll add a workaround in the next 17.06 release to avoid this issue.

It appeared in Chrome 58.0.3029 on Windows 7. This is all I know, since my friend discovered it. I wasn't able to reproduce the problem myself. My machines are all Linux computers and the scene worked fine in Chrome, Firefox, Ice Weasel, Vivaldi. All that aside, I want to thank you for all the good work that you are doing.

Ah, I see. Thanks for the bug report.

It's camera frustum culling. When the emitting object is out of sight, its particles aren't rendered too. Should they be rendered or not depends on a specific scene, so this is a matter of optimization.
The easiest way to fix this is to check the "Disable Frustum Culling" option on the object tab.

So, we've reproduced this bug and found the reason. Briefly speaking, it's because that texture has non-power-of-two dimensions (6144x6144), which forces the engine to apply a resizing workaround and there was a browser bug. I think, if you manually resize the texture to, for example, 4096x4096 then it should work for you.

Reply to post of user ivanmarkovic
It happens on several Windows machines, on various browsers.

We're able to reproduce it in chrome only. Chrome devs already know about this bug and it was fixed in the chrome beta channel. We've also made a fix in the engine, which will land in the next 17.06 release. Anyway, it will be helpful if you tell us in what browsers you discovered the bug.

return context.active_object.type in {'MESH', 'CURVE', 'SURFACE', 'FONT'}
AttributeError: 'NoneType' object has no attribute 'type'

похоже, что перед вызовом нужно вручную выделить в блендере объект одного из перечисленных типов; NoneType означает, что ни один не выделен

а есть где то описание ключиков запуска?

только собственно в справке по флагу -h

да сейчас с переменной поробую. а что инсталятор не ставит ее?

какой инсталлятор? процесс установки - это ж просто распаковка архива с SDK и настройка пути в блендере

ДОПОЛНЯЮ
фокус с путем не прокатил

"C:\Users\user>set
blender=C:\Program Files\Blender Foundation\Blender\"

лучше вообще просто в PATH дописать путь к блендеру
или можно вместо set использовать setx, как описано здесь:
Setting and getting windows environment variables from the command prompt?