-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wrong path in cameraParametersUrl in threex-artoolkitcontext.js #44
Comments
I will fix tomorrow this. |
Great job @kalwalt, i'm closing this as you solved on the linked PR. |
yes, i think it was a very old isue indeed. |
In the future we can consider also another solution for default data configuration, it would be useful have a config file where to store all this settings and so a user can easily changes the default settings. See for example the Ogre engine or other project that has a similar approach. I will open a separate issue for this feature. |
This issue is closed and you have already posted in a new issue here #539 !! Please don't double posting! |
Do you want to request a feature or report a bug?
Trying to fix another bug #43 i found this one.
What is the current behavior?
in threex-artoolkitcontext.js there is this line:
AR.js/three.js/src/threex/threex-artoolkitcontext.js
Line 21 in c2a780a
but it is wrong because point to non existent path.
If the current behavior is a bug, please provide the steps to reproduce.
Do this, in dev example comment out this line:
AR.js/three.js/examples/dev.html
Line 101 in c2a780a
in this way you will force to use the path from threex-artoolkitcontext.js, and you will receive this error:
to solve we need to change the path for cameraParametersUrl in this way:
cameraParametersUrl: ARjs.Context.baseURL + '../data/data/camera_para.dat',
Please mention other relevant information such as the browser version, Operating System and Device Name
Tested on Desktop localhost (ubuntu 18.04.03)
What is the expected behavior?
It should load the default camera parameters.
The text was updated successfully, but these errors were encountered: