Hi,

Thanks for using XML3D. Its great that it works well for you but do not hesitate to let us know when there are problems or when you think there are chances to improve it in some way. Also, we are using XML3D in many other projects and so if you are looking for something it is not unlikely that we may already be working on it. Also feel free to let us know ho and for what you are using it, as this is always interesting for us.

But to your problem: I will let Torsten look into this in detail but a quick response from me. Of course you can use JS-AR-Toolkit as well but there are some advantages of the GE. So far we did not hear from incompatibilities but as no continuous integration tests are available between GEs yet (this is being discussed), this can unfortunately happen. We will look into that as quickly as possible (probably early next week).

Hope this helps (a bit) for now.

Best, Philipp

Hello,

there were some slight changes to parts of the JavaScript API in 4.9, which are related to the new asset feature, and the improved event handling that were part of the release. It is possible that these changes led to the problems you are describing.

We are going to investigate this and see if there is a simple solution. Of course, long term, our goal is to keep AR, which uses XML3D, and 3D-UI-XML3D fully compatible, so we highly appreciate feedback like yours that help us track down bugs during the development.

Could you provide us with more details about where the problems between AR and XML3D occur after changing to XML3D 4.9? Do you have access to some error messages in the browser console for example?

Best,
Torsten

Dear all,

Thanks for your answer!! ☺
I hadn’t received any mail, so I haven’t realized that comments were made (I don´t have clear whether the platform generates mails to tell you about updated or not. Is it necessary to manually check for every question we have made? No automatic mail option from the support platform?).

Regarding your comments, we’ll retrieve technical information and we’ll answer asap.

Thanks!!!! ☺
Carlos

