Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:WebUI
-
HD-Enabler:Web Tundra Avatar
Description
Hi,
Running the Virtual Character GE locally, by opening the html files, the animations are successfully loaded. Although, when using an HTTP server such as Apache, I only get a blank page.
The outputs from Tundra server are:
Using Chrome Version 38.0.2125.111, Firefox version 33.0.2 and Safari 8.0:
User with connection ID 1 and protocol version 3 logged in.
Warning: AssetRefListener::HandleAssetRefChange: Asset request for asset "default_avatar.avatar" failed.
[Avatar Application] Created avatar for Test User
[WebSocketServer]: Connection ID 1 login successful
If I use the internet explorer version 11 the warnings are:
User with connection ID 2 and protocol version 3 logged in.
Warning: AssetRefListener::HandleAssetRefChange: Asset request for asset "default_avatar.avatar" failed.
[Avatar Application] Created avatar for Test User
[WebSocketServer]: Connection ID 2 login successful
[2014-10-30 18:52:26] [fatal] handle_read_frame error: websocketpp.transport:2 (Underlying Transport Error)
There are no relevant information in the Apache logs.
OS: Mac OS X 10.10
Apache running on Ubuntu 14.04 LTS.
Best,
- - -
João Gonçalves
joagonca@onesource.pt
00 351 927 997 531
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
Activity
Hi João,
Thank you for the report and sorry for the late reply.
Now that I took a look at the console log, it appears to me that you have tried to run Tundra's avatar application "Tundra 2.5.3RC\scenes\Avatar\scene.txml". That scene was created to demonstrate native tundra client and server avatars, and the current WebTundra codebase doesn't support it directly. This is because the WebTundra's asset pipeline can't handle Ogre3d mesh format, and each of scene mesh needs to be converted manually to Three.js format.
Order to run the avatar scene in WebTundra following steps needs to be done:
- Convert Ogre3d .mesh format to Three.js .json format.
- Create .avatar description file for the WebTundra.
- Create WebTundra application (html) that sends movement EntityActions to Tundra server.
I did test the animation synchronization with Entity Actions, but that code wasn't mature enough to be pushed to official Tundra repo (https://github.com/realXtend/tundra). But at least avatar transform and animation playback should get synchronized if we choose to write an application that uses the Avatar.
Since this isn't a direct bug, I'll close this ticket.
br,
Jonne
it works here: http://playsign.tklapp.com:8000/WebTundra/examples/Avatar/
that's just a git clone of WebTundra master, where the Virtual Characters GE is included - same as release 1.0 (fiware 3.3)
update: oh with a closer look of the log I see that you're using the Tundra server too (Synchronization GE) – i haven't checked the VC doc now to see how that instructs. the example I point to is just a single user demo, without Sync GE, but just downloading the avatar over http.