Your comments
Hello François -
Please try our support example here -
http://www.oddcast.com/support/saytext_fullbody.html
also - look through our other support examples - each example has "full body" and "classic" versions -
http://www.oddcast.com/support/reference.html
Hope this helps - let me know
Regards
Gil
The SitePal Team
Tony -
We looked into it - our conclusion is that this appears to be a bug with Chrome 46 for desktop.
We do not see the problem in other browsers. Let me know if your experience differs.
Furthermore - we tested with pre-release versions of Chrome -
The latest Beta (47) and Canary(48) do not exhibit the bug.
Since Google release Chrome updates frequently, we think this problem will fade away soon (when 47 is released).
Hope this helps,
Gil
Hi Sachin -
Can you post a link to your page where we can review this functionality?
Are you using a full body or classic character?
I ask because the full body character does not support some of these functions - specifically -
* setGaze
* setFacialExpression
* setIdleMovement
Are not supported for Full Body characters.
setLink & setStatus should work though.
Gil
Hi Sachin -
The SitePal support page includes an API example that demonstrates this functionality -
http://www.oddcast.com/support/setLink_setTarget.html
Hope this helps,
Gil
The SitePal Team
Tony -
Team is on it. I hope to have an update early next week.
Best,
Gil
Hi Tony -
We see the problem - looking into it & will advise asap.
Gil
Posting here on the forum might be a good way to start.
We do not track our developers and could not give you a list.
Let me know how goes - I'd be interested to know.
Meanwhile - if you have questions about your development effort let us know - either here or by sending a note to support@sitepal.com
Best,
Gil
The Sitepal Team
Our systems are up & running. We have not experienced downtime today (& not for quite a long time).
We have automated tracking sensors that trip whenever any subsystem fails - so we would know.
Also - our customer support would be overwhelmed.
Must have been a local disruption of internet service or network connectivity.
Are you still experiencing a problem?
LMK
Gil
This issue is now resolved.
Full body characters are now displayed in HTML5 on Chrome (as well as on mobile devices of course)
We will apply the same to other browsers in the coming weeks - as we gradually phase out Flash.
Let me know if you notice any problem.
Best,
Gil
ps. interesting workaround - good to know!
Customer support service by UserEcho
Hi Sachin -
Without seeing your page I'd need to speculate.
Are you using 3D or 2D classic character?
The 2D character does not support setSpeechMovement and may return an error.
Loading a model dynamically -
The only way is to switch the Scene using the loadScene function call.
Hope this helps!
Gil
ps. would be great if you could create a public version of your page where problems could be seen.