User posts Yuri Kovelenov
07 January 2015 09:42
06 January 2015 22:18
Preference is now for a slight glow to all clickable objects that is always on so mobile users know there is something to click.For persistent glow you need something like this:
var m_scenes = require("scenes");
var myobj = m_scenes.get_object_by_name("How your object is named in Blender");
m_scenes.apply_glow_anim(myobj, 1, 1, 0);
FYI: hover glow not working in IE 11Yeah, being one of "fancy features" that require postprocessing, glow effect is not available in the low quality mode.
06 January 2015 21:57
Not so much for personal projects, but work related stuff requires acknowledging a user base of 43% IE.According to Statcounter, IE share is about 22%. I prefer to trust their estimates.
06 January 2015 13:04
06 January 2015 12:53
IE does nor support depth textures, so we just enforce low quality mode for it in which all fancy features are disabled including god rays. Also IE does not support Web Audio.
Some other hacks can be viewed in this listing. E.g. Firefox video textures issue can be found in line 34.
See also Can I Use website.
For depth texture statistics and for other WebGL and HTML5 features please refer to webglstats.
Anyway, Blend4Web feature support table for different browsers, OSes and devices could be very useful, thanks for suggesting.
Some other hacks can be viewed in this listing. E.g. Firefox video textures issue can be found in line 34.
See also Can I Use website.
For depth texture statistics and for other WebGL and HTML5 features please refer to webglstats.
Anyway, Blend4Web feature support table for different browsers, OSes and devices could be very useful, thanks for suggesting.
06 January 2015 12:41
But what about animation of visibility? In my case I could make an illusion of movement by switching objects on/off.By coincidence, we are now implementing this feature in the NLA Script.
In one project, I used location animation and moved it far far away to make it dissapear but is there another way?
06 January 2015 06:37
Since the original files we receive are .ASMs and .PRTs (PRO-E Files) the typology is terrible. Some of the edges and verts aren't even connected correctly.
Perhaps retopology is what you need.
06 January 2015 06:30
Hi Ryan,
I just tried this tool myself. You need to click the "reload normals" button to see the actual edited and saved normals.
untitled2.blend
untitled2.html
Yes we know this could be done in more convenient way. Hope to see this tool implemented in Blender natively some day.
I just tried this tool myself. You need to click the "reload normals" button to see the actual edited and saved normals.
untitled2.blend
untitled2.html
Yes we know this could be done in more convenient way. Hope to see this tool implemented in Blender natively some day.
05 January 2015 21:29
05 January 2015 21:25