De: Help-Desk jira-help-desk@fi-ware.org
Enviado el: jueves, 04 de junio de 2015 12:11
Para: Carlos Fuertes
CC: philipp.slusallek@dfki.de; torsten.spieldenner@dfki.de
Asunto: [FI-WARE-JIRA] (HELP-3152) [Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D

Hello Carlos,

Your request was assigned and some questions have been asked. Please, read the comments.
Would you please provide feedback?

Thanks.
Manuel
[cid:image001.jpg@01D09EC7.D674E550]

FW External User</secure/ViewProfile.jspa?name=fw.ext.user> created an issue

Help-Desk<https://jira.fiware.org/browse/HELP> / [extRequest] <https://jira.fiware.org/browse/HELP-3152> HELP-3152<https://jira.fiware.org/browse/HELP-3152>

[Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D<https://jira.fiware.org/browse/HELP-3152>

Issue Type:

[extRequest]extRequest

Assignee:

Torsten Spieldenner</secure/ViewProfile.jspa?name=tospie>

Components:

FIWARE-TECH-HELP

Created:

29/May/15 3:32 PM

Priority:

[Major]Major

Reporter:

FW External User</secure/ViewProfile.jspa?name=fw.ext.user>

Status:

[Open]Open

Good morning,

We're trying to implement a FIWARE application using XML3D and AR (Augmented Reality).

We have already used (without problems) GE XML3D (official version 4.9.0).

But when trying to use GE MiWi-AR (official version now available) to implement AR we have realized that it uses an old version of GE XML3D, and that it doesn't work properly with GE XML3D v.4.9.0.

Doubts:

• Is that problem of compatibility between GE's reported by others? (or maybe we're doing something wrong)

• If the problem is real, is it planned to update GE MiWi-AR to make it compatible with official current GE XML3D v4.9.0 version? When will it be available?

• If not, how can we implement AR on Fiware also using GE XML3D? By using JS-AR-TOOLKIT instead of official Fiware GE MiWi-AR? (we have tried that and it works fine with GE XML3D v.4.9.0).

Thanks for your support,
Carlos

Carlos J. Fuertes
Innovation Leader - European Projects
Mobile: (+34) 677 912 638

C/ Antracita 7
28045 - MADRID (SPAIN)
tlf. (+34) 91 456 04 28 - fax (+34) 91 534 87 20

Skype: cjfuertes1

P. Tecnológico Boecillo, C\ Luis Proust, 17
47151 - BOECILLO (Valladolid) (SPAIN)
tlf. (+34) 983 14 06 50 - fax (+34) 983 14 06 53

carlosfuertes@grupotecopy.es<carlosfuertes@grupotecopy.eshttps://jira.fiware.org/images/icons/mail_small.gif<carlosfuertes@grupotecopy.es>>
w w w . g r u p o t e c o p y . e s

Group

Tecopy

Dear all,

We provide requested feedback. Thanks for your help!!

• Could you provide us with more details about where the problems between AR and XML3D occur after changing to XML3D 4.9?

When using the MiWI AR "markerDetection" demo (the one referenced in the FiWare catalogue), you notice that the version they use of XML3D is local and outdated:

<script type="text/javascript" src="../../deps/xml3d.js"></script>

If you inspect it, you can see that it is a development snapshot from 2013:
@version: DEVELOPMENT SNAPSHOT (18.11.2013 14:09:57 EET) 2010-2013

If you want to use the last version of XML3D, the only change you need to do is:

<script type="text/javascript" src="http://www.xml3d.org/xml3d/script/xml3d.js"></script>

But if you switch the XML3D version to the last one, the example does not work.

• Do you have access to some error messages in the browser console for example?

If you change the XML3D library version (using <script type="text/javascript" src="http://www.xml3d.org/xml3d/script/xml3d.js"></script> instead of the local one), you get the following errors in the Google Chrome JS Console:

Xflow: No operator with name 'alvar.detect' found

xml3d.js:25187 TypeError: Cannot read property 'length' of null
at findOperatorByName (xml3d.js:32530)
at updateOperator (xml3d.js:32500)
at updateComputedChannels (xml3d.js:32472)
at ChannelNode.synchronize (xml3d.js:32248)
at ChannelNode.getChildDataIndex (xml3d.js:32281)
at getForwardNode (xml3d.js:28464)
at DataNode._getResult (xml3d.js:28367)
at ComputeRequest.getResult (xml3d.js:28695)
at null.getMatrix (xml3d.js:9236)
at DOMTransformFetcher.updateMatrix (xml3d.js:9219)

Uncaught TypeError: Cannot read property 'getRenderObjectFromPickingBuffer' of undefined

Regards,
Carlos

De: Carlos Fuertes
Enviado el: jueves, 04 de junio de 2015 13:11
Para: 'jira-help-desk@fi-ware.org'
CC: philipp.slusallek@dfki.de; torsten.spieldenner@dfki.de; David Cano
Asunto: RE: [FI-WARE-JIRA] (HELP-3152) [Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D

Dear all,

Thanks for your answer!! ☺
I hadn’t received any mail, so I haven’t realized that comments were made (I don´t have clear whether the platform generates mails to tell you about updated or not. Is it necessary to manually check for every question we have made? No automatic mail option from the support platform?).

Regarding your comments, we’ll retrieve technical information and we’ll answer asap.

Thanks!!!! ☺
Carlos

De: Help-Desk jira-help-desk@fi-ware.org
Enviado el: jueves, 04 de junio de 2015 12:11
Para: Carlos Fuertes
CC: philipp.slusallek@dfki.de<philipp.slusallek@dfki.de>; torsten.spieldenner@dfki.de<torsten.spieldenner@dfki.de>
Asunto: [FI-WARE-JIRA] (HELP-3152) [Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D

Hello Carlos,

Your request was assigned and some questions have been asked. Please, read the comments.
Would you please provide feedback?

Thanks.
Manuel
[cid:image001.jpg@01D09EEA.14C205A0]

FW External User</secure/ViewProfile.jspa?name=fw.ext.user> created an issue

Help-Desk<https://jira.fiware.org/browse/HELP> / [extRequest] <https://jira.fiware.org/browse/HELP-3152> HELP-3152<https://jira.fiware.org/browse/HELP-3152>

[Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D<https://jira.fiware.org/browse/HELP-3152>

Issue Type:

[extRequest]extRequest

Assignee:

Torsten Spieldenner</secure/ViewProfile.jspa?name=tospie>

Components:

FIWARE-TECH-HELP

Created:

29/May/15 3:32 PM

Priority:

[Major]Major

Reporter:

FW External User</secure/ViewProfile.jspa?name=fw.ext.user>

Status:

[Open]Open

Good morning,

We're trying to implement a FIWARE application using XML3D and AR (Augmented Reality).

We have already used (without problems) GE XML3D (official version 4.9.0).

But when trying to use GE MiWi-AR (official version now available) to implement AR we have realized that it uses an old version of GE XML3D, and that it doesn't work properly with GE XML3D v.4.9.0.

Doubts:

• Is that problem of compatibility between GE's reported by others? (or maybe we're doing something wrong)

• If the problem is real, is it planned to update GE MiWi-AR to make it compatible with official current GE XML3D v4.9.0 version? When will it be available?

• If not, how can we implement AR on Fiware also using GE XML3D? By using JS-AR-TOOLKIT instead of official Fiware GE MiWi-AR? (we have tried that and it works fine with GE XML3D v.4.9.0).

Thanks for your support,
Carlos

Carlos J. Fuertes
Innovation Leader - European Projects
Mobile: (+34) 677 912 638

C/ Antracita 7
28045 - MADRID (SPAIN)
tlf. (+34) 91 456 04 28 - fax (+34) 91 534 87 20

Skype: cjfuertes1

P. Tecnológico Boecillo, C\ Luis Proust, 17
47151 - BOECILLO (Valladolid) (SPAIN)
tlf. (+34) 983 14 06 50 - fax (+34) 983 14 06 53

carlosfuertes@grupotecopy.es<carlosfuertes@grupotecopy.eshttps://jira.fiware.org/images/icons/mail_small.gif<carlosfuertes@grupotecopy.es>>
w w w . g r u p o t e c o p y . e s

Group

Tecopy

Hi,

Sorry, that was indeed a glitch on our side, as I assumed that posts on
JIRA would also reach you. This has been clarified.

We have actually discussed this in your call yesterday and you
information will certainly help a lot to track this down. I am including
some of the XML3D and AR developers here as well.

Best,

Philipp

–

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3
---------------------------------------------------------------------------

Hello,

thank you very much for the error log of your problem. The bug seems to
be located in the Augmented Reality GE, more specific, in the way the GE
accesses functionality of XML3D and Xflow, not in XML3D itself.
I am going to assign this issue to the AR GE owner, so they can have a
look into it.

@Ari and the AR GE team:
It seems as if there are compatibility issues with AR and the latest
xml3d.js version. Could you please have a look at it? It furthermore
seems as if the Xflow operator for Alvar operations is missing (see
Carlos' stack trace: "Xflow: No operator with name 'alvar.detect' found").

Best Regards,
Torsten

–
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------

It seems that this is not an error but a possible need for a new compatibility update release of AR GE. Starting to investigate.

Hi,

This has been assigned to Ari as the Owner of the GE, who should be also
answer this question. Where needed we as XML3D Owners wuld be happy to
help. the first thing, however, is to exactly identify the issues.

Thanks,

Philipp

–

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3
---------------------------------------------------------------------------

the code to register alvar.detect to xflow seems to be: https://github.com/Chiru/FIWARE-AugmentedReality/blob/master/src/xAlvarImage.js#L180

has something changed in the API to define xflow operators or something in recent xml3d.js releases?

Old name "[Fiware-tech-help] Doubts - AR (augmented reality) and XML3D – GE MiWi-AR - GE XML3D" changed according to "Request for urgent action on the help-desk - deadline TODAY- 13:00" in 2015-07-06.

There seems to be something wrong with XML3D. After several attempts to get something visible from our old demos I tried a basic tutorial example of XML3d, The Teapot, at https://github.com/xml3d/xml3d.js/wiki/The-Basics-of-XML3D . Result: nothing visible.
Console log:

GET http://www.xml3d.org/xml3d/script/xml3d.js [HTTP/1.1 200 OK 804ms]
GET http://www.xml3d.org/xml3d/script/tools/camera.js [HTTP/1.1 200 OK 163ms]
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. teapot.html
"loadDocument@http://www.xml3d.org/xml3d/script/xml3d.js:6065:8
[10]</Resource.getAdapterHandle@http://www.xml3d.org/xml3d/script/xml3d.js:6342:16
[7]</NodeAdapter.prototype.getAdapterHandle@http://www.xml3d.org/xml3d/script/xml3d.js:5446:0
[18]</DataAdapter.prototype.updateAdapterHandle@http://www.xml3d.org/xml3d/script/xml3d.js:7936:24
[18]</DataAdapter.prototype.init@http://www.xml3d.org/xml3d/script/xml3d.js:7925:0
[7]</NodeAdapterFactory.prototype.getAdapter@http://www.xml3d.org/xml3d/script/xml3d.js:5552:8
[10]</Resource.getAdapter@http://www.xml3d.org/xml3d/script/xml3d.js:6364:0
[46]</<.createRenderNode@http://www.xml3d.org/xml3d/script/xml3d.js:12471:26
[46]</MeshRenderAdapter@http://www.xml3d.org/xml3d/script/xml3d.js:12465:4
[42]</RenderAdapterFactory.prototype.createAdapter@http://www.xml3d.org/xml3d/script/xml3d.js:12177:0
[7]</NodeAdapterFactory.prototype.getAdapter@http://www.xml3d.org/xml3d/script/xml3d.js:5549:14
[7]</NodeAdapter.prototype.traverse@http://www.xml3d.org/xml3d/script/xml3d.js:5467:22
[7]</NodeAdapter.prototype.traverse@http://www.xml3d.org/xml3d/script/xml3d.js:5468:0
[112]</GLRenderer@http://www.xml3d.org/xml3d/script/xml3d.js:21607:4
[58]</RendererFactory/this.createRenderer@http://www.xml3d.org/xml3d/script/xml3d.js:14312:23
[53]</configure/<@http://www.xml3d.org/xml3d/script/xml3d.js:13394:23
[53]</configure@http://www.xml3d.org/xml3d/script/xml3d.js:13392:4
initXML3DElement@http://www.xml3d.org/xml3d/script/xml3d.js:9502:8
onLoad@http://www.xml3d.org/xml3d/script/xml3d.js:9580:8" xml3d.js:25200:0

"No view referenced. Trying to use first view." xml3d.js:25194:24
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create xml3d.js:10977:8
TypeError: this.renderer is undefined xml3d.js:17924:4

The "renderer is undefined" message count increases, when I move cursor above the possible rendering area.
The browser is Firefox 38.0.5
It seems I cannot inspect further without help from XML3D people.

Hi,

can you deploy the scene that causes the error above somewhere to inspect, maybe a FIWARE Lab oder Testbed instance with public IP?

I created a Help request https://jira.fiware.org/browse/HELP-3516?filter=-2 for XML3D people for this.

Cannot analyze the issue, because cannot get anything visible from XML3D - even in a copy of a tutorial example.

Hi,

could you please provide some more information about your actual setup?

• Which XML3D - Version are you using? You can find out by typing
  XML3D.version into the browser console.
• Could you please provide the code of your website?
• Is your application running locally (from filesystem), or is it hosted
  on a Webserver?

Best Regards,
Torsten

–
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------

My problem with analysis was that I tried to run XML3D from file. XML3D cannot be run directly from a file. Firefox didn't give any indication of problems. Chrome gave a message about failure to read from a file. Analysis continues.

Mystical behavior with XML3D 4.9.2. I haven't yet found a good, up-to-date Javascript API documentation for XML3D in order to check that the API is used correctly from AR GE.

With Chrome I can now recreate the error "Xflow: No operator with name 'alvar.detect' found". Not found the root cause yet.

Your Xflow-Operator is defined in some JavaScript-File. I had a look at
the AR Source on Github and found the respective place in
/src/xAlvarImage.js, line 180
(https://github.com/Chiru/FIWARE-AugmentedReality/blob/master/src/xAlvarImage.js#L180):

There it says
Xflow.registerOperator('alvar.detect',

);

Please check whether the script that registers the operator is loaded
and executed correctly.
@Christian / Kristian: Are there changes in the Xflow-Interface that
prevents a correct initialization of the new operator?

–
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------

Hi,

there were no changes to the Xflow operator interface recently, but I
cloned the AR repository and had a look at the demos myself. It appears
that the window.onload in markerDetection.js is fired /after///the
onload listener that XML3D uses to initialize the scene. This is why the
alvar.detect operator isn't found, at that point it hasn't been
registered yet.

I would suggest registering the Xflow operators right away instead of
doing it in an 'onload' listener. It's safe to call
Xflow.registerOperator even if the document hasn't finished loading, as
long as xml3d.js has already been parsed by the browser.

Hope that helps,
Christian

–
Christian Schlinkmann
Agents and Simulated Reality @ DFKI GmbH <http://www.dfki.de/web>
Developer, XML3D @ xml3d.org <http://xml3d.org>
DFKI GmbH, Campus D 3 2, Room 2.32 NB
66123 Saarbrücken, Germany
Phone: +49 681 85775-5082

Added Carlos who posted the original external request back into the
loop, as he may not receive updates via JIRA automatically

–
Torsten Spieldenner, M.Sc.

Tel.: +49 6 81 / 8 57 75 - 77 48
Fax.: +49 6 81 / 8 57 75 - 22 35

Internet: http://www.dfki.de/web/forschung/asr/

-------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany

Geschaeftsfuehrung:
Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
Dr. Walter Olthoff

Vorsitzender des Aufsichtsrats:
Prof. Dr. h.c. Hans A. Aukes

Amtsgericht Kaiserslautern, HRB 2313
-------------------------------------------------------------

When I tried to reorganize the startup sequence to register the xflow
operator
earlier in the demonstration, I hit another problem:(xml3d.js line 24752)
"Note to observe is not (yet). Make sure to pass an XML3D node and to
execute " +
"this function after XML3D has been configured e.g. inside a
DOMContentLoaded listener."

It seems that the implicit requirements of xflow & xml3d for the
initialization
sequence have changed so muchthat some redesign of the demonstration is
needed.

Link to documentation specifying the requirements for combined
initialization
sequence of xflow & xml3d is needed to go further.

I start my delayed summer vacation now and return to business after one
month.

BR
Ari

–
Ari Okkonen
Adminotech

Waiting information from XML3D specialist.

Hi Ari,

can you provide the latest version of your code that leads to above error?

Best,
Torsten

A small redesign cycle will start very soon on AR GE due to replacement of Alvar tag tracking subsystem. This issue will better addressed then. Closing this issue now.