Your comments

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

Hi -
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

Larry -
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


Hi Tony -
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!

Hi Tony - we're working on it. Some problems have been noted, and are being addressed. The process should be concluded within several days.
Tony -
Your characterization of the problem is spot on.
The full body character currently takes advantage of Flash where available - and HTML5 otherwise.
We will be making a change to play back using HTML5 on Chrome.This change will be made in the next several days - it is being tested now.
Regards,
Gil