JGeerWM
JGeerWM

Reputation: 870

Autodesk.Viewing.OBJECT_TREE_CREATED_EVENT not firing

I have a certain AutoCAD model that was published to A360 and for some reason I cannot explore the model tree in the Viewer or get the Autodesk.Viewing.OBJECT_TREE_CREATED_EVENT to fire.

When I look in the console, I see 404 Errors returned from https://developer.api.autodesk.com/viewingservice/v1/items

The model has been uploaded a couple of times, but the problem persists.

Here are sample errors:

https://developer.api.autodesk.com/viewingservice/v1/items/urn%3Aadsk.viewing%3Afs.file%3AdXJuOmFkc2sud2lwcHJvZDpmcy5maWxlOnZmLndJMjhLUzI5UW1Ld2l3T05TQTV0cUE_dmVyc2lvbj0x%2Foutput%2Fundefined?domain=http%3A%2F%2Fgtpstratus.azurewebsites.net&acmsession=9ed966902dfbb1c7b6586ba01f98291a

https://developer.api.autodesk.com/viewingservice/v1/items/urn%3Aadsk.viewing%3Afs.file%3AdXJuOmFkc2sud2lwcHJvZDpmcy5maWxlOnZmLndJMjhLUzI5UW1Ld2l3T05TQTV0cUE_dmVyc2lvbj0x%2Foutput%2Fobjects_attrs.json?domain=http%3A%2F%2Fgtpstratus.azurewebsites.net&acmsession=9ed966902dfbb1c7b6586ba01f98291a

https://developer.api.autodesk.com/viewingservice/v1/items/urn%3Aadsk.viewing%3Afs.file%3AdXJuOmFkc2sud2lwcHJvZDpmcy5maWxlOnZmLndJMjhLUzI5UW1Ld2l3T05TQTV0cUE_dmVyc2lvbj0x%2Foutput%2Fobjects_vals.json?domain=http%3A%2F%2Fgtpstratus.azurewebsites.net&acmsession=9ed966902dfbb1c7b6586ba01f98291a

https://developer.api.autodesk.com/viewingservice/v1/items/urn%3Aadsk.viewing%3Afs.file%3AdXJuOmFkc2sud2lwcHJvZDpmcy5maWxlOnZmLndJMjhLUzI5UW1Ld2l3T05TQTV0cUE_dmVyc2lvbj0x%2Foutput%2Fobjects_avs.json?domain=http%3A%2F%2Fgtpstratus.azurewebsites.net&acmsession=9ed966902dfbb1c7b6586ba01f98291a

https://developer.api.autodesk.com/viewingservice/v1/items/urn%3Aadsk.viewing%3Afs.file%3AdXJuOmFkc2sud2lwcHJvZDpmcy5maWxlOnZmLndJMjhLUzI5UW1Ld2l3T05TQTV0cUE_dmVyc2lvbj0x%2Foutput%2Fobjects_offs.json?domain=http%3A%2F%2Fgtpstratus.azurewebsites.net&acmsession=9ed966902dfbb1c7b6586ba01f98291a

Upvotes: 0

Views: 146

Answers (1)

Augusto Goncalves
Augusto Goncalves

Reputation: 8604

As of now (April, 2017) this issue is under investigation on version 2.13/2.14. I would recommend you use version 2.12 instead.

Upvotes: 1

Related Questions